[CMake] Is it necessary to link a executable file?

Hi all, I have created executable file from C files. is it necessary to link them to some directories. if dont want to do so is ther any problem? Can i do that? Actually since iam not linking it with any library iam facing a problem. but if i create a library of those files or linking them to

Re: [CMake] Is it necessary to link a executable file?

2009/2/4 ankit jain ankitgu...@gmail.com Hi all, I have created executable file from C files. is it necessary to link them to some directories. if dont want to do so is ther any problem? Can i do that? Actually since iam not linking it with any library iam facing a problem. but if i

Re: [CMake] CMake Library Issues

Thanks for your help. It seems that the library cannot be compiled as static, when I tried it as dynamic it worked without a problem. I assume that this is due to the style includes as there wouldn't be a search path for a static library since it's part of the executable. Could anyone tell

Re: [CMake] Fwd: Is it necessary to link a executable file?

2009/2/4 ankit jain ankitgu...@gmail.com: 2009/2/4 ankit jain ankitgu...@gmail.com: Actually in this case i dont want to create libraries thats why iam wondering whether making only executable is permissble or not? If you use ADD_EXECUTABLE it should work just fine. -- Erk I am

[CMake] Fwd: Fwd: Is it necessary to link a executable file?

-- Forwarded message -- From: ankit jain ankitgu...@gmail.com Date: 2009/2/4 Subject: Re: [CMake] Fwd: Is it necessary to link a executable file? To: Eric Noulard eric.noul...@gmail.com 2009/2/4 Eric Noulard eric.noul...@gmail.com 2009/2/4 ankit jain ankitgu...@gmail.com:

Re: [CMake] Is it necessary to link a executable file?

2009/2/4 ankit jain ankitgu...@gmail.com: Actually in this case i dont want to create libraries thats why iam wondering whether making only executable is permissble or not? If you use ADD_EXECUTABLE it should work just fine. -- Erk ___ CMake

Re: [CMake] Fwd: Fwd: Is it necessary to link a executable file?

That's because a library doesn't need a main() function. It's just a set of functions that may be called by applications and is never executed by itself, however an executable needs a point of entry and therefore needs a main() function. On Wednesday 04 February 2009 10:51:31 ankit jain wrote:

[CMake] Problems globbing directory by FILE(GLOB_RECURSE)

Hi, I want to glob directories from a specified location, but unable to do so. My purpose is to run cmake and generate CTestTestfile.cmake in binary tree having multiple ADD_TEST commands. i.e. I want to extract directories ABC and DEF from an area listed below: /path/to/some/area/ABC

Re: [CMake] Problems globbing directory by FILE(GLOB_RECURSE)

