On 6/9/07, Joshua Jensen <[EMAIL PROTECTED]> wrote:
Frankly, I'm ready to just dive in and add the support to the Visual
Studio project generators, mirroring much of the C++ support. I'd
actually only do the Visual Studio 2005 MSBuild support and MAYBE
VS2003, but it would lay the basis for oth
On 6/9/07, Brandon Van Every <[EMAIL PROTECTED]> wrote:
On 6/9/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
> ADD_CUSTOM_COMMAND(
> OUTPUT ${hellolib} ${helloexe}
> COMMAND make -C ${hellodir}
> COMMAND cp ${hellodir}/libhello.so ${hellolib}
> COMMAND cp ${hellodir}/hello ${hello
Brandon Van Every wrote:
On 6/6/07, Joshua Jensen <[EMAIL PROTECTED]> wrote:
So, for fun, I was trying to implement C# support through some extra
.cmake files.
It would be good to get a wiki page up about C# issues, so there's
some stickiness to various people's efforts. When I apply for game
Brandon Van Every wrote:
> CMake users: what source control systems are you using?
>
For my own projects, I've recently switched to git. After years of
using CVS, Subversion and a little of Perforce, git has clearly
surpassed them imo. I tried darcs and it was just too slow and painful
to use.
Pau Garcia i Quiles wrote:
The developers of Qyoto (the C# binding to Qt) have written a
FindMono.cmake which might be useful:
http://websvn.kde.org/trunk/KDE/kdebindings/cmake/modules/FindMono.cmake
This was useful, but I never really made it work well.
* ${CMAKE_CURRENT_SOURCE_DIR}/ must be
On 6/9/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
ADD_CUSTOM_COMMAND(
OUTPUT ${hellolib} ${helloexe}
COMMAND make -C ${hellodir}
COMMAND cp ${hellodir}/libhello.so ${hellolib}
COMMAND cp ${hellodir}/hello ${helloexe}
)
Unfortunately you've discovered the difference between fil
Alan W. Irwin wrote:
> On 2007-06-08 15:37-0400 Ajay Divekar wrote:
>
>> I tried your suggestion by setting
>>
>> SET_TARGET_PROPERTIES (bbb PROPERTIES LINK_FLAGS "-static -lc -lm
>> -L/usr/local/lib/")
>>
>> The result is the same i.e. the executable generated is not completely
>> static.
>> Stil
Brandon Van Every wrote:
CMake users: what source control systems are you using?
We were using Subversion, but we've migrated to Perforce.
Josh
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
For example, I have a project `test' which needs a 3rd-party software
`hello'. The directory structure looks like this:
test/test.c
test/CMakeLists.txt
test/build <-- I run cmake in this directory
test/hello/hello.c
test/hello/main.c
test/hello/Makefile
hello's Makefile will create a lib `test/
We just use CVS and Subversion. In fact we are migrating most of our CVS
projects stuff to Subversion.
Andrew
On 6/9/07, Brandon Van Every <[EMAIL PROTECTED]> wrote:
CMake users: what source control systems are you using?
The Dart dashboard can provide continuous or nightly build status on
t
On 6/8/07, Stuart Herring <[EMAIL PROTECTED]> wrote:
On 6/9/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
>
> but it failed to cmake. So how can I let two executables share one single
> object file?
>
You don't really want to.
Sometimes yes you really do. Not for this trivial example, but it's
On 6/9/07, Stuart Herring <[EMAIL PROTECTED]> wrote:
On 6/9/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
>
> but it failed to cmake. So how can I let two executables share one
single
> object file?
>
You don't really want to.
The cost of compiling the same source file twice is minimal, and it's
On 6/9/07, Clark J. Wang <[EMAIL PROTECTED]> wrote:
but it failed to cmake. So how can I let two executables share one single
object file?
You don't really want to.
The cost of compiling the same source file twice is minimal, and it's
much safer to compile them separately - it means that if yo
CMake users: what source control systems are you using?
The Dart dashboard can provide continuous or nightly build status on
the web for a CMake build. Dart supports CVS and Subversion, but
perhaps CMake users are using more than just that. If so, it's worth
putting a wiki entry together, so th
Take the followling CMakeLists.txt as an example:
PROJECT(test)
SET(CMAKE_VERBOSE_MAKEFILE ON)
ADD_EXECUTABLE(hello1 main.c hello1.c)
ADD_EXECUTABLE(hello2 main.c hello2.c)
When running make, main.c will be compiled twice which is not neccessary. I
tried to write like this:
PROJECT(test)
SET(CM
Hi there,
googling about the issue I'm about to ask, I could not find an answer on the
net (sorry if there is and I did not see it).
Assume you have 2 variables that an user can set up with ccmake, and assume
that the second one depends to the first:
SET(A "/usr/ CACHE STRING "A path"
On 6/8/07, Jon W <[EMAIL PROTECTED]> wrote:
I'm just beginning to learn cmake, and am trying to add the "/EHac-"
option to the additional command line options.
I'm setting the CMAKE_C_FLAGS as follows:
-
SET (MY_C_FLAGS "/EHac-")
MARK_AS_AD
On 6/8/07, Oliver Kullmann <[EMAIL PROTECTED]> wrote:
Alan W. Irwin wrote:
> I always run cmake with a separate build tree so one set of
> terminal windows is open in various sub-directories of the source tree and
> one set in various sub-directories of the build tree, and I now think of
> this
Hello,
Thanks for the many answers!
First some remarks to specific remarks I got and then what seems
best to do.
-
Alan W. Irwin wrote:
> I always run cmake with a separate build tree so one set of
> terminal windows is open in various sub-directories of the source tree
2007/6/9, Oliver Kullmann <[EMAIL PROTECTED]>:
Eric Noulard wrote:
> I think, that with some amount of time (not so much) for defining
> your own WHATEVER_EXECUTE CMake MACROs
> you'll get the power of what you add before
> with shell running in Makefile.
Should be possible; definitely it looks
On 6/8/07, abhijeet mhatre <[EMAIL PROTECTED]> wrote:
Could you tell me how to change the compiler in CMakeLists.txt ?
The compiler is the user's choice, not yours. Have the user run
CMakeSetup or CCMake and let them choose the compiler. You shouldn't
have a compiler hardwired into CMakeLis
On 2007-06-08 15:37-0400 Ajay Divekar wrote:
I tried your suggestion by setting
SET_TARGET_PROPERTIES (bbb PROPERTIES LINK_FLAGS "-static -lc -lm
-L/usr/local/lib/")
The result is the same i.e. the executable generated is not completely static.
Still has shared library dependencies. The output
2007/6/8, Ajay Divekar <[EMAIL PROTECTED]>:
I tried your suggestion by setting
SET_TARGET_PROPERTIES (bbb PROPERTIES LINK_FLAGS "-static -lc -lm
-L/usr/local/lib/")
The result is the same i.e. the executable generated is not completely static.
Still has shared library dependencies. The output g
I'm just beginning to learn cmake, and am trying to add the "/EHac-"
option to the additional command line options.
I'm setting the CMAKE_C_FLAGS as follows:
-
SET (MY_C_FLAGS "/EHac-")
MARK_AS_ADVANCED (MY_C_FLAGS)
SET (CMAKE_C_FLAGS "${CM
I tried your suggestion by setting
SET_TARGET_PROPERTIES (bbb PROPERTIES LINK_FLAGS "-static -lc -lm
-L/usr/local/lib/")
The result is the same i.e. the executable generated is not completely static.
Still has shared library dependencies. The output generated after doing ldd
bbb is
li
On 2007-06-08 14:37-0400 Ajay Divekar wrote:
I am trying to create a static executable and for that I have already defined
using ADD_Definitions the -static option.
But after it is build and when I do
ldd bbb (where bbb is the executable that was just generated)
The output of the above
Please keep the discussion on list so others may benefit from replies.
You can't presently change the compiler in CMakeLists.txt. And you cannot
change it after any CMake TRY_COMPILE commands have occurred without
starting over...
What you can do is this:
Set the environment variables C and CXX
I am trying to create a static executable and for that I have already defined
using ADD_Definitions the -static option.
But after it is build and when I do
ldd bbb (where bbb is the executable that was just generated)
The output of the above command is
libz.so.3 => /lib/libz.so.
HI David
Actually I wanted to change the compiler from g++ to m68k-g++ (compiler for
motorola architecture) so I just edited CMakeCache.txt where it was defined.
I think I did it all wrong and should have put something in CMakeLists.txt
instead of CMakeCache.txt.
Could you tell me how to
On Friday 08 Jun 2007 9:34:13 pm Brandon Van Every wrote:
> I'm pinging bug #3676 about this. I think this thread is evidence of
> why a Table Of Contents is desireable for the documentation, and why
> integrating FAQ material in the docs is also desireable. You can't
> get CMake's theory of oper
On 6/8/07, Brandon Van Every <[EMAIL PROTECTED]> wrote:
On 6/8/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
> Ok,
>
> I finally found out what was the issue. I cannot believe no one has
> had the issue in the past, as it seems like a pretty easy mistake to
> do:
>
> SET(deps foo.h bla.h)
>
On 6/8/07, David Cole <[EMAIL PROTECTED]> wrote:
Do *not* distribute CMakeCache.txt. It simply will not work. CMake must be
run against CMakeLists.txt to produce CMakeCache.txt (and all the rest of
the initial binary tree) on each target build machine...
I'm pinging bug #3676 about this. I thi
On 6/8/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
Ok,
I finally found out what was the issue. I cannot believe no one has
had the issue in the past, as it seems like a pretty easy mistake to
do:
SET(deps foo.h bla.h)
SEPARATE_ARGUMENTS(deps) # very very important !
ADD_CUSTOM_COMMAND(
On 6/8/07, gga <[EMAIL PROTECTED]> wrote:
mbers> Oliver Kullmann wrote:
>
> A lesser problem (likely) seems to be that there is no really fine-grained
> control over where all those auxiliary files go? It seems the basic assumption
> is that of having a build-directory (used only once), where all
Hello,
I created and built my solution with cmake (Visual Studio 8 2005 Win64)
on Windows XP 64 bit platform. When I opened and build the project in
VS2005, configurations of solution and projects turns to win32 from x64
although their configurations seem x64 in Visual Studio Solution
Explorer.
D
Oliver Kullmann wrote:
> The directory structure is "fractal" (or "recursive") and "dynamic", so
> for example modules have subdirectories Module/tests, containing generic
> tests for the components provided by the modules, where Module/tests might
> contain a tests-subdirectory itself for testing
Hi Oliver,
I think you already get a full set of valuable answer to your question.
And I would invite you as Bill said to prototype CMake usage
on real life subset of your project.
I would add some comments about the following:
2007/6/7, Oliver Kullmann <[EMAIL PROTECTED]>:
It appears now that
Brandon Van Every wrote:
On 6/7/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
On Thursday 07 June 2007 15:45, Oliver Kullmann wrote:
> Finally, it somehow seems to us that the conception of cmake is not
really
> that of a powerful extension of make, but more of a convenient
> "user-interf
Hello,
A couple of days ago I noticed something with the ";", too. If you
have a list (created either with SET or with LIST), when you try to
print it with MESSAGE( mylist ) elements are not separated by ";" but
if you print it with MESSAGE( "mylist" ) (with quotes), it will.
SET( mylist
Do *not* distribute CMakeCache.txt. It simply will not work. CMake must be
run against CMakeLists.txt to produce CMakeCache.txt (and all the rest of
the initial binary tree) on each target build machine...
On 6/8/07, abhijeet mhatre <[EMAIL PROTECTED]> wrote:
> Hi
> I configure cmake by wri
Ok,
I finally found out what was the issue. I cannot believe no one has
had the issue in the past, as it seems like a pretty easy mistake to
do:
SET(deps foo.h bla.h)
SEPARATE_ARGUMENTS(deps) # very very important !
ADD_CUSTOM_COMMAND(
OUTPUT ...
COMMAND ...
DEPENDS ${deps}
)
Hello,
Look at http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware and
the Modules directory in the CMake installation
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to the amount of work, I usually need 10 days to answer)
Quoting "martin.lavery" <[EMAIL PROTECTED]>:
Hi,
I'm
Hi,
I'm building a CMakeList.txt file and need to include a package like:
SET(OpenSceneGraph_DIR /OpenSceneGraph_DIR)
FIND_PACKAGE(OpenSceneGraph)
And when i try to build i get this error:
CMake Error: OpenSceneGraph_DIR is set to "/OpenSceneGraph_DIR",
which is not
a directory containing O
2007/6/8, Brandon Van Every <[EMAIL PROTECTED]>:
On 6/8/07, abhijeet mhatre <[EMAIL PROTECTED]> wrote:
>
> Suppose if I want distribute my project with the source code,
> CMake files and all, how do I do this? I dont mind regenerating
> build files using "cmake ." but I dont want to edit the CMak
subj
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
45 matches
Mail list logo
