On 1/21/06, Archaic <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 21, 2006 at 09:15:23AM -0600, Randy McMurchy wrote:
> >
> > prefix=%prefix%
> > exec_prefix=%exec_prefix%
> > libdir=%libdir%
> > includedir=%includedir%
>
> Most elegant would be to create a patch that introduces 2 or 4 new build
> vars (whether you want nss and nspr paths to be separated) and
> referencing them in the .pc files and then submitting upstream.
Agreed. There are a couple vars related generated in configure.
You've got MOZ_NATIVE_NSPR=1 if you pass --with-system-nspr and it
passes mustard.
However, everything it uses from nspr it gets from `nspr-config
--cflags` and `nspr-config --libs`. In build/unix/Makefile.in,
there's an ifdef MOZ_NATIVE_NSPR, then it runs nspr-config to find out
the LIBS and CFLAGS.
A good way here would be to add something like:
NSPR_INCLUDEDIR=$(shell $(NSPR_CONFIG) --variable=includedir)
NSPR_LIBDIR=$(shell $(NSPR_CONFIG) --variable=libdir)
They'd have to be a fall back to $(includedir) and $(libdir) if
MOZ_NATIVE_NSPR was not defined.
Then, you'd change the %includedir% and %libdir% in
$(MOZ_APP_NAME)-{nss,nspr}.pc.in to %NSPR_INCLUDEDIR% and
%NSPR_LIBDIR%. Then tack on a couple extra lines on the sed to
$(MOZ_APP_NAME)-%.pc.in in build/unix/Makefile.in.
Maybe I'll try to submit something upstream.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
