Re: Linking against a re-exported library
Re: Linking against a re-exported library
- Subject: Re: Linking against a re-exported library
- From: Scott Ribe <email@hidden>
- Date: Tue, 31 Dec 2013 11:24:01 -0700
On Dec 31, 2013, at 11:08 AM, Kyle Sluder <email@hidden> wrote:
> This was my first approach, but the PostgreSQL vendor only included
> static versions of libssl and libcrypto that are built for 32-bit Intel.
> (Grr!)
>
> I really don't want to make building PostgreSQL _and_ libssl _and_
> libcrypto part of the build process for building our bug tracker.
Understood. I build PG myself, and use the static libpq. Yet, at the same time, I use the dylibs of libssl and libcrypto. (This is for a custom system, not something where I have to worry about building installers and so on.)
You might, though, check out the build process for libcrypto and libssl. Open source projects range from trivial configure/make/install processes to a hellish rat's nest of dependencies. PostgreSQL is the trivial kind, absolutely no reason to avoid building it once in a while. If libssl & libcrypto are the same, then you could reconsider.
Also take into account that libpq for instance is not part of my usual build process at all. I build it very occasionally, when I deem the time right, then just copy the libpq.a into a folder in my project. FWIW, I do the same for tiff, jpeg, and bzip libraries.
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden