You may want to move this to https://discourse.cmake.org/, as this mailing list
is going away (note, Im not with the cmake org at all.. just a user..)
That said,typically, when a CMake based library is included into a larger cmake
project, it will set some variables. SUBLIB_DIR for instance..
I'm looking for an equivalent to CMAKE_SKIP_INSTALL_ALL_DEPENDENCY for
packages, so when I do a make package, it doesn't build all first.
Does one exist?
Scott
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
We have a similar issue at my company, so the call to
/opt/rh/devtoolset-X/enable is done in our bashrc files
Then we use CMAKE__COMPILER_VERSION in our cmake file to make sure its
set correctly.
Scott
From: CMake On Behalf Of David Aldrich
Sent: Thursday, June 20, 2019 8:40 AM
To: CMake Mail
> Note, Im running from inside visual studio... I do realize for a
> makefile based system, I can run make install from inside the
> executable's build directory
>
> From: CMake On Behalf Of Scott Bloom
> Sent: Wednesday, March 27, 2019 7:23 PM
> To: cmake@c
( CMAKE_SKIP_INSTALL_ALL_DEPENDENCY TRUE )
Thanks again!
Scott
From: Scott Bloom
Sent: Thursday, March 28, 2019 10:20 AM
To: Scott Bloom ; frodak17
Cc: cmake@cmake.org
Subject: RE: [CMake] Install without building unittests
THANKS That was the exact variable I was looking for.
Scott
From: CMake
THANKS That was the exact variable I was looking for.
Scott
From: CMake On Behalf Of Scott Bloom
Sent: Thursday, March 28, 2019 10:05 AM
To: frodak17
Cc: cmake@cmake.org
Subject: Re: [CMake] Install without building unittests
This variable looks very interesting.. Ill play with it and see
This variable looks very interesting.. Ill play with it and see if it solves my
problems 😉
THANKS!!
Scott
From: frodak17
Sent: Thursday, March 28, 2019 10:03 AM
To: Scott Bloom
Cc: Kyle Edwards ; cmake@cmake.org
Subject: Re: [CMake] Install without building unittests
On Thu, Mar 28, 2019
out of date (or non-existant)
Scott
From: Kyle Edwards
Sent: Thursday, March 28, 2019 7:48 AM
To: Scott Bloom ; cmake@cmake.org
Subject: Re: [CMake] Install without building unittests
You could build CMake with -DBUILD_TESTING=OFF. This will skip the unit tests
altogether.
Kyle
On Thu, 2019
Note, Im running from inside visual studio... I do realize for a makefile
based system, I can run make install from inside the executable's build
directory
From: CMake On Behalf Of Scott Bloom
Sent: Wednesday, March 27, 2019 7:23 PM
To: cmake@cmake.org
Subject: [CMake] Install wi
I asked this a couple of years ago, and the answer was "no"...
If you run tests, it doesn't automatically build tests... So why does an
install?
I would never release something into the wild with out running the tests...
But, for developer builds, were we need to install all the packages in or
Strange...
When I had a similar problem, the command line for msbuild required the same
level of detail.
What about running it from visual studio on the command line?
Scott
-Original Message-
From: n...@appletonaudio.com
Sent: Monday, January 21, 2019 14:33
To: Scott Bloom
Cc
Can you make it work by running msbuild directly?
What about building using visual studio from the command line?
Scott
-Original Message-
From: CMake On Behalf Of n...@appletonaudio.com
Sent: Sunday, January 20, 2019 21:02
To: cmake@cmake.org
Subject: [CMake] Different behavior between
e two projects, that depens on the output of a single input
But this works
~~Scott
Original message
From: "Alan W. Irwin"
Date: 1/18/19 19:11 (GMT-08:00)
To: Scott Bloom
Cc: cmake Mailing List
Subject: Re: [CMake] Issue with qt5_add_resources with unit tests
O
I use qt + google test to run tests in my build environment.
The problem I have, is in some (most) of my unit test directories, there will
be multiple test executables created, all dependent on the same output file
from the add_resources step.
Typically its something like
qt_add_resource( reso
I have an older 3rd party (that is no longer supported) cmake file, that relies
on the CMP0053 OLD setting
Since I have moved to 3.12, Im getting the warning that its deprecated etc...
SC_CHECK_BROKEN_FUNC(
strstr "
extern int strstr();
exit(strstr(\"\\\0test\",
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
installi
Thanks I'll look into it.
~~Scott
Original message
From: "Alan W. Irwin"
Date: 4/28/18 01:07 (GMT-08:00)
To: Scott Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Multiple "projects" one directory
On 2018-04-27 22:06- Scott Bloom wrote:
>
I have a rather complicated Qt based project.
We are looking at rolling out a subset tool, and it will be significantly
smaller in functionality.
For that mode, I would like to set a CMake variable LITEVERSION that builds the
tool with -DLITEVERSION defined.
however, one (or two) folders, the
I know from the command line on a make based system, I can simply make install
on an individual project, and it will only install that executable.
Is there any way to do the same from visual studio?
Scott
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Does anyone have an example of COMPILE_PDB_NAME and how to set it?
Scott
--
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. For more
information on each of
20 matches
Mail list logo
