coapp-developers team mailing list archive

[Olaf van der Spek <olafvdspek@xxxxxxxxx>]

2010/4/16 Pierre Joye <pierre.php@xxxxxxxxx>:
> I'm not sure the development files should end in a common directory.
> As it has been mentioned in this thread, it will not be possible to
> have multiple versions of a library. However I'm really not sure that
> the development files and the distribution package should follow the
> same rules. They have very different goals.

> Having a common (or global) include directory can also introduce
> problems. They cannot be solved without introducing other rules
> (version numbering rules for ABI/API compatibility, add extra
> directory like include/zlib12/). But these rules may force developers
> to modify their code for windows only, the #include part. That's a
> small change but yet another one.

IMO changing includes is not an option.

> I would rather put them in the application directory instead and add
> the right path to the include/lib paths (or copy/symlink, depending on
> the developer needs or configuration).

What is the reason we're talking about paths already? Isn't this an
implementation detail?

Olaf