#-- Set the Debug and Release names for the libraries
SET_TARGET_PROPERTIES( ${targetName}
PROPERTIES
DEBUG_POSTFIX ${DEBUG_EXTENSION} )
Mike Jackson
On Jul 11, 2014, at 12:20 PM, "Tessier, Philip A (TASC)"
wrote:
> All, greetings and thank you!
>
> I have a requirem
All, greetings and thank you!
I have a requirement to produce (on Windows, using Visual Studio) a "plugin"
(DLL) whose suffix varies by build. For example, foo.plugin (for Release) and
foo.pluginD (for Debug). I expect to use:
add_library(foo MODULE ${Sources})
and am hoping for a SUFFIX_DEBUG
On 7/11/2014 10:33 AM, Edward Diener wrote:
Shouldn't there be a way to change the current generator in the CMake
GUI ? It seems like I can only do this if I choose a new "Where to build
the binaries" path. But what if I just want to change the current
generator to something else using the curren
On Fri, Jul 11, 2014 at 10:33 AM, Edward Diener
wrote:
> Shouldn't there be a way to change the current generator in the CMake GUI ?
> It seems like I can only do this if I choose a new "Where to build the
> binaries" path. But what if I just want to change the current generator to
> something els
Shouldn't there be a way to change the current generator in the CMake
GUI ? It seems like I can only do this if I choose a new "Where to build
the binaries" path. But what if I just want to change the current
generator to something else using the current outpath path ?
--
Powered by www.kitwa
The latest edition of Mastering CMake is 6th edition (September 13,
2013), covering versions of CMake up to and including 2.8.12.
On Fri, Jul 11, 2014 at 8:34 AM, Petar Petrov wrote:
> Hello,
> just wondering how up to date is the "Mastering CMake"book. Does it
> cover all 3.0 changes ?
>
> Greet
On 07/11/2014 03:33 PM, pierre.anders...@se.atlascopco.com wrote:
Then it is odd that it does not work, the warning is given during
generation time and I have tested to print the status of the 0028 policy
at all points where the projects that get the warning has their
add_library/add_executable c
Then it is odd that it does not work, the warning is given during
generation time and I have tested to print the status of the 0028 policy at
all points where the projects that get the warning has their
add_library/add_executable command called, as well as at the end of their
respective CMakeLists
Hello,
just wondering how up to date is the "Mastering CMake"book. Does it
cover all 3.0 changes ?
Greetings,
Petar
--
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
On 07/11/2014 01:33 PM, pierre.anders...@se.atlascopco.com wrote:
Thanks for the response. None of those are called in the CMakeLists.txt
file that the warning is issued for, they are both called in a file
above that one in the build tree but said file also sets the CML0028
policy afterwards. Is
Thanks for the response. None of those are called in the CMakeLists.txt
file that the warning is issued for, they are both called in a file above
that one in the build tree but said file also sets the CML0028 policy
afterwards. Is it possible that a call to cmake_minimum_required resets the
polic
On 07/11/2014 11:00 AM, pierre.anders...@se.atlascopco.com wrote:
I have a very large project that is built with CMake, and I'm trying to
make it work a little nicer with CMake 3. Right now we, we see everal
warnigns that policy CMP0028 is not set.
Using
cmake_policy(SET CMP0028 OLD)
does not
I have a very large project that is built with CMake, and I'm trying to
make it work a little nicer with CMake 3. Right now we, we see everal
warnigns that policy CMP0028 is not set.
Using
cmake_policy(SET CMP0028 OLD)
does not seem to take effect. It's set at the same, top level, place where
13 matches
Mail list logo
