troy d. straszheim wrote:
> Ingmar Vanhassel wrote:
>> Excerpts from troy d. straszheim's message of Thu Oct 29 23:18:12
>> +0100 2009:
>>> I haven't forgotten about LIB_SUFFIX. It is footnoted in the
>>> exported targets section of the docs:
>>
>> I meant the cmake/ subdirectory, to avoid clutter
Ingmar Vanhassel wrote:
Excerpts from troy d. straszheim's message of Thu Oct 29 23:18:12 +0100 2009:
I haven't forgotten about LIB_SUFFIX. It is footnoted in the exported
targets section of the docs:
I meant the cmake/ subdirectory, to avoid cluttering the library
directory with .cmake files
Excerpts from troy d. straszheim's message of Thu Oct 29 23:18:12 +0100 2009:
> Ingmar Vanhassel wrote:
> > Excerpts from troy d. straszheim's message of Thu Oct 29 21:03:01 +0100
> > 2009:
> >> Brad King wrote:
> >>> troy d. straszheim wrote:
> Michael Jackson wrote:
> > This is THE SING
Ingmar Vanhassel wrote:
Excerpts from troy d. straszheim's message of Thu Oct 29 21:03:01 +0100 2009:
Brad King wrote:
troy d. straszheim wrote:
Michael Jackson wrote:
This is THE SINGLE IMPROVEMENT someone could make for those of us
using CMake and are dependent on the boost libraries.
I di
troy d. straszheim wrote:
> if you link to
> boost_threads-mt-shared, for instance, with the installed exports you
> automagically get -pthread and friends, but with the noninstalled
> exports you don't. Is this expected?
It should work for both. Make sure that the export() command for a
target
Ingmar Vanhassel wrote:
>> Yes. This is a great cmake feature. Boost.CMake now uses this to
>> install a $PREFIX/lib/Boost.cmake file.
>
> Can we agree on $PREFIX/lib$LIB_SUFFIX/cmake/Boost.cmake please?
>
> Also, some users may want to install multiple versions of boost, so I'd
> shove $BOOST_
Excerpts from Ingmar Vanhassel's message of Thu Oct 29 21:11:16 +0100 2009:
> Also, some users may want to install multiple versions of boost, so I'd
> shove $BOOST_VERSION in the filename too.
On that note, it would be a good help if our includes were installed in
a versioned directory.
--
Exhe
Excerpts from troy d. straszheim's message of Thu Oct 29 21:03:01 +0100 2009:
> Brad King wrote:
> > troy d. straszheim wrote:
> >> Michael Jackson wrote:
> >>> This is THE SINGLE IMPROVEMENT someone could make for those of us
> >>> using CMake and are dependent on the boost libraries.
> >> I did s
Brad King wrote:
troy d. straszheim wrote:
Michael Jackson wrote:
This is THE SINGLE IMPROVEMENT someone could make for those of us
using CMake and are dependent on the boost libraries.
I did some work on this. CMake exported targets are really cool. This
doesn't solve the entire FindBoost.c
troy d. straszheim wrote:
> Michael Jackson wrote:
>> This is THE SINGLE IMPROVEMENT someone could make for those of us
>> using CMake and are dependent on the boost libraries.
>
> I did some work on this. CMake exported targets are really cool. This
> doesn't solve the entire FindBoost.cmake pr
So the problem I see with this is that I still need to know "a priori"
what boost libraries are available on the system so exporting the
targets really doesn't help much, at least not me.
In your example (quoted below) what happens if I don't have the shared-
debug of boost-thread but instead
Michael Jackson wrote:
This is THE SINGLE IMPROVEMENT someone could make for those of us using
CMake and are dependent on the boost libraries.
I did some work on this. CMake exported targets are really cool. This
doesn't solve the entire FindBoost.cmake problem, but it is easy.
http://sodi
12 matches
Mail list logo