Did you try: FILE (GLOB_RECURSE item /path/to/some/area/*) (Note the /* on the end of the globbing expression...) On Wed, Feb 4, 2009 at 6:28 AM, Ashutosh Juneja ashutosh.jun...@gmail.comwrote: Hi, I want to glob directories from a specified location, but unable to do so. My purpose is to

Re: [CMake] CMake Library Issues

I don't think the style of include paths has anything to do with whether or not the library will compile as a static or dynamic library. What is the output of: MESSAGE(SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}) Please post that to the list.

[CMake] Passing Macro Arguments to configure_file

Not sure what I am doing wrong but here is my problem. I have a macro that takes a few arguments. Within the macro I am calling configure_file and in the file that gets configured I am using the values of the arguments. Unfortunately after the file is configured during cmake time the

Re: [CMake] Passing Macro Arguments to configure_file

There is no variable named variable inside your macro. There is sort of like a pre-processor token that gets substituted in every place ${variable} is referenced as the macro is expanded for use. (Not exactly alike, but very similar to the C pre-processor macro concept... (#define)) If you want a

[CMake] Embedding Private Frameworks in Mac OSX Bundles

Hi there! I'm getting started with CMake and I'm using it to generate XCode files for the Mac. One thing I had trouble with is embedding private frameworks in the bundle such that it lives in the Contents/Frameworks subdirectory. I tried doing something like this: if (APPLE)

[CMake] FindQt4.cmake issues on OS X

Using CMake CVS on OS X with Qt 4.4.3 for my project. I was hacking some cmake code and decided to print out the ${QT_LIBRARIES} variable. The output was a little surprising: -- QT_LIBRARIES: /Users/Shared/Toolkits/Qt-4.4.3-UBDylib/lib/ libQtGui.dylib;-framework Carbon;-framework

[CMake] Fwd: Is it necessary to link a executable file?

-- Forwarded message -- From: ankit jain ankitgu...@gmail.com Date: 2009/2/4 Subject: Re: [CMake] Is it necessary to link a executable file? To: Eric Noulard eric.noul...@gmail.com 2009/2/4 Eric Noulard eric.noul...@gmail.com 2009/2/4 ankit jain ankitgu...@gmail.com:

Re: [CMake] Fwd: Fwd: Is it necessary to link a executable file?

2009/2/4 ankit jain ankitgu...@gmail.com: The CMakeLists iam using contains: PROJECT(hello) ADD_EXECUTABLE(hello h1.C) Error iam getting is: Linking CXX executable hello /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/../../../crt1.o(.text+0x18): In function `_start': : undefined reference

Re: [CMake] Fwd: Fwd: Is it necessary to link a executable file?

2009/2/4 Eric Noulard eric.noul...@gmail.com 2009/2/4 ankit jain ankitgu...@gmail.com: The CMakeLists iam using contains: PROJECT(hello) ADD_EXECUTABLE(hello h1.C) Error iam getting is: Linking CXX executable hello

[CMake] ctest with cmake without compiler

Hi, I'm looking for the switch that kills the compiler check in cmake. Is there such a switch? Through Google I found http://www.mail-archive.com/cmake@cmake.org/msg08245.html but the answer is not in there. Regards, Arjen ___ CMake mailing list

Re: [CMake] CMake Library Issues

OK, I finally found the problem. It seems that I was being silly and not being consistent with case in the project(X) call and the ${X_SOURCE_DIR} references. Everything is working as expected now, thanks for your help guys. On Wednesday 04 February 2009 12:19:11 Michael Jackson wrote: I

[CMake] integrating cmake projects and those built with legacy build systems

As I ponder moving our entire hairy system to cmake, I'm stuck with several sub-projects where I will not want to replace the existing build system. In particular we use internal builds of several FSF tools and when necessary to build one as part of building a cmake'd project we'll just want to

Re: [CMake] ctest with cmake without compiler

On Wednesday 04 February 2009, Verweij, Arjen wrote: Hi, I'm looking for the switch that kills the compiler check in cmake. Is there such a switch? Which problem do you have with the check ? It should work. Alex ___ CMake mailing list

Re: [CMake] timeout on total test time?

Thanks for the info, I'll use a workaround then ... Bram Bill Hoffman wrote: Bram de Greve wrote: Hello, Can anyone answer this question? I've tried the --test-timeout switch on ctest, but it seems to have no effect. Thanks, Bram Hi, Is it possible to specify the total amount of time

Re: [CMake] continuous build on a branch?

Weird, because that's exactly what I'm trying. I'll have a closer look. Bram Bill Hoffman wrote: Bram de Greve wrote: Hello, Does anyone know how I can fix this? I need a continuous build on a branch, but it keeps updating to the main branch This script does that:

Re: [CMake] ctest with cmake without compiler

Well, obviously the problem is requiring a compiler when it makes no sense. Like on test-only systems. Arjen From: cmake-boun...@cmake.org on behalf of Alexander Neundorf Sent: Wed 2/4/2009 7:49 PM To: cmake@cmake.org Subject: Re: [CMake] ctest with cmake

Re: [CMake] ctest with cmake without compiler

Verweij, Arjen wrote: Well, obviously the problem is requiring a compiler when it makes no sense. Like on test-only systems. Not that obvious project(FooBar NONE) That will stop CMake from enabling any compilers or languages. -Bill ___ CMake

[CMake] CMAKE_MFC_FLAG is inherited in subdirectory ?

Hello I have one cmakelists in which I do the following : set(CMAKE_MFC_FLAG 2) In the same cmakelists I am using add_subdirectory to add another project , and this makes my added directory with sub_directory to have set CMAKE_MFC_FLAG too ,which is not the behaviour I want . How to avoid this ?