Mueller-Roemer, Johannes Sebastian wrote:
> produces a file containing:
> IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE
> "${Boost_COROUTINE_LIBRARY_RELEASE}"
You need to make sure policy CMP0022 is NEW for the
BUILD_INTERFACE to be handled correctly. Unfortunately
there is no warning in this case.
Andrew Maclean wrote:
> Is this a reasonable approach to using cx_11 features on multiple
> platforms? The issue is that I think you need to manually select the MSVC
> compiler version that supports these features target_compile_features only
> works for gcc.
Correct, I'm no confident I can maint
It appears that wasn't really the issue, but rather that I had my CMake minimum
version set to 2.8.11 and not 2.8.12.
Is there a cleaner solution for the "debug" and "optimized" keyword issue than
using individual library variables?
--
Johannes S. Mueller-Roemer, MSc
Wiss. Mitarbeiter - Interact
On 11/25/2014 02:31 PM, Mueller-Roemer, Johannes Sebastian wrote:
It appears that wasn't really the issue, but rather that I had my CMake minimum
version set to 2.8.11 and not 2.8.12.
cmake_minimum_required(VERSION 2.8.12) sets policy CMP0022 to NEW
because the policy was introduced in 2.8.12
Mueller-Roemer, Johannes Sebastian wrote:
> It appears that wasn't really the issue, but rather that I had my CMake
> minimum version set to 2.8.11 and not 2.8.12.
See the reply from Nils and the documentation link I posted previously.
> Is there a cleaner solution
> for the "debug" and "optimi
For clarification:
As an imported target can't have debug and optimized keywords, I can't simply
use
$ $
But have to do
$:
${Boost_COROUTINE_LIBRARY_DEBUG}
${Boost_CONTEXT_LIBRARY_DEBUG}
${Boost_SYSTEM_LIBRARY_DEBUG}
>
$<$>:
Mueller-Roemer, Johannes Sebastian wrote:
> For clarification:
>
> As an imported target can't have debug and optimized keywords, I can't
> simply use $
> $ But have to do
> $ $<$:
> ...
Yes, but for the user of the target, it's just
target_link_libraries(mytgt Boost::Coroutine)
This is acade
Actually, I'm using this to make a static library that uses boost useable via
find_package without having hard-coded paths inside it and my Config.cmake
contains a find_package(Boost 1.56 EXACT REQUIRED COMPONENTS coroutine context
system). So it isn't exactly only academic... Yes, it would be s
> Basically package source generator (in the sense of RPM, DEB and alike)
> are unsupported.
I hoped that the CPack software can also help with the corresponding
processing for such data formats.
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators
Do I need to achieve the desired source file a
This CMake wiki page (
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library) claims one can
create a library from subdirectories containing libraries, which is exactly
what I want to do. However, it doesn't seem to work. Here's my SSCCE (
http://sscce.org) "toy" example file structure:
.
|--
10 matches
Mail list logo
