Le Thu, 9 Aug 2007 09:17:28 +0200, "kRAkEn/gORe" <[EMAIL PROTECTED]> a écrit :
> hey gimpel ! > thanx for the info, i've fixed this by creating a symbolic link, but i > think that > could be created in the ebuild isn't it ? > I think at it will be better to follow gimpel's advice. You must modify your build system to work with pkgconfig. This will work with any distribution. To make a symlink in lash ebuild in order to solve a problem with a buggy xyz build system is not a fix but a workaround -- a bad workaround in fact. And this will work only in gentoo. I have no reference on how to implement pkgconfig in Makefile.am and configure.ac. Maybe pkgconfig doc or website can help you. Another way can be to take a look in Makefile.am and configure.ac from another program (it is was I do most of the time. When it doesn't help, I take a look in the doc and search on google). Cheers, Dominique > On 8/7/07, Thomas Kuther <[EMAIL PROTECTED]> wrote: > > On Di, 07.08.07 12:17 "kRAkEn/gORe" <[EMAIL PROTECTED]> wrote: > > > > > i've emerged lash (and ladcca in turn) and i stated that the headers > > > are actually in > > > > > > /usr/include/ladcca-1.0/ladcca/* > > > /usr/include/lash-1.0/lash/* > > > > > > but in other distros they are > > > > > > /usr/include/ladcca/* > > > /usr/include/lash/* > > > > > > this way one can't use a single #include statement in his source code > > > to be compiled in other platforms. > > > > > > could the ebuilds be changed or at least make a symbolic link by > > > default ? > > > > > > thanx > > > > > > lucio > > > > Yo kunitoki! :) > > > > This has to be fixed upstream, as the ebuild runs nothing else but a > > "make install" - so this seems to be intended. > > > > Simply use gcc `pkg-config --cflags lash-1.0` or something like that, > > then #include <lash/lash.h> etc should work too. > > > > Cheers. > > > > > -- Dominique Michel -- N.B.: Tous les emails que je reçois sont filtrés par spamassassin avant de me parvenir.
