On Thu, 3 Jul 2014, Malcolm J. Currie wrote:
> Do we know how long it wouldtake to fix the specific JPEG library issue and
> the general relocation? We were waiting for Peter's revisions to the
> autotools before we could avoid setting DYLD_LIBRARY_PATH. Where are we now
> in this respect Peter?
Sorry, no idea, it's not something I looked at and I don't work on OS X.
We are using the latest libtool so if this is supposed to work then it
might. The likely gotchas are those parts of the tree that do not use
libtool.
> A part of me would like to see this fixed prioperly for 2014A, and if it
> takes a week or so then Mark may have TOPCAT 4.2 ready. OTOH I can see
> potential dangers of new issues cropping up, as we're not testing MacOSX as
> extensively as Linux. Also I don't want to keep pushing the release back.
> When one issue is fixed, something else can come along and we never make a
> release.
>
> What do we/I need to do to make 2014A starjava apps work on MacOSX?
> Just run install_name_tool -add_rpath on the binaries?
>
> Was anything done specifically in the build-system changes to cope with
> CFITSIO?
>
> To get it out of the door I'd be happy for this release to say in the
> installation notes that users need to have the JPEG library installed, say
> from Homebrew. That would give us more time until the next release to
> resolve the relocation issue.
>
>> Fixing up the binaries so that we do not need to set DYLD_LIBRARY_PATH is
>> by far the best option.
>
> OK. Sarah has been doing some tests that look promising.
>
>> Secondly, it's probably true that we should link against the Apple imaging
>> frameworks but I'm not sure how to handle the -framework linker option in
>> autotools.
>
> This is longer term, not 2014A, right?
>
> Malcolm
> --
> Scanned by iCritical.
>
--
Peter W. Draper, http://astro.dur.ac.uk/~pdraper
|