Hi Rob, I've been away and I'm now just trying to catch up.
On 23/04/2014 17:13, Rob Arthan wrote:
I have a couple of comments and a query about polyc (which seemed particularly attractive on Cygwin, where there seems to be quite a long list of libraries you need to know about if you are going to call the linker directly). The comment is that the help text is a bit misleading as it has more functionality than just compiling and linking a source file, e.g., you can pass it the name of an object file and it will link it with libpolymain and libpolyml.
I take it you mean the text that gets printed with polyc --help. The man page contains a bit more. Any suggestions for a suitable, brief replacement?
The query relates to the fact that polyc doesn’t do anything with LD_RUN_PATH (or DYLD_LIBRARY_PATH on Mac OS). Am I right in thinking that libpolyml will now always be statically linked so that you no longer to need to tell the dynamic linker where to find it? (For Poly/ML versions 5.5 and earlier the ProofPower makefiles that I am updating used to create an executable that linked libpolyml dynamically.)
What exactly does LD_RUN_PATH do and how does it relate to LD_LIBRARY_PATH? With the default setting of --disable-shared there should not be any need to specify the location of a shared library. Of course, if --enable-shared is given explicitly then there will be, but I would have thought that that would only be used when packaging for a system where the libraries were being installed to the "standard" location.
polyc is really a work in progress and I'm happy to receive suggestions to improve it.
On a more general note, I think it's time for a new release of Poly/ML. Unless there are any immediate bug reports I'm planning to release the current SVN as 5.5.2.
David _______________________________________________ polyml mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
