RE : debian and gentoo branches [to be removed]

[Xavier Oswald]

On 11:03 Tue 17 Nov     , PICCA Frédéric-Emmanuel wrote:
> > > As you said before some libraries are non compatibles all together.
> > > Must we  have a sort of .so number for the lisaac libraries ?
> 
> > We cannot !
> > Lisaac uses global compilation, you cannot load .so or wathever extension module
> > in a Lisaac code.
>  
> ok so we must wait for user to report bug saying my application use libA (1.0.0) + libB (1.0.1) do not compile.

When compiling using debug mode, you will have the prototype failing listed.

@ THE TEAM: what do you think about using the LIP or whatelse to say the file X
crashes + this file is part of the library Y. Something like that.
 
> how can we ensure that everything library installed on the system are compatible ?

The Lisaac syntax is now fixed so you will be able to use any library. It will
not depend of Lisaac. But we have to take care about bindings compatibilities.

> maybe we can think about a dh_lisaac that help use generate the right lisaac::Depends use to compute the binary package
> dependencies.

Good point, at the final 0.4 release, we could think about that.

> PS: I would like to use lisaac in real life for some scientific computation, but if I can not generate
> a libxxx.so library usable from C or C++ programs, it is pointless to me :((.

I see. But using separate compilation render the code less optimized, you will
loose the fact of doing inlinning and such.

What you want is to be able to write a library in Lisaac and generate a .so
file.

@ BENOIT or other, Could we allow such a thing only for libraries maybe... ?

Greetings,
-- 
 ,''`. Xavier Oswald                         | xoswald at debian.org         
: :' : Software Engineer at CALDERA GRAPHICS | http://www.caldera.eu   
`. `'  GNU/LINUX Debian Developer            | http://www.debian.org                
  `-   Isaac Project Developer               | http://www.lisaac.org