looking for the wrong header files when building prelude client apps

Hello all,

I just noticed that the header files that are intended for libprelude clients
contain references to a "config.h" file. For example:

src/include/prelude-thread.h (line 27):
---------------------------------------
#ifdef HAVE_CONFIG_H
# include "config.h"
#endif
---------------------------------------

Now, if a libprelude client is built using the GNU autotools then
it will most probably have its own "config.h" file. So, any #include
statement referencing a libprelude header file, will (re)include the
local "config.h" file. Is this the intented behaviour?

Appart from the "config.h" file, I also see references to a "common.h" 
file which might again be part of a client app. If these files contain 
information that is required when building a libprelude client,
then maybe they should have a "prelude-" prefix added to their names.

Cheers,

Dimitris Glynos
_______________________________________________
Prelude-devel site list
[email protected]
http://lists.prelude-technologies.com/mailman/listinfo/prelude-devel