Re: [CMake] Building out of source

On Fri, Dec 5, 2008 at 2:37 PM, David Cole <[EMAIL PROTECTED]> wrote: > What is the output? That should definitely work. I do it all the time with > Visual Studio... > Is this Vista? (I use XP and Vista, Vista has more seemingly random "file > can't be created/deleted" problems) > Are you running

Re: [CMake] cmake 2.6.3 RC 5

2.6.3R5 behaving a little strangely on one of my test projects. I have a program that generates cpp files from some input file. My program also outputs a dependency file which I parse into a CMake readable format. The basic setup creates a cmake script using configure_file with all the commands t

Re: [CMake] Output directory

On Fri, Dec 05, 2008 at 03:53:11PM -0500, [EMAIL PROTECTED] wrote: > So, for example, you can get some of the intermediate files to be > written to component1/build/obj/Release, but you can't get them written > directly to component1/build/obj. Unless you are willing to download > > I complained

Re: [CMake] 'unset' not in --help-commands-list (also, attn: neundorf)

Philip Lowman wrote: On Thu, Dec 4, 2008 at 5:36 PM, Matthew Woehlke wrote: What version of cmake are you looking at? Maybe I am wrong what version introduces 'unset'? As far as I know the unset command hasn't been backported to the CMake 2.6.x branch. If you want to use it in your scripts yo

Re: [CMake] Output directory

Ioan Calin Borcoman wrote: > I dump all my apps in the CMAKE_BUILD_DIR with: > > set(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}) This is a useful thing to do if you're using CMake to generate a Visual Studio 6.0 workspace. But as far as I can tell, if you generate a "solution" for any later ver

Re: [CMake] Forcing CMake to place targets in directories?

On Dec 5, 2008, at 12:52 PM, Robert Dailey wrote: On Fri, Dec 5, 2008 at 10:48 AM, David Cole <[EMAIL PROTECTED]> wrote: The target name is the name given as the first argument to ADD_LIBRARY, ADD_EXECUTABLE or ADD_CUSTOM_TARGET. CMake uses the target name to create the name of the vcproj

Re: [CMake] Building out of source

What is the output? That should definitely work. I do it all the time with Visual Studio... Is this Vista? (I use XP and Vista, Vista has more seemingly random "file can't be created/deleted" problems) Are you running as admin or non-admin? (I always run as non-admin) Which version of cmake are yo

Re: [CMake] Output directory

On Dec 5, 2008, at 11:54 AM, Robert Dailey wrote: On Mon, Nov 24, 2008 at 10:34 AM, Ioan Calin Borcoman <[EMAIL PROTECTED] > wrote: I dump all my apps in the CMAKE_BUILD_DIR with: set(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}) Thanks for your response. I'm having a hard time understandin

Re: [CMake] Building out of source

On Fri, Dec 5, 2008 at 12:44 PM, David Cole <[EMAIL PROTECTED]> wrote: > They are placed in the current directory. Run it from another directory and > then give the path to the source tree, as in: > checkout source tree to "source" directory > mkdir build > cd build > cmake -G "Unix Makefiles" ../

Re: [CMake] How do you determine what compiler is being used?

Bill, Is there not always the option to just set this manually in the input cache if you need to? Otherwise, the default value could be something like "UNKNOWN" and then people could check for known systems to make special tweaks. - Ross > -Original Message- > From: Bill Hoffman [m

Re: [CMake] [Fwd: Re: Why does dependency scanning in version 2.6 seem so slow?]

Jose Luis Blanco wrote: These are my results: All the details go below, but in two computers, both with cmake 2.6.0 (from the Ubuntu repositories), it takes ~ 50sec vs. 19sec to recompile when only one file changes... and the longest delay happens in the better PC, though the CPU's are very sim

Re: [CMake] How do you determine what compiler is being used?

Philip Lowman wrote: CMAKE_C_COMPILER_ID CMAKE_CXX_COMPILER_ID CMAKE_Fortran_COMPILER_ID Thanks for adding this Bill. With the exception of dealing with MinGW or differing versions of MSVC this would seem to be a very good replacement for conditionals like: IF(CMAKE_COMPILER_I

Re: [CMake] Building out of source

They are placed in the current directory. Run it from another directory and then give the path to the source tree, as in: checkout source tree to "source" directory mkdir build cd build cmake -G "Unix Makefiles" ../source In this example, source and build are siblings... HTH, David On Fri, Dec

Re: [CMake] Building out of source

I have a folder for project files only (everything that CMake creates). To build to that folder I just run cmake from that folder. I have: cpp/project_files/tools cpp/project_builds/tools cpp/source/tools The CMakeLists.txt is in cpp/source/tools. I run CMake from cpp/project_file

[CMake] Building out of source

Hi, Instead of using the GUI frontend for CMake on windows, I'm choosing to use the command line directly (Don't ask why). How can I specify the directory for which the target files are placed when I run "cmake -G"? Right now all of the vcproj files and cache are being placed in the same directori

Re: [CMake] Forcing CMake to place targets in directories?

On Fri, Dec 5, 2008 at 10:48 AM, David Cole <[EMAIL PROTECTED]> wrote: > The target name is the name given as the first argument to ADD_LIBRARY, > ADD_EXECUTABLE or ADD_CUSTOM_TARGET. > CMake uses the target name to create the name of the vcproj files. > > By default, the name of the library or ex

Re: [CMake] How to make ctest not buffer its output?

2008/12/5 Hugo Heden <[EMAIL PROTECTED]>: > 2008/12/5 Daniel Nelson <[EMAIL PROTECTED]>: >> Alexander Neundorf wrote: >>> >>> On Thursday 04 December 2008, Hugo Heden wrote: Good day all, I use ctest --build-and-test to do some stuff that takes a long time. It seems that ct

Re: [CMake] Output directory

On Mon, Nov 24, 2008 at 10:34 AM, Ioan Calin Borcoman <[EMAIL PROTECTED]>wrote: > I dump all my apps in the CMAKE_BUILD_DIR with: > > set(EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}) Thanks for your response. I'm having a hard time understanding how this works. My project structure looks like

