RE: [Corelinux-develop] Frameworks

[Frank V. C. <fr...@co...>]

FROM: Christophe Prud`homme
DATE: 08/21/2000 15:06:37
SUBJECT: RE:  [Corelinux-develop] Frameworks
               

>> No, I don`t want to move clfw or any of the abstractions (Library Load,
>> Persist, etc.) that will go with it.
>>
>> When I create the FunctionLibraryLoad implementation, though, it should
>> be as separate as clfw is to corelinux.

> I see
> shouldn`t be a problem to achieve that
> however they will be source-packaged in clfw
> but for the binary packages we can create separate packages for each component
> actually that`s a good idea I think to modularise the frameworks as much as 
> possible, it is unlikely that all components will be all used 
> 
> May be it is also interesting to have all the components merged also in one 
> lib.
> So we would have
>   - separates modules to provide lightweight services
>   - one big lib to provide them all

No, thats not what I meant. Source package for clfw contains all main
framework utility, and all abstract frameworks.


And each framework implementation is separate. So for example, I might
have on my machine:

libcl++.so	(core)
libclfw++.so	(core framework and abstractions)
libclfwfl++.so	(function library load implementation)
libcpfl.so	(Christophe Prud`homme's function library load
implementation)

we provide (from a release perspective)

libcorelinux
libcoreframeworks
libfunctionlibraryload

capice?



-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package