On 04/20/2010 09:40 PM, Benoit Thomas wrote:
> On 2010-04-20 03:27, Michael Hertling wrote:
>> On 04/19/2010 10:07 PM, Benoit Thomas wrote:
>>
>>
>>> I'm using an external library which is already compiled. I have wrapped
>>> the library in a MyLib.cmake and use it in cmake as an imported libr
On 2010-04-20 03:27, Michael Hertling wrote:
On 04/19/2010 10:07 PM, Benoit Thomas wrote:
I'm using an external library which is already compiled. I have wrapped
the library in a MyLib.cmake and use it in cmake as an imported library.
It works fine, but since the include line uses relative
On 04/19/2010 10:07 PM, Benoit Thomas wrote:
> I'm using an external library which is already compiled. I have wrapped
> the library in a MyLib.cmake and use it in cmake as an imported library.
> It works fine, but since the include line uses relative path, it changes
> from projects to project
Am Montag, den 19.04.2010, 16:07 -0400 schrieb Benoit Thomas:
> Hello,
>
> I'm using an external library which is already compiled. I have wrapped
> the library in a MyLib.cmake and use it in cmake as an imported library.
> It works fine, but since the include line uses relative path, it changes
On 19. Apr, 2010, at 22:07 , Benoit Thomas wrote:
> Hello,
>
> I'm using an external library which is already compiled. I have wrapped the
> library in a MyLib.cmake and use it in cmake as an imported library. It works
> fine, but since the include line uses relative path, it changes from proj
Hello,
I'm using an external library which is already compiled. I have wrapped
the library in a MyLib.cmake and use it in cmake as an imported library.
It works fine, but since the include line uses relative path, it changes
from projects to projects and in some case it looks just wrong.
I w