Re: [CMake] Forcing CMake to place targets in directories?

The target name is the name given as the first argument to ADD_LIBRARY, ADD_EXECUTABLE or ADD_CUSTOM_TARGET. CMake uses the target name to create the name of the vcproj files. By default, the name of the library or executable created is based on the target name and any appropriate prefixes or suff

Re: [CMake] cmake -E chdir on vista and xp

Might it be a directory permissions issue? "The system cannot find the file specified" might be telling you that untar cannot create the top level directory found in the tar file... Was the directory created by an admin, but you're running as a non-admin...? On Fri, Dec 5, 2008 at 5:55 AM, Boudew

Re: [CMake] Forcing CMake to place targets in directories?

The documentation says: OUTPUT_NAME sets the real name of a target when it is built and can be used to help create two targets of the same name even though CMake requires unique logical target names. The target being built here seems to be the VCPROJ when using "cmake -G" for visual studio 2008.

[CMake] CMakeEd Eclipse Plugin 1.1.0 RC4 is now available.

On Behalf of BlueQuartz Software and CThing Software I would like to announce another Release Candidate of the CMakeEd Eclipse Plugin. It can be downloaded from . This release contains more fixes for opening files not reco

Re: [CMake] CHECK_FUNCTION_EXISTS and -Werror

On Fri, Dec 5, 2008 at 12:12 PM, Eric Noulard <[EMAIL PROTECTED]> wrote: > 2008/12/5 Mathieu Malaterre <[EMAIL PROTECTED]>: >> 'lo there, >> >> I had my CFLAGS set to -Werror, and because of that a try compile failed >> with: >> > [...] >> /usr/share/cmake-2.6/Modules/CheckFunctionExists.c:3: war

Re: [CMake] CHECK_FUNCTION_EXISTS and -Werror

2008/12/5 Mathieu Malaterre <[EMAIL PROTECTED]>: > 'lo there, > > I had my CFLAGS set to -Werror, and because of that a try compile failed > with: > [...] > /usr/share/cmake-2.6/Modules/CheckFunctionExists.c:3: warning: > conflicting types for built-in function 'strncasecmp' > > > Does this mean

[CMake] cmake -E chdir on vista and xp

Hi, I'm wondering whether I've found a bug... If I execute the command cmake -E chdir data tar xvf ../../bla.tgz on XP, it works, but on Vista I get c:\WORK\HyvesDesktop\trunk\build>cmake -E chdir data tar xfz ../../data/static_bundle.tgz The system cannot find the file specified Even though

[CMake] CHECK_FUNCTION_EXISTS and -Werror

'lo there, I had my CFLAGS set to -Werror, and because of that a try compile failed with: Run Build Command:/usr/bin/make "cmTryCompileExec/fast" /usr/bin/make -f CMakeFiles/cmTryCompileExec.dir/build.make CMakeFiles/cmTryCompileExec.dir/build make[1]: Entering directory `/home/mmalaterre/Proje

Re: [CMake] How to make ctest not buffer its output?

2008/12/5 Daniel Nelson <[EMAIL PROTECTED]>: > Alexander Neundorf wrote: >> >> On Thursday 04 December 2008, Hugo Heden wrote: >>> >>> Good day all, >>> >>> I use ctest --build-and-test to do some stuff that takes a long time. >>> It seems that ctest buffers the output of its subcommands so that >>