From: Jennifer A. <jm...@CO...> - 2008-08-01 12:09:21
|
Dear Experts, I've been pecking away at the configure scripts and thinking about the logic in them. There's a lot of cruft in there -- support of "historical" stuff that is no longer relevant, and outdated platform dependencies. It seems to me that the default behavior should be to look for a directory called "supplibs" (in ./ and ../) and if not found then go hunting in the system for the required libraries, creating a dynamically linked executable. To create a more portable build, the configure flag "--disable-shared" will stick with what's in the "supplibs" directory and use the "-L/ga_supplb_path/ libname.a" syntax instead of -L/path -lname" . The "--with-PACKAGE" configure options will be used to guide the hunting for a specific library, something like --with-hdf=/opt/local (and then it will look for /opt/local/lib/libmfhdf.a and /opt/local/include/mfhdf.h) Doesn't that seem more reasonable? Jennifer -- Jennifer M. Adams IGES/COLA 4041 Powder Mill Road, Suite 302 Calverton, MD 20705 jm...@co... |