Re: [CMake] FW: cmake newbie questions

Mike Jackson wrote: You are going to have to look through the CMake files and determine where the TEST_BIG_ENDIAN(variable) is located. Then you will need to put in some sort of conditional statement that says if you are compiling for z/OS then set variable to true. This really sounds like

Re: [CMake] FW: cmake newbie questions

Phil Smith wrote: OK, next issue. I'm following (or trying to) the cross-compiler page. Since the same source tree is to be used to generate Win32 and z/OS, I think I want to tell it This is a z/OS run using a flag. I thus created zcmake.bat: cmake -DCMAKE_TOOLCHAIN_FILE:string=zos.cmake

Re: [CMake] FW: cmake newbie questions

Phil Smith wrote: But then it complains that there's no CMakeLists.txt in the directory. Anyway, I wasn't clear: the same person isn't likely to be doing z/OS and Windows on the same machine. But since the same CMakeLists.txt is to be used, I didn't want to hard-code anything in there. I've

Re: [CMake] CMAKE/CTEST input test file

Edward Flanigan wrote: Using CTest, is there any way to specify what tests I want to run in a file? There is the option for -I where you have to specify the test number. I want to specify the test name (not the number): TestA TestB TestD use that file as an input to CTEST and run only the

Re: [CMake] CMAKE/CTEST input test file

. Right, ctest -RTest[A-D] The -R is a regular expression. Not quite what you want, but should do the job if you name your tests with some sort of convention. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371

Re: [CMake] CHECK_INCLUDE_FILES

) CMAKE_REQUIRED_INCLUDES = list of include directories -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http

Re: [CMake] CHECK_INCLUDE_FILES

HAVE_NETINET_TCP_H) -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] MS VS 2005 nmake problem

[EMAIL PROTECTED] wrote: Hi, I am running CMake 2.6 on an XP machine with MS Visual Studio 2005 and am trying to compile VTK cvs from the Visual Studio 2005 command prompt. I am getting the following errors reported by CMake: CMake Error at CMakeLists.txt:1005 (ADD_SUBDIRECTORY):

Re: [CMake] MS VS 2005 nmake problem

[EMAIL PROTECTED] wrote: Hi Bill, RC 15 for 2.6.1 and using C instead of c: cmake C:/C++/Source/VTK -GNMake Makefiles but now I have: Checking for ipv6 support. - no RegularExpression::compile(): Nested *?+. RegularExpression::compile(): Error in compile. CMake Error at

Re: [CMake] CPack Stripping Debug

Paul Hatfield wrote: When compiling a binary with CMAKE_BUILD_TYPE as RelWithDebInfo, I verify that the binary has debug symbols, but when I generate an rpm using Cpack the debug symbols are lost. What's causing this? rpm automatically runs strip on executables. It is not cmake doing this

Re: [CMake] CHECK_INCLUDE_FILES

/types.h;netinet/tcp.h HAVE_NETINET_TCP_H) -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman

[CMake] cmake 2.6.1 RC 16

I have a release candidate (RC 16) for 2.6.1 ready for CMake. If I do not get any complaints about this RC, it will become 2.6.1. Again, if there are no major issues, I am going to make this 2.6.1 official. Thanks. The files can be found here: http://www.cmake.org/files/v2.6/*RC-16* The

Re: [CMake] Error running link command: Argument list too long

Andrew Sayman wrote: The ChangeLogs that I can find for CMake 2.4.8 and 2.6.0 all seem to indicate that link lines being too long was fixed. Unfortunately, I'm still seeing link lines that are too long and immediately fail out because of it. Is there any place with more details on exactly *what*

[CMake] CMake 2.6.1 available for download

On behalf of myself, Ken, Brad, Dave, Alex and the rest of the CMake team, we are pleased to announce that CMake 2.6.1 is available for download at: http://www.cmake.org/HTML/Download.html If you have any problems or find any bugs, please report them at www.cmake.org/Bug. A list of changes for

Re: [CMake] CMake 2.6.1 available for download

