Peter,
Do you need the MS C compiler to build the libs natively, or were you
thinking of some other MS software that would make your life easier. I
can setup anything you need on the vmware system at RAL. I thing the MS
C compiler is free, isn't it, but you to not get the visual studio
stuff.
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Peter W. Draper
Sent: 31 January 2005 13:55
To: [log in to unmask]
Subject: Re: Starlink Nightly Build On System: SPARC-SOL9
On Mon, 31 Jan 2005, Mark Taylor wrote:
> On Mon, 31 Jan 2005, Peter W. Draper wrote:
>
> > > If you feel the urge to have a go at sorting the JNLP files out,
> > > by all means go ahead (probably it needs some changes in SPLAT as
well
> > > as my packages, so you'll have to do some stuff in any case). If
you
> > > don't though I'll take a look at it in the reasonably near future.
> >
> > OK, I'll have a look.
>
> Right thanks, I'll leave it with you until you say otherwise.
>
> > I'm completely bogged down on the JNIAST windows DLL problem that's
> > holding back SPLAT-VO progress, so I intend to give it a rest for a
while
> > and see if I get my hands on some Microsoft development kit we're
> > apparently licensed for in the university. It's grasping at straws,
but
> > it's all I have without a major insight.
>
> Bummer. JNIAST on Windows has worked OK up till now hasn't it.
Yes, had some problems in the early days (mainly before I started using
MINGW interfaces, rather than Cygwin), but it seems to have been rock
solid for quite a while.
> What's started to go wrong now? (not expecting to be able to help,
just
> curious).
Well it just randomly crashes when loading in FITS table spectra.
I'd swear it was some problem in the newer parts of AST (the units
handling code), but cannot track anything down. Windows doesn't give you
a
lot to work from when things are going badly just some memory
references,
or offsets from the start of a routine if you're lucky. This is
particularly bad because I'm building for Windows under Cygwin targeting
MINGW, so there's a lot to get in the way. Then of course Java doesn't
help. Checking native code for memory overruns or leaks as you'd
naturally
do when seeing this kind of behaviour is impossible as the JVM does so
many clever things all the memory leaks/overrun checkers are completely
stuffed.
Peter.
|