[cmake-developers] Adding the OpenRAVE library module

[Rosen Diankov]

about import targets and the static library export problem:

it would be great if there was an option for exporting that will set
static libraries to be ignored. i'm not comfortable with managing all
the dynamic libraries and putting them into LINK_INTERFACE_LIBRARIES.
OpenRAVE contains a lot of 3rdparty libraries stored in source in case
users don't have the system install versions, therefore the same
logical target can switch how it is linked. Although it is possible to
manage this list, it will be much easier to have cmake help out ;0)

rosen,

2011/4/15 Brad King <brad.king at kitware.com>:
> On 04/15/2011 09:48 AM, Rosen Diankov wrote:
>> From what i understood in the documentation, I would have to set
>> LINK_INTERFACE_LIBRARIES to all the non-static install libraries
>> right?
>
> Yes.  It should list the libraries that applications should link when
> linking to your library.  If your public headers include a public
> header from another library then that library should be listed.
>
>> for the registry, the name could just be the version string right?
>
> Yes, if you don't care about multiple copies of the same version
> being installed on the same system ;)
>
>> so i would have
>>
>> "0.3.0" = "C:\Program Files\OpenRAVE-0.3"
>>
>> where the configuration file is in:
>>
>> C:\Program Files\OpenRAVE-0.3\lib\cmake\openrave-0.3
>
> It should be the path to the directory containing the config file:
>
> "0.3.0" = "C:\Program Files\OpenRAVE-0.3\lib\cmake\openrave-0.3"
>
> You can test it with the nightly build I linked earlier.
>
> -Brad
>