 |
 |
On 2004 Dec 27 , at 21.13, Tim Jenness wrote: > * dipso > - autobuild system ignores link dependencies > so I've made TRN a build dependency for kaplibs The link dependencies shouldn't be required for just building. The time the link dependencies _are_ required, is where there's a <build option='link'>Y</build> declaration for a component X -- that is, to build X, you need to have built Y, and because you're going to link against it, you must also have built all of Y's link dependencies. I got the impression that Steve handled those in whatever it was that generates the list of dependencies for autobuild (and I was impressed, because it took me a couple of goes to get these things right in GenerateDependencies). That is to say, that if TRN isn't a direct build dependency for kaplibs (that is, kaplibs needs include files from it), but only a link dependency, then it shouldn't be declared as a build dependency, and this might be pointing to an error in the generated autobuild configuration. > * sgmlkit > - depends on dvi2bitmap but that dependency is not specified. > I assume Norman has a reason for not doing that. I've modified this, but haven't committed it. I spent a little while before the New Year break fixing this and trying to get the sgmlkit dist target working. It's more fiddly than I expected, and I think we're going to have a few boring troubles when we come to look more carefully at those. I'll finish this off today. > * dvi2bitmap > Fails on 64bit linux due to link problem Yes -- rather aggravatingly, it appears that a library it needs is built and installed as a static library only, in such a way that it can't be linked in to a shared library on some platforms (if I recall correctly). Grr. I'm trying to find a non-hacky way of detecting that. See you, Norman -- ---------------------------------------------------------------------- Norman Gray : Physics & Astronomy, Glasgow University, UK http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk