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 ?
T
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
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 withou
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:
http://www.cdash.org/CDas
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 CTe
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
CMake@cma
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 del
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 don'
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
CMak
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 AppKit;/Use
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)
set(ADDITIONAL_INCLUDE
Thanks for the clarification on that. I did figure out the set
(variable ${varaible}) part though as a work-around.
Just my opinion but that is not very intuitive. Now that I know how
to deal with it I guess it is ok.
Thanks
---
Mike Jackson www.bluequartz.net
On Feb 4, 2
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 wan
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 val
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.
__
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
wrote:
> Hi,
>
> I want to glob directories from a specified location, but unable to do so.
> My purpose is to run cmake and gene
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
/path/to/so
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:
2009/2/4 Eric Noulard
> 2009/2/4 ankit jain :
> >
> > 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
> > fu
2009/2/4 ankit jain :
>
> 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 to `main'
-- Forwarded message --
From: ankit jain
Date: 2009/2/4
Subject: Re: [CMake] Fwd: Is it necessary to link a executable file?
To: Eric Noulard
2009/2/4 Eric Noulard
2009/2/4 ankit jain :
> >>
> >> 2009/2/4 ankit jain :
> >>
> >> > Actually in this case i dont want to create
2009/2/4 ankit jain :
>>
>> 2009/2/4 ankit jain :
>>
>> > 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 using that only
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
-- Forwarded message --
From: ankit jain
Date: 2009/2/4
Subject: Re: [CMake] Is it necessary to link a executable file?
To: Eric Noulard
2009/2/4 Eric Noulard
2009/2/4 ankit jain :
>
> > Actually in this case i dont want to create libraries thats why iam
> > wondering whethe
2009/2/4 ankit jain :
> 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 mailing list
CMake@cmake.
2009/2/4 ankit jain
> 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 o
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 any
27 matches
Mail list logo