curl-library
Re: Statically linking libcurl in Mac OS X.
Date: Tue, 8 Mar 2005 15:44:07 -0500
Heh. I wish I could.
However due to a bug in OS X a CFM app (old-style carbon) won't look
for private frameworks inside its bundle (found that issue before with
another one). So I'll need to build a bundle itself and load it
manually from inside the app.
Would it be very difficult to modify the makefile to build a bundle? (I
would add my code in it and be done with the problem).
Our app is Panther & up only, so we don't need to be compatible with
10.2.8 fortunately.
Thanks for the helpful tidbits though.
On Mar 8, 2005, at 15:27 , Matt Veenstra wrote:
> I need to use a newer version of libcurl than the one included in OS
> X 10.3.8 (7.10.2) in my application, but I can't have my application
> install it over the OS one (we want the application to be
> self-contained and not have to install anything in unix places). Also
> my application is old CFM compiled with CodeWarrior so I'll need to
> put the libcurl stuff in a bundle instead of inside the application
> itself.
>
> Has anyone been before in a similar situation, or for whatever reason
> created a bundle that contained the libcurl statically linked to it?
> Any pitfalls to be aware of or any advice? Or anyone has a sample
> Xcode project that compiles the libcurl? (I could work on that quite
> easily)
>
>
> Oscar,
>
> In the download is a makefile to make a libcurl.framework. This is
> what we use. So we distribute our application and link to the
> framework sitting next to it.
>
> This is what I would recommend. The other thing is if you need
> backward compatibility then you will want to master on 10.2.8. So
> the libssl links properly. Or have enough unix skills to install the
> old ssl libs, which I do not.
>
> Hope that helps,
> Matt Veenstra
> Tribeworks
Received on 2005-03-08