Re: [E-devel] Eflpp

[Andreas V. <li...@br...>]

Am Tue, 07 Aug 2007 20:46:24 +0200 schrieb tr1gun:

> Hello,
> 
> i got some design questions about eflpp.
> Wouldn't it perhaps be better to split out ewl/etk and some other
> stuff, so you don't have to recompile/bump the whole package if
> something changes in only a small part of the library?

Hello,

eflpp is currently in "proto" that means it's in protoype state. The
library design may change in future, but now it's easier to develop all
stuff in a big library. Maybe mickeyl could say more about this topic.

> The other thing i want to know. Why isn't the path used in the include
> path? So you could use #include <ewlpp/someheader.h> or #include
> <ewlpp/esmart/someheader.h> in your application. This way imho it
> would be easier to split the single files into several smaller ones
> e.g. one file for each class and you wouldn't have to prefix all
> files.

Currently the header path works with installed and uninstalled
libraries. As above this may change if eflpp is split perhaps in future.

regards
Andreas