Mathieu Malaterre wrote: Bill, I can reproduce my infinite dependencie problem. Every time I type 'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce the issue. How do I track this thing down ? Otherwise steps are simply: svn co

Re: [CMake] CMake 2.6.1 available for download

Mathieu Malaterre wrote: As a side note, linux user are second class citizen and AFAIK do not get automated RC build, right ? win user are simply a click away of trying RC. No, I do a full build for each RC, all platforms that are done for the release are done for the RC's. And AMD64 people

Re: [CMake] Symbian GCC/nmake build #3

. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake 2.6.1 available for download

Hendrik Sattler wrote: Am Montag, 4. August 2008 17:48:28 schrieb Mathieu Malaterre: That was not really my main concern anyway, instead I am more concerned with the patch done for debian people (admittedly I dont understand what they are trying to do):

Re: [CMake] CHECK_TYPE_SIZE works incorrectly with LDFLAGS=-Wl, --gc-sections

to reproduce this bug. Steps to reproduce: 1. Save the attachments to ${PROJECT_SOURCE_DIR} 2. Run: export LDFLAGS=-Wl,--gc-sections 3. Run: cmake ${PROJECT_SOURCE_DIR} 4. Read ${PROJECT_BINARY_DIR}/config.h I use CMake 2.6.0. What is in the CMakeError.log? Why is it failing? -Bill -- Bill Hoffman

Re: [CMake] CHECK_TYPE_SIZE works incorrectly with LDFLAGS=-Wl, --gc-sections

Arfrever Frehtes Taifersar Arahesis wrote: 2008-08-05 00:01:51 Bill Hoffman napisał(a): Arfrever Frehtes Taifersar Arahesis wrote: CHECK_TYPE_SIZE returns incorrect (empty) values of types sizes when the LDFLAGS variable contains -Wl,--gc-sections. This bug causes compilation failures

Re: [CMake] CHECK_TYPE_SIZE works incorrectly with LDFLAGS=-Wl, --gc-sections

Arfrever Frehtes Taifersar Arahesis wrote: Can you do a find in your build tree and find CMakeError.log? `find -name CMakeError.log` doesn't return anything. Can you do this: cmake --debug-trycompile Then tar up and zip the whole thing and email it to me off the list. Thanks. -- Bill

Re: [CMake] OS X Framework creation and DEBUG_POSTFIX

in framework creation.Eric? -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman

Re: [CMake] cmake 2.6-1 : no more GLEW support ?

Antoine PREVOT wrote: Hi, I am actually testing cmake 2.6-1, and I can't find FindGLEW.cmake anymore in the Modules folder of both darwin sources and binary archives (cmake-2.6.1.tar cmake-2.6.1-Darwin-universal.tar). Nothing about this in the ChangeLog. Bug or Feature ? :) That module

Re: [CMake] some basic questions

[EMAIL PROTECTED] wrote: Hi all, I have some probably easy to answer questions, nevertheless I found no answer on the web yet. And I dont want to start separate threads because I think there will be one word only answers :) * can CMake handle multiple make processes or any other strategy

Re: [CMake] Where does cmake look for include files?

Marianne B. Wiese wrote: Hello Just to let you know: It turns out that the way cmake looks for a file to include, is by TRY_CO)MPILE() a tiny c-file whith for example #include GL/glu.h. However, Visual C++ cannot compile with #include glu.h if windows.h is not included too. Therefore I

Re: [CMake] Invoking an script from the link command.

Óscar Fuentes wrote: Óscar Fuentes [EMAIL PROTECTED] writes: [snip] Solved: target_link_libraries(myexe `/path/to/script arg1 arg2`) This is in general a non-portable way to write cmake files, and is not guaranteed to work in any version of CMake. This is the same as a pkg-config script.

Re: [CMake] Invoking an script from the link command.

Óscar Fuentes wrote: Bill Hoffman [EMAIL PROTECTED] writes: Solved: target_link_libraries(myexe `/path/to/script arg1 arg2`) This is in general a non-portable way to write cmake files, and is not guaranteed to work in any version of CMake. This is the same as a pkg-config script. The way

