On Fri, Jun 01, 2007 at 09:45:58PM +0200, Alexander Sack <[EMAIL PROTECTED]> wrote: > On Fri, Jun 01, 2007 at 09:26:04PM +0200, Mike Hommey wrote: > > On Fri, Jun 01, 2007 at 09:18:46PM +0200, Alexander Sack <[EMAIL > > PROTECTED]> wrote: > > > On Fri, Jun 01, 2007 at 09:04:36PM +0200, Mike Hommey wrote: > > > > On Fri, Jun 01, 2007 at 08:49:17PM +0200, Alexander Sack <[EMAIL > > > > PROTECTED]> wrote: > > > > > > So its actually not used in the wild, but its ment to work, so lets > > > please fix it. Any idea, why its not replaced when created from > > > mozilla-config.in ? > > > > Look at the rule creating the -config file in build/unix/Makefile.in. > > It does sed (...) -e "s|%includedir%|$(includedir)|" (...) > > > > I put 2 %includedir%'s in one line... > > > > As a workaround, I'd suggest you to use pkg-config instead. > > > > I won't fix this bug before taking care of stable security updates. > > > > pkg-config has a different semantic and it probably doesn't have info > about every single component shipped by xulrunner. > > For instance getting the include dir for cookie component, how can i > achieve that. With xulrunner-config I would do > > xulrunner-config --cflags cookie
Except for the javascript and nspr components, which has their own pkgconfig file, all components use /usr/include/xulrunner/$component (as you can see in the xulrunner-config file). For instance, epiphany's configure script just gets /usr/include/xulrunner from a pkgconfig file and adds the component to it. Anyways, that's just another broken way to do it. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
