[Ecls-list] Integrating Monolithic Static Libraries with asdf

Seth Burleigh seth at tewebs.com
Fri Mar 26 14:14:23 UTC 2010


It doesn't appear to use the :init-name keyword for static libraries.
Instead it just uses the default initialization name, init_lib_LIBRARY


The result of 
(asdf:make-build :library :type :lib :init-name
"library_init" :monolithic t :move-here "~/place/") , however, will use
the supplied init name while 

the result of (asdf:make-build :library :type :binary :init-name
"library_init" :monolithic t :move-here "~/place/") wont (itll use
init_lib_LIBRARY)



On Fri, 2010-03-26 at 09:56 +0100, Juan Jose Garcia-Ripoll wrote:
> As I think I explained some emails before (or maybe it was in the ASDF
> mailing list)
> 
> 
> (asdf:make-build :my-system :type :binary :monolithic :t :move-here
> "~/path/to/destination/")
> 
> 
> builds a replacement for your ASDF system consisting on 3 files, a new
> *.asd file for prebuilt-components, a *.fas file that you can load
> into your lisp and a *.a statically linked library that you can also
> use in other MAKE-BUILD operations.
> 
> 
> Juanjo
> 
> On Fri, Mar 26, 2010 at 6:46 AM, Seth Burleigh <seth at tewebs.com>
> wrote:
>         Recently ive built a  monolithic static library and have
>         loaded it into
>         a c program.
>         
>         
>         The problem is that the library is not registered with asdf.
>         So, if i
>         attempt to (require 'library), or to load another library
>         which depends
>         upon it from the c code, it'll rebuild the library from the
>         file system
>         because it doesn't know it has already 'loaded' it from the
>         monolithic
>         library. Is there any known solution to this?
>         
>         
>         
>         
>         
>         
>         ------------------------------------------------------------------------------
>         Download Intel® Parallel Studio Eval
>         Try the new software tools for yourself. Speed compiling, find
>         bugs
>         proactively, and fine-tune applications for parallel
>         performance.
>         See why Intel Parallel Studio got high marks during beta.
>         http://p.sf.net/sfu/intel-sw-dev
>         _______________________________________________
>         Ecls-list mailing list
>         Ecls-list at lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/ecls-list
> 
> 
> 
> -- 
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain) 
> http://tream.dreamhosters.com
> 






More information about the ecl-devel mailing list