Re: [CMake] ctest 'magic string' - failure

Matthew Woehlke wrote: Is there any way to arrange for running ctest to mark a test as failed if it outputs a particular string? I'm using ctest to write unit tests for a library that has some debugging facilities where if something goes wrong, it dumps an error message, but doesn't cause the

Re: [CMake] Invoking an script from the link command.

Óscar Fuentes wrote: Óscar Fuentes [EMAIL PROTECTED] writes: Bill Hoffman [EMAIL PROTECTED] writes: [about using shell backquotes embedded on link commands through `target_link_libraries'] I don't even think this will work with cmake 2.6.0, because we use link scripts. It is working

Re: [CMake] Re-executing CMake from the Makefile.

Óscar Fuentes wrote: Currently, when `make' is executed and a CMakeList.txt file is out of date, `cmake' is automatically invoked and then `make' continues. Is it possible to do this (on a reliable way) with an arbitrary file? I need to re-execute `cmake' whenever certain file changes. I wonder

Re: [CMake] Re-executing CMake from the Makefile.

Óscar Fuentes wrote: Bill Hoffman [EMAIL PROTECTED] writes: Óscar Fuentes wrote: Currently, when `make' is executed and a CMakeList.txt file is out of date, `cmake' is automatically invoked and then `make' continues. Is it possible to do this (on a reliable way) with an arbitrary file? I

Re: [CMake] Environment variable for a custom command

Gregory C. Sharp wrote: I found this little tidbit in the FAQ: [E]nvironment variables SET in the CMakeLists.txt only take effect for cmake itself, so you cannot use this method to set an environment variable that a custom command might need. I would like to augment the path during a

Re: [CMake] Environment variable for a custom command

Gregory C. Sharp wrote: Bill Hoffman wrote: Gregory C. Sharp wrote: I found this little tidbit in the FAQ: [E]nvironment variables SET in the CMakeLists.txt only take effect for cmake itself, so you cannot use this method to set an environment variable that a custom command might need

Re: [CMake] Customizing manifest

? Jan wrote: Hi, is there any way of customizing manifest in cmake (using MSVC 2008 and Vista)? Particularly, I need to modify requestedExecutionLevel. If there is not such possibility, are there any plans for next versions of cmake? You can do something like this:

Re: [CMake] Make program arguments

Moreland, Kenneth wrote: Is there a way to add arguments to the invocation of make? In particular, I want to add the -j flag to do parallel compiles. I tried setting the CMAKE_MAKE_PROGRAM variable to /usr/bin/make -j8, but I get the following error when I try to compile. CMake Error:

Re: [CMake] How to make cmake-2.6 tell why it fails

. Looking at the module: IF(QT_INCLUDE_DIR AND QT_QT_LIBRARY) SET( QT_FOUND YES ) ENDIF(QT_INCLUDE_DIR AND QT_QT_LIBRARY) So, what are the values of QT_INCLUDE_DIR AND QT_QT_LIBRARY in the users CMakeCache.txt file? One of those must not be found. -Bill -- Bill Hoffman Kitware, Inc. 28

Re: [CMake] How to make cmake-2.6 tell why it fails

Martin Costabel wrote: Bill Hoffman wrote: [] So, what are the values of QT_INCLUDE_DIR AND QT_QT_LIBRARY in the users CMakeCache.txt file? One of those must not be found. Indeed: QT_INCLUDE_DIR:PATH=QT_INCLUDE_DIR-NOTFOUND If I read the module correctly, cmake looks if the file $ENV

Re: [CMake] command line build and install on OSX

Darren Weber wrote: On Tue, Aug 19, 2008 at 2:15 PM, Bill Hoffman [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Darren Weber wrote: FYI, In case it makes any difference, I'm working on Mac OS X Leopard Server. Darwin elegans.buckcenter.org http

Re: [CMake] Can't compile a quite simple Fortran static library

Win32 -- 2Project not selected to build for this solution configuration == Build: 0 succeeded, 1 failed, 1 up-to-date, 1 skipped == Strange, looks like it is trying to create block3d.exe. Can you send me the generated project files? Thanks. -Bill -- Bill Hoffman

Re: [CMake] Can't compile a quite simple Fortran static library

Bill Hoffman wrote: CMake 2.6 successfully creates the Visual Studio project but, when I hit the build button, I get the following error message: 1-- Build started: Project: edgepack, Configuration: Debug Win32 -- 1Compiling with Intel Fortran 9.1 C:\Arquivos de programas\Intel

Re: [CMake] Can't compile a quite simple Fortran static library

Bill Hoffman wrote: Looking at the buildlog.html that you sent me, I see this: -- Build started: Project: edgepack, Configuration: Debug|Win32 -- Compiling with Intel Fortran 9.1 C:\Arquivos de programas\Intel\Compiler\Fortran\9.1\IA32\... ifort /nologo /Zi /fpp /define:ASLIB

Re: [CMake] Can't compile a quite simple Fortran static library

Renato N. Elias wrote: Hi Bill, I've followed your hint and tried to create a lib with 4 routines (https://mail.nacad.ufrj.br/~rnelias/transfer/cmake/SimpleLib.zip) and the problem persists. The VS project created by CMake doesn't work at all while my hand-made project works just fine. Is

Re: [CMake] Can't compile a quite simple Fortran static library

Bill Hoffman wrote: Renato N. Elias wrote: Hi Bill, I've followed your hint and tried to create a lib with 4 routines (https://mail.nacad.ufrj.br/~rnelias/transfer/cmake/SimpleLib.zip) and the problem persists. The VS project created by CMake doesn't work at all while my hand-made project

Re: [CMake] Can't compile a quite simple Fortran static library

Can you try this: In the .vfproj file that works it has this: VisualStudioProject ProjectType=typeStaticLibrary ProjectCreator=Intel Fortran Keyword=Static Library Version=9.10 ProjectIdGuid={3963F5B6-C0D8-4C36-8503-131A2F661664} In the one that does not work, it looks like this:

Re: [CMake] BUILD_DOCUMENTATION vs. BUILD_DOXYGEN

Darren Weber wrote: What's the difference between the CMake options: BUILD_DOCUMENTATION vs. BUILD_DOXYGEN The doxygen documents the C++ code in CMake. The documentation is the cmake --help stuff. -Bill ___ CMake mailing list CMake@cmake.org

Re: [CMake] re-config on make all

Vandenbroucke Sander wrote: Hi, Sometimes CMake re-configures my build tree when running make. Unfortunately CMake uses wrong options, I normally set those on the command line. This forces me to re-config rebuild my entire source tree. This is a bit annoying since, in most cases, this is not

Re: [CMake] MEMORYCHECK_COMMAND

Andy Lego wrote: Hi, Sounds like a nice rainy Sunday project. Unfortunately it does not rain in California that much, so it is going to take a while before I have a chance to look at it. Andy On Tue, Sep 2, 2008 at 11:07 AM, Sean McBride [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:

Re: [CMake] cmake 2.6 insists on using MSVC x64 even when in 32 bit shell

Anders Moe wrote: Thank for answering. I'm using the CmakeSetup.exe utility and interactively pick the Visual Studio 8 2005 compiler when it asks meI hope that answered the question ? The error dialog doesn't allow copy/paste, or I'd include more info. The information should be

Re: [CMake] cmake vista tutorial?

Craig Miller wrote: Thanks for the reply Alex. As a new user, I wasn't aware of the wiki and didn't think to look under the developer menu (thought it was for CMake devs, not devs using CMake). I was following the directions under http://www.cmake.org/HTML/Documentation.html. I'll take a

Re: [CMake] cmake vista tutorial?

Craig Miller wrote: Yeah, I made a few posts last week with the details of the specific problem I'm having. A couple of folks tried to help, but in the end they were stumped too. Here's an excerpt with the meat of the problem from one of those posts: On Aug 28, 2008, at 5:04 PM, Craig Miller

Re: [CMake] cmake vista tutorial?

Craig Miller wrote: I'm running Visual Studio 2005 w/ SP1. OK, so lets start from the beginning... Create a very simple project: ---CMakeLists.txt-- cmake_minimum_required (VERSION 2.6) project(bar) add_library(foo foo.c) - foo.c int foo() { return 1; } Put

Re: [CMake] cmake vista tutorial?

Craig Miller wrote: Yep, a Visual Studio 2005 target works. The output of rc /? is: c:\users\craig\nav\maps\basemaps\installrc /? Microsoft (R) Windows (R) Resource Compiler Version 5.2.3690.0 Copyright (C) Microsoft Corporation. All rights reserved.

Re: [CMake] Can't compile a quite simple Fortran static library

Renato N. Elias wrote: Bill Hoffman wrote: Renato N. Elias wrote: A managed to do something work (but not in the way that I'd like). In CMake, when configuring my project, if a check the Show Advanced Values and insert a /c in the CMAKE_Fortran_FLAGS the project works fine. Weird

Re: [CMake] cpack, nsis and visual studio 9

. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] cpack, nsis and visual studio 9

Boudewijn Rempt wrote: On Thu, 4 Sep 2008, Bill Hoffman wrote: Did you install service pack 1 for Visual studio 9? Yes -- it's Visual Studio Express 9.0.30729.1 SP We have been having some trouble with that. It seems that when you compile with VS 9 it puts one manifest in your .exe

Re: [CMake] cpack, nsis and visual studio 9

Boudewijn Rempt wrote: On Thu, 4 Sep 2008, Bill Hoffman wrote: It creates executables that embed the old version of the manifest, but ships with redist manifests that are the old (pre service pack) manifests. I wonder if you did a simple text edit on the redist manifests if it would work

Re: [CMake] Copying directories and build error

Bo Huang wrote: After running CMake to generate Visual Studio project files, I made a copy of C:\myProj to C:\myProjCopy In this copy, I change all references of “C:\myProj” to “C:\myProjCopy” in all .cmake, .txt, and other files. I build but get this: 1Checking Build

Re: [CMake] cmake 2.6.2 RC 3

Sean McBride wrote: On 9/5/08 9:02 AM, Bill Hoffman said: I have a release candidate (RC 3) for 2.6.2 ready for CMake. Thanks. The files can be found here: http://www.cmake.org/files/v2.6/*RC-3* The changes from 2.6.2 are as follows: From 2.6.1 I assume? Yes. - .m compiled with gcc

[CMake] [Fwd: [sldev] Meet the Experts: CMake]

FYI. -Bill ---BeginMessage--- And yet another event to announce -- Please join us for a meet the experts chat with Bill Hoffman of Kitware, creators of CMake http://www.cmake.org/HTML/index.html, and Bryan O'Sullivan (Sardonyx Linden), leader of the CMake build system implementation

Re: [CMake] ctest puts LD_LIBRARY_PATH into environment impacts sub-runs of cmake/ctest

(${CTEST_BINARY_DIRECTORY}) CTEST_BUILD (BUILD ${CTEST_BINARY_DIRECTORY}) SET(ENV{LD_LIBRARY_PATH} ...=) CTEST_TEST (BUILD ${CTEST_BINARY_DIRECTORY}) CTEST_SUBMIT () That will use the LD_LIBRARY_PATH for just the tests. You can keep it out of the configure step if you need to. -Bill -- Bill Hoffman Kitware, Inc

Re: [CMake] Compiler varience?

Preston A. Elder wrote: That does help a lot, but I think does not go quite far enough. As I said, there are other things that need to be done such as: - Adjusting warning levels (CMAKE_WARN_LEVEL=(None|Full|Standard) ) - Forcing a 32-bit or 64-bit compile - Allowing for platform-specific

Re: [CMake] ctest puts LD_LIBRARY_PATH into environment impacts sub-runs of cmake/ctest

Wheeler, Frederick W (GE, Research) wrote: Thanks for this helpful tip, which is panning out well, though I'm still testing/fixing a few things. I have a few follow-up questions, and I'm grateful for any advice on any of them from anybody. 1. What is the right way to add a notes file when

Re: [CMake] CVS write access for module maintainers

Matt Leotta wrote: Hi, I'm a new module maintainer and I've just join this list as well. I've filled out the web form to get a developer account, and Mantis now lists me as a developer. How do I check out the modules from CVS for read/write access? I haven't been able to fine the appropriate

Re: [CMake] How to add a test and compare its output to a reference file ?

Judicaël Bedouet wrote: Hi, I 'm converting a project to CMake. Tests in this project print messages to cout and these output traces are compared to reference files. If output and its reference are different, the corresponding test is considered as failed. I can't see how to make these tests

Re: [CMake] Small, realistic Cpack example

Boudewijn Rempt wrote: On Tue, 16 Sep 2008, Stephen Collyer wrote: Does anyone know of/have a realistic cpack example showing packaging of 3rd party libraries, as well as those built from the install target ? If the third party libraries happened to include Qt, that'd be just fine .. Ah...

Re: [CMake] make -j and cmake

Jim Chaney wrote: Although the version of make available on the cmake website seems to work OK from the command line, when I then run it under Incredibuild (to move from parallel to distributed builds) I get a crash inside make.exe. I have spoken to Xoreax (the makers of Incredibuild) and they

Re: [CMake] multi-line definitions

cyril_wobow wrote: Have you tried the following SET (CMAKE_C_FLAGS_RELEASE -mcpu=arm7tdmi -std=gnu99 -fgnu89-inline ... -DNDEBUG) Cyril That won't work. It will create a list of items and it needs to be a big string. The only way would be something like this: set(a -mcpu=arm7tdmi

Re: [CMake] multi-line definitions

Hendrik Sattler wrote: Am Thursday 18 September 2008 15:18:46 schrieb Bill Hoffman: cyril_wobow wrote: Have you tried the following SET (CMAKE_C_FLAGS_RELEASE -mcpu=arm7tdmi -std=gnu99 -fgnu89-inline ... -DNDEBUG) Cyril That won't work. It will create a list of items and it needs

Re: [CMake] Regenerating Visual Studio projects

Jesper Eskilson wrote: Hi all, When CMake (2.6) discovers that a CMakeLists.txt file has changed, and that one or more Visual Studio projects/solutions need to be reloaded, it attempts to interrupt the build, force Visual Studio to reload the projects, and then restart the build. This is

Re: [CMake] Customizing target locations with VS generator

Armin Berres wrote: On Wed, 17 Sep 08 12:28, cyril_wobow wrote: This is great but I would really love to find a way to remove that $(OutDir) from the way, so that all my targets are put into the same directory, not depending on the build config. There is no possible filename clash since

[CMake] cmake 2.6.2 RC 5

be different when analyzing gcov output. - Add warning level W0 to visual studio - Add support for OSX library version flags -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax

Re: [CMake] cmake 2.6.2 RC 5

Alan W. Irwin wrote: On 2008-09-22 13:56-0400 Bill Hoffman wrote: I have a release candidate (RC 5) for 2.6.2 ready for CMake. I think this one will be it for 2.6.2, so speak now or forever hold your peace... :) Could we have a fix for the enable_language bug #4772? I don't know the CMake

Re: [CMake] cmake 2.6.2 RC 5

Mike Jackson wrote: Any chance of getting Bug 6195 put into this release. This is an important bug/feature for OS X users. Sorry, that will have to wait until 2.6.3. Too much of a new feature. There are some issues with 2.6.1 that really need to be fixed so that some existing projects

Re: [CMake] find_library feature request

Christopher Harvey wrote: Hello list, I was wondering if a better way to handle failed find_library under windows would be to give the user a chance to manually find the package before giving an error. I know the user always has the chance to specify the path afterwards in the GUI, but I

Re: [CMake] cmake 2.6.2 RC 5

Alan W. Irwin wrote: Never mind since you indicated in your answer to Mike you were only interested in fixing newly introduced bugs for this release, and this CMake bug has been around a long time. On the other hand it is bad when a clear and obvious bug like this one persists for a long time

[CMake] Early Registration Ends Sept. 30th!

Kitware is pleased to announce the next Developer's Training Week for VTK, ITK, ParaView and CMake, which will be held November 3-6, 2008 in Clifton Park, NY. Course details are provided below and online at http://www.kitware.com/products/protraining.html. Early Registration ends September 30th.

Re: [CMake] cmake 2.6.2 RC 5

Alan W. Irwin wrote: On 2008-09-22 16:44-0400 Bill Hoffman wrote: [...]this bug is a bit of a corner case. Most projects just enable all the languages as the top of the project. In this case, no one could have a project that depends on this working because it never worked. However, I

Re: [CMake] cmake 2.6.2 RC 5

Alan W. Irwin wrote: enable_language(Fortran OPTIONAL) project(myproject C CXX) It would always test for fortran, and enable it if they have it. If they do not have it, then you can just turn off that binding. It won't be an error not to have it. If they do have it you can offer the

Re: [CMake] Additional testing of bug #4772

Alan W. Irwin wrote: i.e., the only pattern that gives the correct result is one that does not use ENABLE_LANGUAGE. I did all the above tests with 2.6.0, but previously I have shown the CVS version of CMake had similar problems. OK, thanks for trying it. I noticed that you only test with

Re: [CMake] Additional testing of bug #4772

Alan W. Irwin wrote: Bill, can you or someone else from Kitware take over now to finish this off? If you don't have immediate access to Linux, I am willing to do any experiments you suggest on that platform. Currently, I feel I am floundering around close to the solution of the problem on my

Re: [CMake] Compute Node Linux (CNL)

-- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Compute Node Linux (CNL)

John Biddiscombe wrote: Bill That is just a test. You might want to try make -k, most of cmake does not require shared stuff. However, I don't think we have an option to turn off all shared stuff yet. Good spot. OK. cmake has built itself now. I should have realized that the fail was

Re: [CMake] the switch to subversion?

Mike Arthur wrote: On Tuesday 23 September 2008 16:19:05 Michael Wild wrote: git rocks! ;-) I agree but not everyone is happy using the console for their VCS. You move to git and you alienate said people. Subversion, on the other hand, has a lots of GUI tools available for such folks. Lets

Re: [CMake] the switch to subversion?

Mathieu Malaterre wrote: svn 'external' links to repositories (not tested). Do not know what is the default behavior for branching... Yup, but there are issues with that. For one thing you can not do an atomic commit from the top of the tree and have it go into the sub project correctly.

[CMake] cmake 2.6.2 RC 6

I have a release candidate (RC 6) for 2.6.2 ready for CMake. There is one small fix over RC 5. I fixed cpack so it would run from a symlink, which fixes the command line install on Mac OSX when the application bundle is used. If there are no issues by the morning I will do a release

Re: [CMake] CMake Error: The source directory ./build/CMakeFiles/CMakeTmp does not exist.

Roger Martin wrote: Hi, I'm trying to build a build with cmake-2.6.1-win32-x86 CMakeSetup for Visual Studio 9 2008 Win64 as the build target. Keep getting a --- CMake Error: The source directory ./build/CMakeFiles/CMakeTmp does not exist. Specify --help for usage,

Re: [CMake] CMake Error: The source directory ./build/CMakeFiles/CMakeTmp does not exist.

Roger Martin wrote: Setting the full path fixes it. I'm wondering, on relative paths, if the cmake home/bin directory is the root. Yes, ./ is the current directory of the project from where I run a cmd script. With the paths fixed as you pointed out, I then get an error dialog

Re: [CMake] CMake Error: The source directory ./build/CMakeFiles/CMakeTmp does not exist.

Roger Martin wrote: The project consists entirely of configurations that require support for platforms which are not installed on this machine. The project cannot be loaded. The project consists entirely of configurations that require support for platforms which are not installed

Re: [CMake] Problems with cmake, visualstudio generator and add_library / target_link_libraries

Thomas Veith wrote: Hi *, when using a simple CMakeLists.txt like the following: cmake_minimum_required(VERSION 2.6) PROJECT(socket) add_definitions( -D_CRT_SECURE_NO_WARNINGS ) add_library(socket STATIC ../../src/base64.cpp ../../src/http.cpp ../../src/PoolThread.cpp

Re: [CMake] Problems with cmake, visualstudio generator and add_library / target_link_libraries

Thomas Veith wrote: Hi Bill, Thanks a lot! I did add_executable(foo foo.cpp) add_dependencies(foo socket) and wasnt aware that I also need target_link_libraries(foo socket) Now it works! Actually, you don't need that add_dependencies call either. That is only needed to force something

Re: [CMake] cmakesetup launch discrepancy

Aleksander Demko wrote: The commands: cmakesetup \src\mysource and cmakesetup c:\src\mysource seem to do different things under XP (Cmake 2.6.1). The first version loads the last source/build directories, while the second version does the right thing: loads mysource as the source and . as

[CMake] CMake 2.6.2 available for download

On behalf of myself, Ken, Brad, Dave, Alex and the rest of the CMake team, we are pleased to announce that CMake 2.6.2 is available for download at: http://www.cmake.org/cmake/resources/software.html If you have any problems or find any bugs, please report them at www.cmake.org/Bug. A list of

Re: [CMake] [New Module] Protocol buffers

Mike Arthur wrote: On Thursday 25 September 2008 17:36:52 Bill Hoffman wrote: Please see here: snip New modules added to the bug tracker are generally ignored. Patches for existing ones are assigned to the maintainer. It would be nice if you could send the above links and close the bug

Re: [CMake] Unix Makefiles can not find some project files

Mike Jackson wrote: I started down the path of using Unix Makefiles on Windows. Here is what I have done so far. I downloaded the GnuWin32 files to my PC. I edited the .bat file that launches GnuWin32 shell and added the Visual Studio 2008 vsvars.bat file. I open a new GnuWin32 shell and type

Re: [CMake] Dependent Libraries added automatically?

Mike Jackson wrote: I started noticing some warnings when I am linking my project executables that bascially says libraries are listed multiple times on the link line. Now this is just a warning so I _could_ ignore it but I am curios about how cmake is working at this point. Here is what I

Re: [CMake] Dependent Libraries added automatically?

Michael Jackson wrote: add_library(a ...) target_link_library(a b c) add_executable(foo ...) target_link_libraries(foo a) This will cause foo to link to a b c. With CMake 2.6.2 you can stop this from happening with a target property:

Re: [CMake] Fwd: Fwd: cmake link against Qt4's OpenGL

moc -help. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 [EMAIL PROTECTED] http://www.kitware.com 518-371-3971 (phone and fax) ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMAKE_CURRENT_SOURCE_DIR for modules

James Bigler wrote: Sure, but how can I do this from within FindMyPackage.cmake? Leave off the .cmake. include(extrastuff) should work if CMAKE_MODULE_PATH is set correctly. -Bill ___ CMake mailing list CMake@cmake.org

Re: [CMake] win32 wrongly set on linux when using subdirectories

Stephen Sinclair wrote: Hi, This is strange. I'm using CMake on Fedora Core 9. I have a few .c files that should only be included when my project is compiled on Windows, but for some reason it was including them on Linux. I paired this down to a minimal example that goes wrong. It seems that

Re: [CMake] Finding a library on Windows

Moritz Moeller wrote: FIND_LIBRARY(3DELIGHT_LIBRARY NAMES 3Delight PATH $ENV{DELIGHT}/lib) MESSAGE(STATUS ${3DELIGHT_LIBRARY}) It is PATHS not PATH. You told it to look for a library that might be named 3Delight, PATH or C:/Program Files/3Delight/lib. -Bill

<    1   2   3   4   5   6   7   8   9   10   >