On 10/06/2015 09:42 AM, Robert Maynard wrote:
I am proud to announce the first CMake 3.4 release candidate.
This appears to have broken plplot's ada build on Fedora. Previous good
(cmake 3.3.2):
[ 22%] Building Ada object examples/ada/CMakeFiles/x00a.dir/x00a.o
cd /builddir/build/BUILD/plplo
So if this is the case, how does one "write correctly" the find/config
module so that both debug and release libraries are found? I've got a
library I depend on whose maintainer may not have built the best Find
module in the world. I've looked at
https://cmake.org/Wiki/CMake/Tutorials/How_to
CMake supports multi-config generators such as Visual Studio and Xcode for
a long time.
There are two flavors of config-modules (and find-modules), the legacy one
which creates variables like MY_PACKAGE_LIBRARIES and the install-export
kind which creates IMPORTED targets.
Both kinds of modules sup
I am looking for a way to tell my project to link against external debug
libraries with a debug build and external release libraries with a
release build with Visual Studio.
I sort of want to be able to say something like
if (BuildingReleaseConfig)
find_package(OtherPackage REQUIRED COMPONENTS
Hello.
I am using cmake 3.3.2.
The following script sets the CUDA_USE_STATIC_CUDA_RUNTIME option, then
finds the CUDA package.
cmake_minimum_required(VERSION 3.3)
option(CUDA_USE_STATIC_CUDA_RUNTIME OFF)
set(CUDA_TOOLKIT_ROOT_DIR "d:/work/CUDAToolkit")
message(STATUS CUDA_USE_STATIC_CUDA_RUNTIM
I have libpng16.dll, libpng16.lib, and png.h
Where should I put these files to cmake:FindPNG foud them?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community.
I am proud to announce the first CMake 3.4 release candidate.
Sources and binaries are available at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.4
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.4/release/3
hello list,
I am running Xcode (5 & 6) and using CMake to generate the Xcode project
files. We have a lot of targets for our project and we were looking into ways
of refactoring the Cmake codes in order to reduce the number of targets. For
example we have a lot of plugins that we compile and
Hi Roman,
I'm not necessarily only talking about CMAKE_CXX_FLAGS here. I define compile
flags for my targets in a number of different ways. Like:
find_package( ROOT COMPONENTS ${ROOT_LINK_COMPONENTS} REQUIRED )
include( ${ROOT_USE_FILE} )
...
add_definitions( ${ATLAS_DEFINITIONS} )
...
Hi,
What is the best way to check if a test is already defined using function
add_test?
My initial though was that if() can be used for that purpose but,
unfortunately, if (TEST ) is not supported for now.
Thanks.
Marc
--
Powered by www.kitware.com
Please keep messages on-topic and check
CMake performs deduplication of per-target flags for sure.
However I'm not sure if CMAKE_CXX_FLAGS is deduplicated. But I consider this
variable as global flags for the whole project which is defined at topmost
CMakeLists.txt. If you need to specify some flags specifically for a target use
t
11 matches
Mail list logo