On Tue, Oct 19, 2010 at 2:43 PM, Vincent Torri <[email protected]> wrote: > > > On Tue, 19 Oct 2010, Gustavo Sverzut Barbieri wrote: > >> On Tue, Oct 19, 2010 at 1:47 PM, Vincent Torri <[email protected]> >> wrote: >>> >>> >>> On Tue, 19 Oct 2010, Raphael Kubo da Costa wrote: >>> >>>> At Tue, 19 Oct 2010 16:31:38 +0200 (CEST), >>>> Vincent Torri wrote: >>>>> >>>>> On Tue, 19 Oct 2010, Raphael Kubo da Costa wrote: >>>>> >>>>>> Hey all, >>>>>> >>>>>> The installed Eina.h includes the files in the eina/ subdirectory via >>>>>> #include "foo.h" instead of #include "eina/foo.h" or #include >>>>>> <eina/foo.h>. >>>>>> >>>>>> Are people always expected to -I both eina-1's path and eina-1/eina? I >>>>>> thought #includ'ing <Eina.h> and -I'ing $PATH_TO_EINA-1 was enough, >>>>>> and the rest was details. >>>>> >>>>> use what >>>>> >>>>> pkg-config --cflags eina >>>>> >>>>> returns, and include *only* Eina.h. >>>> >>>> In this specific project, I was trying to stick to CMake and keep >>>> pkgconfig usage to a minimum. It is possible to follow your >>>> suggestion, however I was thinking of GStreamer, for example, which >>>> has a gst.h that includes headers in subdirectories, but whose .pc >>>> includes only the base directory. >>>> >>>> Doesn't it make more sense to keep the eina/ subdirectory "away from >>>> the public"? >>> >>> gstreamer has all its headers in $prefix/include/gstreamer-0.10/gst >>> >>> eina has its headers in $prefix/include/eina-1 for Eina.h and >>> $prefix/include/eina-1/eina for the other headers. That's almost the same >>> thing. The only difference is that Eina.h is not in >>> $prefix/include/eina-1/eina but in the parent directory. >>> >>> I don't know how cmake works, so i can't help you with that >> >> it does almost fine, but as with everything in life they screw with >> stupid bits by suffering from NIH syndrome... instead of using >> pkg-config they went with FindXXX.cmake, that is used by their >> macros... just because pkg-config is hackish on windows... yeah, >> window is broken, so let's break windows and others :-( > > well, i'm using pkg-config on Windows without any problem. Why do they think > it is hackish ?
because things on windows tend to be relocatable and the pkg-config guys had to hack it to change the prefix from .pc, which they consider hackish... but they don't provide a better solution :-/ -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
