Re: [Boost-build] Adding 3rd party dependencies in jam file

Subject: Re: [Boost-build] Adding 3rd party dependencies in jam file
From: Vladimir Prus (ghost_at_[hidden])
Date: 2010-03-21 08:48:46

Christian Henning wrote:
> Hi Vladimir, thanks for your reply.
> 
>>> 2. When linking the user needs to set up paths to all library files
>>> needed by unit tests. Also, he needs to state the name of the
>>> binaries, e.g. libjpeg.lib. Of course the system needs to deal with
>>> static and dynamic libraries.
>> How are the static and dynamic libraries named, in your case? I believe
>> there's no universal convention for windows.
> 
> Static libs in Windows usually end with ".lib", whereas dynamic libs
> have ".dll". I bet you know that already. 

The problem is that import libraries also have ".lib" -- so import libs
and static libs must differ is something else.

Though, right now there are
> three supported image formats that are dependent on 3rd party libs.
> Here is a list of all 3rd party libs my unit tests need to have
> available:
> 
> - libpng also needs zlib
> - libjpeg
> - libtiff
> 
>> maybe we can approach the problem from another end -- do you happen
>> to know, for each third-party dependency:
>>
>> - The name of a header file that it surely has
>> - Name of a static library
>> - Name of a shared library
> 
> After parsing my source code these are the header files:
> 
> png: png.h, needs zlib.h internally
> jpeg: jpeglib.h
> tiff: tiff.h, tiffio.h, tiffio.hxx
> 
> These names are static and probably wont change with the users.
> 
> Now, binaries are a bit more problematic and this is why I suggested a
> makefile approach since here names will change all time. Here is what
> I use on my Windows box:
> 
> png: libpng.lib and libpng.dll
> jpeg: libjpeg.lib and libjpeg.dll
> tiff: libtiff.lib and libtiff.dll
> 
> Sometimes when users use prebuilt libraries the file name can have
> version numbers in them.

I see -- this means user has to be able to adjust the base name of the
library that is used.

>> If you tell me that, and tell me the URL of your library, I can provide a
>> 'seed' solution.
> 
> Thanks a lot for your offer here is the link:
> 
> http://gil-contributions.googlecode.com/svn/trunk/gil_2/
> 
> The test folder is here:
> 
> http://gil-contributions.googlecode.com/svn/trunk/gil_2/libs/gil/io_new/test/

I'll take a look at get back to you.

- Volodya