Re: Mex generator

From: ianfasel (ianfasel_at_[hidden])
Date: 2005-11-15 23:50:13

Thanks Volodya, using <source> works. I also tried your suggestion of using:
generators.register-linker mex.mex : CPP C OBJ SEARCHED_LIB STATIC_LIB IMPORT_LIB : 
MEX ;
 
This basically worked the same as before -- and still did not propagate thelibrary 
features. :-(

Also, another question: is there some way to require that when building with gcc or 
darwin, the library I am trying to link to *must* be the one built using the gcc-3.3 (or 
darwin-3.3) toolset? This is because the MEX files are really shared libraries that must use 
the same ABI as Matlab, which uses gcc-3.3. However the other binaries (non-MEX) in this 
project must use gcc-4.0, because they need to be 64-bit. This means that when I run 
bjam it needs to build two versions of the library -- one using gcc-3.3 andone using 
gcc-4.0.

> > # I think all this stuff is slightly (or completely) wrong, as it doesn't
> > seem to work right. 
> 
> What exactly does not work right?

I thought that my problems were because this is not the proper way to import features. I 
still wish that generators.register-linker made <library> linkflags etc. become available. I 
think that mex probably is sufficiently similar to a linker, so it should work.

> 
> > import toolset : flags ; 
> > flags mex.mex OPTIONS <debug-symbols>on : -g ;
> > flags mex.mex OPTIONS <optimization>off : ;
> > flags mex.mex OPTIONS <optimization>speed : -O ;
> > flags mex.mex LINKPATH <library-path> ;
> > flags mex.mex INCLUDES <include> ;
> > flags mex.mex FINDLIBS-ST <find-static-library> ;
> > flags mex.mex FINDLIBS-SA <find-shared-library> ;
> > flags mex.mex LIBRARIES <library-file> ;
> 
> HTH,
> Volodya

Thanks,
-Ian