On Aug 30, 2006, at 4:00 PM, skaller wrote: > BTW: pls post to the list.
Gak. Sorry. I tend to hit Reply, not Reply All, and forget to add the Cc: (Incidentally, where is the 'Certification' in email CCs?) By "everything," I meant everything Felix (or the module) needs, specified as search paths within the flx_pkgconfig. For Felix modules this would be an extra field, such as use_path: which would substitute for setting the path variable on the command line to flx_pkgconfig (a substitute to modifying $PATH) and would essentially operate like the argument --path= . For systems that have standard directories (POSIX), it might be useful to allow a '-' or 'not' flag to keep out certain directories, such as use_path: not=/usr/bin:usr/include:usr/lib if you have a library you want to avoid. For mpi, there is an arbitrary precision library typically installed as libmpi.a and you might want to avoid making ld go over (and rejecting) those worthless symbols. > The problem is how to create the *.fpc files: > > Here is config/mpi.fpc: > > cflags: -I/usr/lib/mpich/include > provides_dlib: -lmpi > provides_slib: -lmpi > > The cflags are correct .. the libraries aren't yet, > a -L switch is required. Problem is, the libraries > aren't called > > libmpi.so > > they're actually called: > > /usr/lib/mpich/lib/libpmpich.a > /usr/lib/mpich/lib/shared/libmpich.so > > This is because the libraries reflect the MPI implementation model. > There are more of them .. but who would ever guess these locations? When configuring mpich2, the configure script (or Debian package) should have logged the install sub-location--the part that comes after --prefix= . Couldn't you search for $prefix and use that setting? >> In any case it might also solve the problem of erasing new header >> locations every time you build: this way you could pull the locations >> from a config file that is separate from the build directory, if it >> exists or the user has chosen to keep it, and go from there. > > Yes, we need to have some 'persistent' config stuff. > The question is, exactly how? What about adding a flx-config variable, such as: FLX_CONFIG_FILE=/full/path/to/config/file/flx_config.fpc or FLX_CONFIG_DIR=/full/path/to/config/file Felix already stores flx.fpc in the /usr/local/lib/felix/felix- [version]-[build] directory; it might be nice to relocate that to, say, the user's home directory under ~/.felix , then store all module files there. (Keeping the config in a system directory prohibits me-- and any felix package install--from modifying it, unless I have root authority.) Then module files could include that directory in the use_path: variable I mentioned above or by default their current directory '.', so flx_pkgconfig could search it for other modules. -Pete ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Felix-language mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/felix-language
