.cmake file by
install(FILES foo.txt DESTINATION . CONFIGURATIONS Debug )
Do I figured it was the best way to do it
Scott
-Original Message-
From: Scott Aron Bloom
Sent: Saturday, May 14, 2016 10:41 AM
To: 'J Decker'; Roman Wüger
Cc: cmake@cmake.org
Subject: RE: [CMake] Debug vs Release
I was able to use the ${BUILD_TYPE} and the ${CMAKE_INSTALL_CONFIG_NAME} using
a INSTALL( CODE
Call.
Thanks for all the help
Scott
-Original Message-
From: J Decker [mailto:d3c...@gmail.com]
Sent: Friday, May 13, 2016 6:52 PM
To: Roman Wüger
Cc: Scott Aron Bloom; cmake@cmake.org
Looking for some advice.
In order to make our Visual Studio debugging environment, as self-contained
(and easy to use for the developers) as possible, we use developers must run an
install. We also use the resulting release based Install for our packaging
into our installer.
We change the
When I am building DLLs I tend to use an "install step" as part of my cmake
process. Then I make sure the builds' install area is in the path of the
application.
The issue may be your EXE cant find the DLL in its path.
Scott
-Original Message-
From: CMake
I had asked a similar question 2 weeks or so ago. The conclusion, which DID
work well was the following.
Rather than having 1 “large” cmake project with sub libraries.
Use the “super-project” system, where you do an ExternalProject_Add for each of
the projects. Then for the projects that
urrent configuration isn’t
known as a CMAKE variable at the proper time
So I descided to just "hard code" it in, like you suggested.
Scott
-Original Message-
From: David Cole [mailto:dlrd...@aol.com]
Sent: Thursday, March 24, 2016 12:30 PM
To: Scott Aron Bloom
Cc: Hendrik
-Original Message-
From: Hendrik Sattler [mailto:p...@hendrik-sattler.de]
Sent: Thursday, March 24, 2016 3:54 AM
To: Alan W. Irwin; Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Two phase install?
Am 24. März 2016 10:14:40 MEZ, schrieb "Alan W. Irwin&
...@cmake.org] On Behalf Of Scott Aron Bloom
Sent: Wednesday, March 23, 2016 8:53 PM
To: Alan W. Irwin
Cc: cmake@cmake.org
Subject: Re: [CMake] Two phase install?
> Thanks I'm getting close now.
>
> However, for the two sub projects, there doesn’t seem to be a way to run the
> make stage with
> Thanks I'm getting close now.
>
> However, for the two sub projects, there doesn’t seem to be a way to run the
> make stage with -j 6 or any make options.
>
> Am I missing something? I see how to set CMAKE_ARGS but no MAKE_ARGS
Hi Scott:
Some of my further comments are somewhat off your
...@gmail.com]
Sent: Wednesday, March 23, 2016 6:14 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Two phase install?
Sure, here are a couple of my own projects:
https://github.com/LB--/events/blob/e3215d84644c67848b6d716d308e66c6f186b84e/CMakeLists.txt#L26-L29
https://github.com
Ok.. Do you have an example somewhere ?
-Original Message-
From: Nicholas Braden [mailto:nicholas11bra...@gmail.com]
Sent: Wednesday, March 23, 2016 6:11 PM
To: Scott Aron Bloom
Cc: Alan W. Irwin; cmake@cmake.org
Subject: Re: [CMake] Two phase install?
Both projects should be built via
[mailto:cmake-boun...@cmake.org] On Behalf Of Scott Aron Bloom
Sent: Wednesday, March 23, 2016 2:50 PM
To: Alan W. Irwin
Cc: cmake@cmake.org
Subject: Re: [CMake] Two phase install?
-Original Message-
From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
Sent: Wednesday, March 23, 2016 2:48
-Original Message-
From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
Sent: Wednesday, March 23, 2016 2:48 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Two phase install?
On 2016-03-23 20:25- Scott Aron Bloom wrote:
> Here is my problem.
>
> The
Here is my problem.
The project I have creates an application, that is needed to build the rest of
the project.
To imagine it, imagine the application is a custom yacc/lex based parser that
reads in a file and generates an output file.
In order for the application to run correctly, it needs
The number one thing I would love to see for CMake + Visual Studio is the
ability to create a Win64 and Win32 from the same project.
Scott
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Marian Luparu
Sent: Thursday, March 10, 2016 6:15 PM
To: cmake@cmake.org
Subject: [CMake] CMake
While a possibility, not necessarily..
I would white list your projects directory.
Scott
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of David Cole via CMake
Sent: Tuesday, December 29, 2015 5:52 AM
To: Mauro Ziliani
Cc: cmake@cmake.org
Subject: Re: [CMake]
I wound up doing exactly what you started….
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Dzenan Zukic
Sent: Thursday, November 26, 2015 8:48 AM
To: CMake users
Subject: [CMake] MSVC version string
Hi everybody,
is there a way to get MSVC's version string (for the current generator)
gymnastics with add_test WORKING_DIRECTORY, or setting a test's ENVIRONMENT
property.
On Fri, Nov 6, 2015 at 3:14 PM, Scott Aron Bloom <sc...@towel42.com> wrote:
> I have a unit test, that I have have avoided deploying, because its
> executable (gmock/gtest based) depend
I have a unit test, that I have have avoided deploying, because its executable
(gmock/gtest based) depends on a third party dll. Essentially it's a unit test
to test our interface to the thirdparty library. So for much of the application
unittesting, I have a mock to simulate the 3rd party
When I had tried it previously, It was too out of date, I will take a look.
Im still hoping CMake integrates it in.
Scott
-Original Message-
From: Greg Marr [mailto:greg.m...@autodesk.com]
Sent: Wednesday, August 5, 2015 11:42 AM
To: Raymond Wan; Scott Aron Bloom
Cc: cmake@cmake.org
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of David Cole via CMake
Sent: Tuesday, August 4, 2015 3:11 PM
To: Tamás Kenéz
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
There's nothing wrong with that
-Original Message-
From: Raymond Wan [mailto:rwan.w...@gmail.com]
Sent: Tuesday, August 4, 2015 5:14 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
On Wed, Aug 5, 2015 at 7:10 AM, Scott Aron Bloom sc...@towel42
-Original Message-
From: Raymond Wan [mailto:rwan.w...@gmail.com]
Sent: Tuesday, August 4, 2015 6:53 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
On Wed, Aug 5, 2015 at 8:23 AM, Scott Aron Bloom sc...@towel42
This is why I don’t use the CXX_STANDARD and instead use the CXX_FLAGS and add
the flag I need.
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of digitalriptide
Sent: Friday, July 3, 2015 1:56 PM
To: cmake@cmake.org
Subject: [CMake] Setting CXX_STANDARD 11 Enables GNU Extensions
If I
Is there any plan, on merging the Win32 and Win64 generators for the current
set of VS 20XX generators?
I know there are a couple of non-kitware attempts.. but nothing that I would
call ready for the commercial world.
Scott
--
Powered by www.kitware.com
Please keep messages on-topic and
What have you tried? And what is causing you problems?
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of salil vishnu Kapur
Sent: Saturday, June 20, 2015 5:48 AM
To: CMake@cmake.org
Subject: [CMake] Regarding CMake usage in creating User Defined Functions in
mysql on windows OS
Hello
Generator is the target build system. If you run cmake –help, it will give you
a list of available generators.
Scott
From: salil vishnu Kapur [mailto:salilvishnuka...@gmail.com]
Sent: Saturday, June 20, 2015 10:55 AM
To: Scott Aron Bloom
Subject: Re: [CMake] Regarding CMake usage in creating
Recently, during our install phase, we get the following error message
CMake Error at CoreApp/CLI/cmake_install.cmake:45 (file):
file RPATH_CHANGE could not write new RPATH:
$ORIGIN/lib
to the file:
/home/marc_local/views/.branch/bin/dbg/Install/./.BluePearlCLI
No valid ELF RPATH
Is it possible to have multiple install targets?
Essentially, our install system, installs a bunch of mostly static files,
that rarely change, but are needed for a complete installation.
However, running the install, takes time to verify each file hasn't changed.
What Im thinking, is creating
That makes sense.. Ill play with it and see.
It looks like a straight forward solution…
Scott
From: CHEVRIER, Marc [mailto:marc.chevr...@sap.com]
Sent: Wednesday, May 20, 2015 12:00 AM
To: Scott Aron Bloom; cmake@cmake.org
Subject: Re: [CMake] Setting install dir based on Debug or Release
We use the install system, and love it.
However, since our install include copies of 3rd party debug libraries that are
named the same as the release counterparts (not our call ;() I would like to
just have a the path be install.deb rather than install
We set the CMAKE_INSTLL_PREFIX variable,
What is your cmake generator being used?
For Visual Studio 2013, you will need to use
cmake –G “Visual Studio 12 2013 Win64”
Scott
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Xi Shen
Sent: Thursday, April 23, 2015 11:28 PM
To: cmake@cmake.org
Subject: [CMake] cmake 3.1.1 does not
When creating a project using cmake, and Visual Studio 2013, I get the
following warning:
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5):
warning MSB8029: The Intermediate directory or Output directory cannot reside
under the Temporary directory as it
...
But make install, should just build the things being installed and THEIR
dependencies, NOT the ALL dependency.
Scott
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Scott Aron Bloom
Sent: Saturday, March 21, 2015 7:07 AM
To: David Cole; Nils Gladitz
Cc: CMake ML
Subject: Re: [CMake] unit
I run make test separately .. I just don't want it to go through the
dependency check for thr 600 unit tests..
--Scott
Original message
From: David Cole dlrd...@aol.com
Date:03/21/2015 04:19 (GMT-08:00)
To: Nils Gladitz nilsglad...@gmail.com
Cc: Scott Aron Bloom sc
from all attribute, that is really
an exclude from install?
Scott
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Scott Aron Bloom
Sent: Friday, March 20, 2015 16:05 PM
To: CMake ML
Subject: [CMake] unit tests include in all but not install
In general, I want unit tests, are build when
In general, I want unit tests, are build when I do a make all, but I really
don't care if they are up to date for a install..
Is that a possibility?
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
Based on what was posted.. I was able to get this working without much
difficulty.
For all of my libraries, I use the technique borrowed from my qmake days, so
all headers (and source) are stored as a variable ${project_H} and if it's a qt
based header ${qtproject_H}
So I added to every
I have found I can disable it project by project, but I cant seem to disable
it, globally for every project
Is there a way (or point in the cmake flow) to disable it globally?
Scott
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
I have some functions, that when Im working on, I need to debug, but the other
developers don't need to see the debug messages.
I wind up commenting them out, but I would prefer to put them out as debug
level messages, ie when -debug-output is set.
Is this possible?
Scott
--
Powered by
, Mar 4, 2015, 11:03 AM Scott Aron Bloom
scott.bl...@onshorecs.commailto:scott.bl...@onshorecs.com wrote:
Another question on this..
It appears, that cmake creates the proper solution, for 64 bits even if the
shell is setup for 32 bits, and vice versa.
Is this correct? Meaning when its checking
Agreed on all points.. Unfortunately... ;)
I remember going through this with qmake, which initially could not create a
debug and release vc project file...
--Scott
Original message
From: David Cole dlrd...@aol.com
Date:03/08/2015 13:57 (GMT-08:00)
To: Scott Aron Bloom
the generator Visual
Studio...Win64 vs Visual Studio for bit width
If Im not using a command line based build, does it matter how my command line
is setup for running cmake?
Scott
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Scott Aron Bloom
Sent: Friday, February
That’s what I have been doing... :(
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, February 27, 2015 8:33 AM
To: Scott Aron Bloom; CMake ML
Subject: Re: [CMake] Multi-platform visual studio projects
I have been successful with
Src\build.32 and src
Thanks!
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, February 27, 2015 8:26 AM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Multi-platform visual studio projects
However, once the solution is created, does the path of the shell
Is it possible with cmake, to build a VS 2013, win32 and win64 vsproj solution
file set?
If not, I understand, then I have a follow on question..
Once the two solutions have been built, does it matter how you bring up VS
2013? Or does it only matter for the initial running of cmake ?
Scott
the solution is created, does the path of the shell matter at
all?
Scott
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, February 27, 2015 8:06 AM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Multi-platform visual studio projects
On Fri, Feb
I am attempting to use the JOM makefile generator, Im using the latest (1.0.14
of jom)
I get the following error:
-- The C compiler identification is MSVC 15.0.30729.1
-- The CXX compiler identification is MSVC 15.0.30729.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
We have been building for 32 bits on windows, and 64 bit on linux and OSX for a
while.
In order to enable this, we have a simple function that uses
CMAKE_SIZEOF_VOID_P to add a define via add_defintions
However, we are now going to build for windows 64, I calling vsvarsall.bat with
x64 as a
That was it! Is there any way to set that as the default? Ie, is there an
environmental variable that sets the default generator?
Scott
From: Nils Gladitz [mailto:nilsglad...@gmail.com]
Sent: Wednesday, February 04, 2015 11:34 AM
To: Scott Aron Bloom; cmake@cmake.org
Subject: Re: [CMake
Thanks. :(
From: Nils Gladitz [mailto:nilsglad...@gmail.com]
Sent: Wednesday, February 04, 2015 11:53 AM
To: Scott Aron Bloom; cmake@cmake.org
Subject: Re: [CMake] Building for 64 bit with Visual Studio 2013
On 04.02.2015 20:44, Scott Aron Bloom wrote:
That was it! Is there any way to set
Is there any builtin CMake support for compiler independent support for
pre-compiled headers?
I have found a couple of hacks out there for MSVC, and some for gcc.. but
nothing that is all inclusive, and frankly none that look up to the quality of
CMake :)
Scott
--
Powered by
:00)
To: Scott Aron Bloom scott.bl...@onshorecs.com
Cc: cmake@cmake.org
Subject: Re: [CMake] Bug in SLN generation
Hi Scott.
To file a bug, use the Mantis tracker at http://public.kitware.com/Bug/
As for running custom processing post-generation, there is no way hook this,
and a request
The other problem with the script technique, is most of my devs use cmake
inside visual Studio..
--Scott
Original message
From: David Cole dlrd...@aol.com
Date:01/06/2015 07:35 (GMT-08:00)
To: Petr Kmoch petr.km...@gmail.com
Cc: Scott Aron Bloom scott.bl...@onshorecs.com
I have found a bug in SLN generation when the property USE_FOLDERS is set to
on.
The order of the folders, and vcprojects added to the folders is not sorted.
It is sorted correctly if USE_FOLDERS is not set.
I have two questions, first, what is the appropriate mechanism for filing a
bug? I
...@gmail.com]
Sent: Thursday, January 01, 2015 20:45 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Rename target RUN_TESTS
On Thu, Jan 1, 2015 at 11:27 PM, Scott Aron Bloom scott.bl...@onshorecs.com
wrote:
For windows Visual Studio using CMake with google test, one
That doesn't work :(
Unfortunately it could be that I have put the custom target command in the
wrong location, however, I put it as the last line in my top level
CMakeLists.txt
ADD_CUSTOM_TARGET( ALL_RUN_TEST DEPENDS RUN_TESTS )
But it doesn't right mouse clicking - build doesn't give the
For windows Visual Studio using CMake with google test, one of the complaints
my team has, is the project name RUN_TESTS gets lost in the numerous projects.
Is there a CMake command to rename a target?
We would like to name it ALL_RUN_TEST
Scott
--
Powered by www.kitware.com
Please keep
Im in the process of converting a CMake 2.X project to 3.X.
I cant for the life of me, find a deterministic way to properly SET the policy
so I don't get the
Policy CMP0043 is not set: Ignore COMPILE_DEFINITIONS_Config properties.
Run cmake --help-policy CMP0043 for policy details. Use the
that they set the
policy the way you want it).
The documentation of cmake_policy() has details about this, including how the
policy stack works. You should be able to find more info there.
Petr
On Thu, Dec 11, 2014 at 10:13 AM, Scott Aron Bloom
scott.bl...@onshorecs.commailto:scott.bl
I am setting and using CMAKE_AUTOMOC to on, however, for Qt4+Cmake 2.8 builds,
I would put the moc files into a separate folder (Visual Studio) using
source_group(Generated Files FILES ${qtproject_MOC_SRCS})
Where qtproject_MOC_SRCS was defined via
QT4_WRAP_CPP(qtproject_MOC_SRCS ${mocheaders})
The warning message for CMP0020 seems to be completely random as to where you
actually have to set the policy.
Im not getting the warning on my main executables, but cant seem to get rid of
it on any of my Qt based unittests (using gmock/gtest )
I have the following line, in various places in
So I may be taking on too much.. but I am migrating to Qt5 and Cmake 3.0 on my
project (from Qt4.8 and CMake 2.8)
I have minimized the project to a simple testcase that will represent the
problem, and it still exists.
My project, has multiple executables and multiple libraries for each exec.
Im using a package installation, and its working fine.. Except 1 minor issue.
When the user installs an updated version, it doesn't uninstall the previous
version. Im not an OSX expert by any means, is it possible to have in
uninstall the previous version?
Scott
--
Powered by
I have a couple of similar files to this.
Some are XML based source files, others are “SVN” sourced file. Others are
.y/.l based files.
Some are checked in, some are not. The reason, not every developer has or
needs the “full” development environment. Ie, not every developer has
flex/bison
At some point in the 2.8 lifecycle, the choice was made to no longer copy the
.pdb files on windows builds with the .lib that is generated.
I found a note somewhere, that there was good reasoning for it.. And in
general, I agree, for many applications you don't need the pdb files for static
Im not sure if that is available on the version of MSVC I am using.. But Ill
take a look.. Thanks
-Original Message-
From: David Cole [mailto:dlrd...@aol.com]
Sent: Wednesday, May 21, 2014 9:45 AM
To: Scott Aron Bloom; cmake@cmake.org
Subject: Re: [CMake] PDB generation
However
Somehow I have corrupted the Visual studio macro, and its no longer effective
when cmake is run.
I have tried uninstalling and re-installing cmake, and it doesn't resetup the
macro. Is there a registry setting somewhere? Or a addin I need to manually
uninstall?
VS 2008 btw..
Scott
--
Somehow, I corrupted the visual studio CMake macro.. I have no idea how...
However, I cant figure out how to completely remove it, and then have cmake
re-install it
I have been googling on and off for 2-3 weeks with no success
Thanks in advance,
Scott
--
Powered by www.kitware.com
Please
69 matches
Mail list logo
