On Fri, 21 Jul 2017, David Berry wrote:
> On 21 July 2017 at 12:32, Mark Taylor <[log in to unmask]> wrote:
> > On Fri, 21 Jul 2017, David Berry wrote:
> >
> >> Ah yes - thanks for keeping your eye on this Mark. When I looked over
> >> this change I missed the point that jniast carries its own (rather
> >> old) AST source files round with it in src/ast, and does not use an
> >> external AST library. So as you say there is no need to make any
> >> changes to jniast.
> >
> > Not quite - the src/ast/*.c files are never compiled, they are
> > only used for their comments (to auto-generate javadocs).
> > If you execute the build-native ant target it does use an
> > external AST library (which must match the API it's expecting),
> > but that's not a normal part of the build process, it's only
> > done when generating the src/lib/*/jniast_libs.jar files,
> > which are checked in to the repository.
>
> Ah - I was fooled by the fact that the jniast sharable library defines
> all the AST internal symbols itself rather than using libast.so -
> shows my poor knowledge of ldd etc.
Bet my ignorance of linkers is deeper than yours!
> So it could be a little tricky to do a build-native as we'd need to
> dig out and build a suitable old version of AST first.
That's what VCSs are for I suppose. But I still don't fancy trying it.
Historically, Peter has always stepped up to do this when it's been
necessary.
--
Mark Taylor Astronomical Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-9288776 http://www.star.bris.ac.uk/~mbt/
|