Re: OS X distribution close to completion
Fabian Keil <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
Ian Silvester <[email protected]> wrote: > I now have a 3.0.19 OS X distribution built that, by rights, should work > on Leopard upwards and on all three architectures (PPC, i386 & x86_64). > It has so far been tested on Snow Leopard 64 bit and 32 bit, and on Lion > 64 bit. Great. > Before I make it generally available I have one more issue to resolve. > One tester pointed out that I am using the statically-linked PCRE that's > part of the Privoxy source code. I'm aware that it's de rigeur to > dynamically link to a more recent version. I've downloaded the PCRE > project, but (and please excuse my ignorance) I have a few questions: Note that while using a more recent pcre version is recommended, it's not a hard requirement and currently not done for the Windows and OS/2 binaries either. If you can use a more recent pcre version that's great, but it's not really a show-stopper and if it isn't trivial it could always be done later. > - if I build and install this in the default manner, will Privoxy's > configure automatically choose to link to it rather than the built-in > version? That's the idea. If it doesn't, you may have to specify some additional library or include paths to check, though. On FreeBSD I always set LDFLAGS and CPPFLAGS to make sure the pcre version installed through the ports is picked up. My privoxy-configure alias starts like this: LDFLAGS=-L/usr/local/lib CPPFLAGS=-I/usr/local/include/ CC=... ./configure ... For gcc46 this is not actually necessary, as it apparently looks at those paths by default, but it's required for all the other compilers I occasionally use, for example the system gcc 4.2.1, the system clang 3.0 (branches/release_30 142614) and pcc installed from ports. > - am I free to bundle the PCRE binary I build with my distribution? More recent pcre versions are licensed under 'THE "BSD" LICENCE': http://www.pcre.org/licence.txt which in FSF-speak is not actually the "original BSD license", but the "Modified BSD license" and thus GPL-compatible: http://www.gnu.org/licenses/license-list.html#ModifiedBSD So as far as the licenses are concerned, the binaries can be legally bundled. On most free operating systems bundling them would be considered bad form as it duplicates code and prevents separate updates, but of course OS X isn't a free operating system and if a bundled pcre version is what most users would expect, that's probably the way to go. > - crunch question - if I make a multi-architecture ('Universal' in > Macintosh parlance) PCRE binary, will my multi-architecture privoxy > binary link to the correct architecture at runtime? No idea, maybe that's documented somewhere on the pcre website. Fabian ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Ijbswa-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
signature.asc
(application/pgp-signature, 196 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8kBEwACgkQSMVSH78upWOqWwCePDcGswXCdSllw0n27Ei8yx8K EJ8AniCIxb7V5IkIWJZUeg1QK3Qtx7yR =IW3b -----END PGP SIGNATURE-----