t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 5993579..b7641ff 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 12)
-set(CMake_VERSION_PATCH 20180814)
+set(CMake_VER
>
> This seems like something that would be best-suited for a toolchain file
>
Is a toolchain file not equivalent to the corresponding list of '-D'
initializers? (aside from convenience)
On Tue, Aug 14, 2018 at 1:34 PM Michael Ellery wrote:
> This seems like something that would be best-suited
What about switching to Linux? It generally does what you tell it to do. :)
(Just wanted to release a bit the tension here… Dunno how effective it
is...)
_
-. .´ |
', ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
.' '. |
-' `’
https://rdb.is
On 15 agosto
It also cannot find CUDA likely as CUDA was not installed after 2017. I
would like it to load 2013 after being told to generate Visual Studio 2013
project files. Is this difficult to ask fo Kitware? I am sure there are
certainly some shenanigans like path or VS2017 hooking calls to 2013 tools
Visual studio 2017 is able to keep old project types and build them as
is... so it is using the 2013 tools even though loaded in the 2017 IDE.
I noticed this because the command line build tools are 2015, so if I
configure a project for node; it gets built as 2015, and the visual studio
project
Am 15. August 2018 00:20:37 MESZ schrieb Brian Davis :
>Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing
>2017... sigh.
>
>Without even regenerating or re configuring (even though that has no
>effect
>either) when "Open Project" is selected 2017 is opened and not 2013...
Am 14. August 2018 22:08:36 MESZ schrieb "Sebastián Mancilla"
:
>Normally, find modules call FIND_PACKAGE_HANDLE_STANDARD_ARGS, which in
>turn calls FIND_PACKAGE_MESSAGE, to print a nice message about the
>location
>and version of the dependency.
You can do that with
It doesn’t for me.. I would check your path… its probably just calling
devenv, and not an explicit path
Scott
From: CMake On Behalf Of Brian Davis
Sent: Tuesday, August 14, 2018 15:21
To: cmake Mailing List
Subject: [CMake] Why does CMake 3.9.0 open VS2017 when targeting 2013 after
Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing
2017... sigh.
Without even regenerating or re configuring (even though that has no effect
either) when "Open Project" is selected 2017 is opened and not 2013... errr
what am I targeting again? Happened after 2017 install. How
Normally, find modules call FIND_PACKAGE_HANDLE_STANDARD_ARGS, which in
turn calls FIND_PACKAGE_MESSAGE, to print a nice message about the location
and version of the dependency.
But I haven't found any way or example to do the same when using the CONFIG
mode of find_package. And I really want to
I wanted to try Conda for normal day-to-day C++ development, while having
all the dependencies isolated from other projects and the base system.
- Change the sources
- Build
- Run the tests
- Repeat
The most common workflow possible. I shouldn't go through conda-build for
that. There is nothing
Hi CMake people,
I am trying to configure CMake to retrieve boost, and then run boosts bcp tool
to extract a subset of boost (math/special_functions) that I need for my
project. I had it working before, but now I'm not sure what went wrong.
Right now when I build, CMake is able to retrieve the
This seems like something that would be best-suited for a toolchain file:
https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html
Have you given that a try? Also, I wonder if STATIC_LIBRARY_FLAGS is a custom
setting, because I don’t think that one is a standard cmake variable.
-Mike
Hi,
What is the correct way of setting archiver (and flags) and linker
(and flags) outside the CMakeLists.txt?
1) I am trying to use the following pattern:
cmake -DCMAKE_AR="" -DCMAKE_CXX_LINK_EXECUTABLE=" -o
" -DSTATIC_LIBRARY_FLAGS=""
-DCMAKE_SHARED_LINKER_FLAGS=""
Why are you not using conda-build here? Anaconda Distro and
conda-forge build countless CMake projects. It handles so much extra
stuff on top of building (DSO verification, rpath rewriting, more). If
your end goal is not conda packages then you can untar most sets of
conda-packages to make working
15 matches
Mail list logo
