Thinking about things that need to be in place for the nanahope
release in July. I can think of the following things that are being
worked on or problematic:
- vtk no longer builds on x86_64 Mac OSX because it keeps finding
the native Tcl/Tk frameworks instead of
finding the starlink tcl libraries. There are updates in the
repository submodules that are not synced
to the supermodule so I'm not sure whether this needs a local fix.
[ 87%] Building CXX object Rendering/CMakeFiles/vtkRenderingTCL.dir/
vtkRenderingTCLInit.o
Linking CXX shared library ../bin/libvtkRenderingTCL.dylib
ld warning: in /Developer/SDKs/MacOSX10.5.sdk/System/Library/
Frameworks//tk.framework/tk, missing required architecture x86_64 in
file
- Norman may or may not come through with the autotools update but
I'm thinking probably not in time for
nanahope
- on leopard the default build generates incorrect libtool files for
the fortran section (it's an
issue with -nostdlib). This may be a g95 vs gfortran linking issue
or maybe a leopard vs tiger issue. I haven't
tried building 32-bit with g95 on my leopard system.
- Not sure if Brad is intending to do an automated perl build for
this release using shipwright
or whether he is going to build for all architectures manually.
- SAMP support in GAIA
- David's CUPID VO STC-S work seems to be ready.
- I think GAIA-VO needs more testing by people before the release.
Can people try it and see whether
it works for them?
- Peter: Will GAIA visualisation of STC-S catalogues be ready at
least in a demo mode? Or would you prefer to punt to August? I'd like
to have some debugging time before you turn into a pumpkin.
- Sam Hart has requested that we ship the linux builds with Java 1.6
so that he can begin the process
of migrating the OT now that JSky requires v1.6.
- Need to make sure the Nanahope release notes are updated (even for
oracdr).
In terms of architectures:
CentOS5.3 32- and 64-bit
OSX PPC Tiger
x86_64 Leopard [gcc-4.2 / gfortran ]
32-bit intel Tiger
Will this be the last Tiger release? It doesn't have to be if we can
get a fully automated build working so that we can just "push the
button" and tar up the result.
What have I missed?
--
Tim Jenness
Joint Astronomy Centre
|