On Wed, 4 Aug 2004, David Berry wrote:
> On Wed, 4 Aug 2004, Tim Jenness wrote:
>
> > On Wed, 4 Aug 2004, Rankin, SE (Stephen) wrote:
> >
> > > Is memsys still a requirement to build KAPPA in the new CVS system?
> >
> > No. Currently the memsys build is disabled.
> >
> > I'm intending to put the test in to conditionally enable the memsys build
> > (it's possible to check for the include file) but I haven't got around to
> > it yet (partly because we don't have mem installed at the JAC)
>
> Good oh!
>
David, since you're back, can you have a quick look at the "possible
refactoring" section of the wiki and comment on my kappa/kaplibs notes?
In essence, at the top of my list:
1. Move the kappa_mon application .f files to kappa_mon directory,
move ndfpack_mon stuff to ndfpack and kapview_mon to kapview
directories. I would leave the toplevel .f files in the toplevel
but all the application files would be tidier in subdirs
2. Change the link so that only ndfpack (!) links against tk.
[no reason for kappa_mon and kapview to include tk in the link]
This would require a libtkkpg to be made.
3. Actually, change kaplibs so that it has a -notk option
so that it is possible to link against kaplibs without
dragging in libtk.
Much of this came out of the porting to OSX exercise since it was becoming
obvious that most applications linked against tk even though they didn't
use it.
If you approve of these changes I'll start fiddling [with the reorg of the
application fortran files it might be better to move them in the
repository to retain history and just act as if they were never in the
toplevel]
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|