Hello, On Tue, 19 Jun 2012, Michael Orlitzky wrote: >On 06/19/2012 04:40 PM, walt wrote: >> I'm trying to build an xfce4 applet that's not in portage. For >> reasons I don't understand there are some standard gnome headers >> that don't get pulled in during the configure process, like orbit, >> libbonobo and libbonoboui. >> >> I edited the autoconf.in to check for those standard libraries, >> and it did partly work. The generated makefiles now have correct >> entries like LIBBONOBO_CFLAGS. >> >> The problem is that those flags are never used during the compile >> phase. So, anyone know how make that extra step happen?
Adjust Makefile.am / .in to actually use $(LIBBONOBO_CFLAGS) in those rules (or all if unsure) where they are needed. Have a look in the info documentation of automake/autoconf, esp. at the samples. >(no, nobody really understands autotools) I do. It's just m4 generating shell-scripts (plus some other easily understood bits) from templates. And all is quite well documented. Next, you'll tell us cmake/qmake/smake/scons/bjam etc.pp. ad nauseam are better understood and documented and what you have to do to adjust stuff like above. Yeah sure. I've been building stuff for 11+ years now, most for a 99'ish platform. In and after say '05 until '10. Believe me, I had to adjust stuff a lot. And autotools was _BY FAR_ always the easiest to do so, almost always just set/export a variable for configure and *tada*. Adjusting min-version of autoconf/-make to my "too old" version and running autoreconf was occasionally needed. Sure, if requirements for a lib weren't met, the stuff wouldn't build, but not because of the autotools or their generated makefiles, but just because the lib would not fit. No such luck with the other build-systems. With some of above mentioned "build-systems" you have to adjust _system_ files to get them to DTRT. BTDT. With the autotools, you could alternatively just use CFLAGS += $(pkg-config --cflags libbonobo-2.0) LDFLAGS += $(pkg-config --libs libbonobo-2.0) in your Makefile or the corresponding CFLAGS="$CFLAGS $(...)" in an ebuild or .spec or debian/rules or whatever. Piece of cake. (and the same for -activation if needed). -dnh -- > Noooo.... Not "She offered her honor, he honored her offer"? ...and so all evening he was honour and offer. -- known
