|
From: | Paul Kienzle |
Subject: | Re: mkoctfile, LINK_DEPS and -lhdf5 |
Date: | Sun, 15 Feb 2004 12:52:31 -0500 |
On Feb 15, 2004, at 11:58 AM, Per Persson wrote:
On Feb 15, 2004, at 01:32, John W. Eaton wrote:Also, I added FLIBS to the definition of LINK_DEPS in mkoctfile. Is there any case where that could cause a problem? We already link to libcruft, which depends on FLIBS, so I don't see how it could.Shouldn't LDFLAGS be added as well?In my case, I keep the fortan compiler separate from the standard locations.FLIBS specifies libg2c and LDFLAGS the non-standard path.
A small note, any standalone package created (windows or mac) needs to allow the possibility of users creating their own oct-files. I'm assuming this would be a separate development package which includes all the headers and in the case of windows, the lib files corresponding to the octave dll files. Paul Kienzle
[Prev in Thread] | Current Thread | [Next in Thread] |