Sorry, the .sln is what I meant by "the solution file generated by
CMake". Thanks for catching that, it wasn't clear the way I wrote it.
=D English fail!
When I was smashing around in the solution file to try and get ALL_BUILD
to be the default project but also have it stored in the
PREDEFINED
You can't.
The default target is stored in the .suo file. That file is generated
by visual studio when it loads the solution file. The rules that Visual
studio uses for chosing the default target are not published and don't
seem to make a lot of sense. The reason that ALL_BUILD is marked as the
I looked at the code and the possibility of introducing a policy to
allow the alternate behavior. Looks quite straight forward, so I ask:
What is the policy on adding policies?
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
> > Is there some reason that couldn't be a property as well? Or
possibly a
> > Policy?
>
> 2) why does ALL_BUILD need to be the default project
>
> - This one I can't answer. I don't understand why it even is the
default
> startup project anyhow. As such, it's useless. It seems to me
> It is (forced by backwards compatibility requirements) by design.
>
> Here is the source code where I wanted to assign it to the
CMakePredefinedTargetsFolder:
>
> #if 0
> // Can't activate this code because we want ALL_BUILD
> // selected as the default "startup project" when
Hi All,
I was just trying out the Target folders stuff in 2.8.4. The ALL_BUILD
target doesn't seem to be affected by the PREDEFINED_TARGETS_FOLDER
property.
Is that by design or an oversight?
Aaron Meadows
Software Engineer
Thomson Reuters
Phone: 314.468.3530
Mobile: 636.541.6139
aar
Here's what I ended up with:
function(AssureOutOfSourceBuilds)
# make sure the user doesn't play dirty with symlinks
get_filename_component(srcdir "${CMAKE_SOURCE_DIR}" REALPATH)
get_filename_component(bindir "${CMAKE_BINARY_DIR}" REALPATH)
# disallow in-source builds
if(${src
Thanks for pointing that out.. not that it effects the example in the
slightest... they could have been "Bozo" and "Crusty" and still prove it
works. =D
Aaron C. Meadows
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, October 08, 2010 11:52 AM
To: Mea
Seems to work correctly from my tests:
CMakeLists.txt:
cmake_minimum_required (VERSION 2.8)
project(test CXX)
message( STATUS "CMAKE_GENERATOR: ${CMAKE_GENERATOR}")
message( STATUS "CMAKE_CL_64: ${CMAKE_CL_64}")
c:\dev2\Builds\test\x64>cmake -G "Visual Studio 8 2005" ../.
-- C
Is this not sufficient: (from "Variables That Describe the System")
CMAKE_CL_64: Using the 64 bit compiler from Microsoft
Set to true when using the 64 bit cl compiler from Microsoft.
This is what I'm intending on using, so if this won't work, I'll need to
know...
Aaron C. Meadows
I'd rather make it as hard as possible to form bad habits. It would also be
helpful to me. I've moved to the console and typed "cmake ." several times
thinking I was in the build directory, and then cussed quite a bit while
digging through removing cruft. (Points on Version Control taken, I'll
Yeah, I think I'll go with something like what you are saying. I wonder
if I can remove the CMakeFiles directory and the CMakeCache.txt file
from within the CMakeLists script...
Aaron C. Meadows
> Hi all.
>
>
>
> Is there a good way to disallow in-source builds? Ideally, I'd like
to
> prev
Hi all.
Is there a good way to disallow in-source builds? Ideally, I'd like to
prevent it before any cruft is written into the source tree. I
experimented with writing a function into my CMakelists file and calling
it. The function checked if CMAKE_BINARY_DIR was equal to
CMAKE_SOURCE_DIR an
Done: Issue 0011292
Cheers!
--aaron
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
Sent: Tuesday, October 05, 2010 9:24 AM
To: phi...@yhbt.com
Cc: cmake@cmake.org
Subject: Re: [CMake] CMa
I can try and take a look at it. I actually tried it in a hacky sort of
way and it worked great, but I wasn't using CMake's variable for the
compiler, etc... I used execute_process() and didn't have any issues
with 'cl /?' waiting on input. It shaved off several seconds with the
hacked-together
Done. Issue number 11279.
[http://public.kitware.com/Bug/view.php?id=11279]
I also noted that the script could be improved by calling the compiler
with the '/?' switch and parsing it's output instead of parsing the
output from try_compile'ing a simple c file it writes. That would make
it quit
Hi all. I noticed that CMakeDetermineVSServicePack.cmake only supports
vs2005, vs2005 sp1, vs2008, vs2008 sp1. I wanted to use it for vs2010.
I looked for a bug but the only one I found was the one that resulted in
the scripts creation: http://public.kitware.com/Bug/view.php?id=8803
I hav
Ok, I'll give that a shot. I wonder if I could iterate the list of targets and
make the target_link_libraries() calls on them in a loop.
Aaron C. Meadows
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Wednesday, August 25, 2010 9:59 AM
To: Meadows, Aaron C
Hi all.
I need to use different link paths for Debug and Release builds of my
software. I'm building with the Visual Studio Generator (2005, 2008,
etc). I had put this in my CMakeLists.txt, but as it turns out, this
doesn't do what I need (likely because of the single pass to generate
the pro
I don't believe this is possible. There was actually a discussion about
this, simultaneous to your question, regarding x86 and x64 builds in the
same solution files. The answer given was that it is not possible, and
it is better to have an x86 build tree and an x64 build tree. There was
a link g
>From the bug Description at
http://public.kitware.com/Bug/view.php?id=3796:
Visual Studio has "Solution Folders" for grouping Projects (i.e. build
targets). Large software projects would benefit from this feature. I
suppose the appropriate command would be PROJECT_GROUP, to parallel
SOURCE_GRO
In your Unification Script, you have the following:
# I found that SUBDIRS had a more desirable behavior for me as
to where
# binaries were created as opposed to ADD_SUBDIRECTORY.
SUBDIRS(lua luasocket luafilesystem luasql lualogging luadoc)
I was wondering if you could g
I don't know what options are compiled in for CMake, but it looks like
this is the libcurl option required to follow redirects:
CURLOPT_FOLLOWLOCATION
A parameter set to 1 tells the library to follow any Location: header
that the server sends as part of an HTTP header.
This means that
Speaking of GLOBbing, I have heard the same thing from the list. I read
the SO post you linked to, in particular, this seems to be the only
thing on the list which not GLOBbing gets you:
* CMake will track the dependencies of a new file on disk
correctly - if we use glob then files not glo
Ah.. think I've answered my own question. Looks like I need to use
TARGET_LINK_LIBRARIES() instead of ADD_DEPENDENCIES().
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
Sent: Wednesday, May 19,
Hi all. I hope this isn't a terribly obvious question that I just can't
find in the documentation..
If I have an executable 'A' that depends on a static library 'B', and
static library 'B' depends on static library 'C', can I capture this
dependency as part of the CMakeLists.txt for static lib
AWESOME! That's completely right!!! Thanks for the quick response,
this was really frustrating me!
So, file globs are evil? Not to get off subject, but care to expand on
that a bit?
Thanks for the help, I really appreciate it!!
Aaron C. Meadows
-Original Message-
From: Michael Wild
Incidentally, I have the same error on the LIBRARY_OUTPUT_PATH vs.
CMAKE_LIBRARY_OUTPUT_PATH, but they were being placed in the directory I
wanted. Is that a but or just a non-obvious feature?
Aaron C. Meadows
-Original Message-
From: Michael Wild [mailto:them...@gmail.com]
Sent: Monda
Hi All!
I'm trying to migrate an existing Visual Studio 8 2005 source tree to
CMake. The only problem I'm having right now is getting the build
artifacts to end up in the directories I want them in. I would like
everything to show up in the ${PROJECT_BINARY_DIR}/bin dir, but only
static libra
I had seen that option, which is for a specific library, I was hoping to just
be able to selectively set the library path for a particular configuration.
The current configuration relies heavily on #pragma
comment(lib,"libraryname.lib") to automatically build the library link list.
That's pro
Background:
* I am moving from Visual Studio 2008 projects to Cmake in
preparation
for porting our software to Linux.
* We have debug and release versions of 3rdparty libraries to
link
against in two separate paths but under the same name.
(debug
31 matches
Mail list logo
