the configure.in checks already try to use pkgconfig unless you specify the paths manually in the configure line. the configure line is mostly still around in case we want to build nss in statically iirc.
Jeff On Fri, 2003-11-07 at 13:17, JP Rosevear wrote: > On Wed, 2003-11-05 at 19:30, Not Zed wrote: > > On Thu, 2003-11-06 at 02:17, JP Rosevear wrote: > > > On Wed, 2003-11-05 at 09:16, Frederic Crozat wrote: > > > > Le mer 05/11/2003 � 10:19, Harry Lu a écrit : > > > > > I was able to build HEAD one week or so before with NSS 3.7.1 and NSPR > > > > > 4.2.2, but these days I got the following errors in addressbook: > > > > > > > > According to : > > > > http://www.mozilla.org/projects/security/pki/nss/release_notes_32.html#migration > > > > > > Chris, Michael, Jeff - is there any good way to detect this in > > > configure.in and act accordingly? > > > > I dunno about 'good' way (or even if good is ever possible with > > autoconf), but we could probably just try one set of libs then the > > other and go with what we find? > > Frederic pointed out that for mozilla >= 1.1 there are nss pkgconfig > files. Could we just be using these? I don't see much of a need to > build against 1.0. > > -JP -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
