On Thu, 15 Nov 2007 14:00:44 -0600, Simon L. Nielsen <[EMAIL PROTECTED]>
wrote:
On 2007.11.11 18:42:08 -0600, Jeremy Messenger wrote:
While I am here, I am wondering why we don't have openssl.pc import and
install (maybe /usr/libdata/pkgconfig)? I think, OpenBSD does install
openssl.pc. I think it would be nice if FreeBSD has openssl.pc too for I
don't have to add hacks in ports tree to workaround of openssl.pc
doesn't
exist.
It's not intentionally that the .pc files are not installed.
From what I can see the .pc files are generated and not just
distributed with OpenSSL and installed. Since we in the base system
doesn't use the OpenSSL build framework/toos somebody(tm) needs to
find a good way to do this with our build framework.
Ah, I see now that it uses Makefile to generate three *.pc files. I don't
know exactly how our build framework works. Is it possible to import the
*.pc files on your own by copy from Makefile or you prefer to use
openssl's Makefile?
I will try to have a look at this at some point in a not too distant
future, but no promises of when. If it's important to anybody,
patches are accepted :-).
Cool thanks!
When we have these *.pc files installed, then I am thinking about tweak in
ports/Mk/bsd.openssl.mk by add something like
PKG_CONFIG_PATH=/usr/libdata/pkgconfig:${LOCALBASE}/libdata/pkgconfig in
the WITH_OPENSSL_BASE area. I don't know if it will working yet, but we
will see.
--
After thinking about that more... One thing that got me a bit worry about
get complicate. If there is other stuff in our base system also need to
install *.pc file. Let's say bind9.pc (I make up). When a user want to use
OpenSSL from base system but want to use bind9 from ports rather than base
system, then that PKG_CONFIG_PATH won't work very well unless we rename
the name of *.pc file to something like openssl-base.pc. I don't know
which we should:
1) Forget about install *.pc files, hack in ports tree.
2) Go ahead change the name of *.pc file and install these,
then add simpler hack in ports tree.
3) Do anyone have any better suggest?
I personal like #2, because it is a lot easier to hack in configure to
change the name from openssl to openssl-base than #1 way like I did with
net-p2p/transmission/files/patch-configure .. But... I am up for the vote.
:-)
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED]
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
