On 9/19/13 4:47 PM, Alex Merry wrote: > On 19/09/13 15:14, David Matthews wrote: >> I don't know how useful it will be in general, though. I've done a >> quick look and pkg-config doesn't seem to be installed on several >> set-ups I looked at including Mac OS X and Solaris. The other problem >> is that it is going to require the PC files to be written into >> /usr/lib/pkgconfig or some other non-user-writable directory. One of >> the problems I was trying to work round was the fact that many users of >> Poly/ML are running on systems that are managed centrally and they don't >> have root access. It's this that makes shared libraries a problem >> because libpolyml can't be installed to /usr/lib or /usr/local/lib. All >> this means that anyone distributing code, such as HOL4 or Metit that are >> intended to be built with poly, can't rely on pkg-config. > > It should just be installed to $PREFIX/lib/pkgconfig; users can then > export the environment variable > PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH > before building the tool that uses Poly/ML, in much the same way that > they have to set > PATH=$PREFIX/bin:$PATH > (or supply an absolute path to poly). pkg-config will then find the .pc > file. > > pkg-config is mostly a Linux thing (although I suspect it's easily found > on *BSD systems), so it's not so useful for Windows or the proprietary > unices like OS X and Solaris.
A possible option would also be to generate a shell script, say poly-config, and install on the same path as poly which would accept the same options as pkg-config. The script could be generated in case the pkg-config is not available. This would solve the portability issue for non linux systems. > > Alex > _______________________________________________ > polyml mailing list > [email protected] > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml > Ramunas _______________________________________________ polyml mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
