You can include a custom built libcurl3.dylib file with your application and
then make sure your application links against it relative to your
application's install path.

Not sure what OS you are targeting but on a Mac you can see which libraries,
versions, and paths to libraries that your app is referencing by running
`otool -L my-app/binary`

...and you can change any one of those paths to reference a libcurl.dylib
that you include with your application by using `install_name_tool -change
/usr/lib/libcurl.dylib /path/to/my/libcurl3.dylib`

Nick

On Thu, Jan 7, 2010 at 11:19 AM, CP YEH <ntdev74_at_gmail.com> wrote:

> Hi All,
>
> I have written a program that uses libcurl but I need some advice on
> how I should bring it to customer machines.
> In other words, if I build my program with libcurl3, it will only work
> on machines that have libcurl3. I noticed that there are machines out
> there that have different versions of libcurl shared library. Normally
> it's either libcurl.so.3 or libcurl.so.4 so I want to know how I
> should tackle this problem because I can't really ask customers what
> libcurl version they have on their machines.
> Should I just build statically but I kind of not want to do that but I
> would like to hear some feedback from those of you who have faced this
> issue before. Thank you.
>
> YEH
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
>

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-01-07