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 CMakeLists.txt
and CMakeCache.txt when I distriubute my proj
> Hi
> I configure cmake by writing a CMakeLists.txt file in a source
folder.
> It runs fine.
>
> Now if I move the folder to some other location, cmake complains that
the
> files still refer to the previous location. Then I have to edit
> CMakeCache.txt and replace the project path at 3-4 the
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-interface", with the typical trade
Hi,
On Thursday 07 June 2007 15:45, Oliver Kullmann wrote:
> Hello,
>
...
> 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 migh
On 2007-06-07 20:45+0100 Oliver Kullmann wrote:
It appears now that the computational power of cmake is rather restricted?
There seem to be no functions?? (While we had hoped that there are many
more than in make?) Even just a shell-call seems to need to be programmed
by ourselves?? (I can't bel
2007/6/7, Brandon Van Every <[EMAIL PROTECTED]>:
On 6/7/07, Jesper Eskilson <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I would like to be able to create a static library on Windows which
> includes an import library to a DLL, so that users of the static
> library do not need to specify the import
Hello,
We are currently in the process of evaluating whether we shall/can
update our build system from make to cmake. We see several problems,
which we would like to post here, hoping about enlightenment
on how to solve these problems (or not(!)).
Perhaps a few words about the project: It's about
On 6/7/07, abhijeet mhatre <[EMAIL PROTECTED]> wrote:
Hi
I configure cmake by writing a CMakeLists.txt file in a source folder.
It runs fine.
Now if I move the folder to some other location, cmake complains that the
files still refer to the previous location. Then I have to edit
CMakeCache.txt
On 6/7/07, Jesper Eskilson <[EMAIL PROTECTED]> wrote:
Hi all,
I would like to be able to create a static library on Windows which
includes an import library to a DLL, so that users of the static
library do not need to specify the import library.
By chance, is your library a C library that is c
Mathieu Malaterre wrote:
> It looks like you are on windows. Could you please try a nmake ("NMake
> Makefiles") build and do:
>
I'm on Linux (thank god), but have also a windows box with vnc.
I tried it on both, with cmake2.5 (CVS), but cmake2.4 should be the same
( I was using it before ).
> 1)
You cannot move a configured project. If you move it you need to clean
the build folder and then run cmake again after the move.
Warm regards,
Kishore
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of abhijeet mhatre
Sent: Thursday, June 07, 2
Hi
I configure cmake by writing a CMakeLists.txt file in a source folder.
It runs fine.
Now if I move the folder to some other location, cmake complains that the files
still refer to the previous location. Then I have to edit CMakeCache.txt and
replace the project path at 3-4 there. Then it w
On 6/7/07, gga <[EMAIL PROTECTED]> wrote:
Mathieu Malaterre wrote:
> Example, your foo.i depends on bla.h. First time your configure,
> dependency will be right, for instance:
>
> Makefile:
> ...
> foo_wrap.cpp: foo.i
> foo_wrap.cpp: bla.h
> swig -o foo_wrap.cpp foo.i
>
> but now edit your foo.i
Mathieu Malaterre wrote:
> Example, your foo.i depends on bla.h. First time your configure,
> dependency will be right, for instance:
>
> Makefile:
> ...
> foo_wrap.cpp: foo.i
> foo_wrap.cpp: bla.h
> swig -o foo_wrap.cpp foo.i
>
> but now edit your foo.i file and add a new header file 'bar.h'. Th
On 6/7/07, gga <[EMAIL PROTECTED]> wrote:
Mathieu Malaterre wrote:
> This is a follow up on a previous post.
>
> I have written a simple dependency scanner macro (*). There is still
> one dependency missing:
> I need to reexecute the CMake macro every time the swig *.i file is
> modified.
>
> How
Hi all,
I would like to be able to create a static library on Windows which
includes an import library to a DLL, so that users of the static
library do not need to specify the import library.
CMake does not allow me to do this.
TARGET_LINK_LIBRARIES( FooLib BarLib )
does not work when creating
2007/6/6, Sylvain Benner <[EMAIL PROTECTED]>:
Jon W a écrit :
> Are there any tools available to convert Visual Studio files to
> cmakelists.txt? I have hundreds of vcproj files and this would help
> make the conversion to cmake easier.
I don't know if there are some tools to do this. If you do
Mathieu Malaterre wrote:
> This is a follow up on a previous post.
>
> I have written a simple dependency scanner macro (*). There is still
> one dependency missing:
> I need to reexecute the CMake macro every time the swig *.i file is
> modified.
>
> How do I do that ?
>
You don't. You add th
This is a follow up on a previous post.
I have written a simple dependency scanner macro (*). There is still
one dependency missing:
I need to reexecute the CMake macro every time the swig *.i file is modified.
How do I do that ?
Thanks
-Mathieu
(*)
On 5/30/07, Mathieu Malaterre <[EMAIL PROTE
Alexander Ivash wrote:
> Hello, cmake.
>
> Is the subj is possible? I have two cmake-managed projects: the library
and tests. And this tests need to
> be linked against the library. How can I get such result? (Of course I can
place tests and library into
> the same cmakelists.txt, but I think ther
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
development jobs, I typic
Andreas Beckermann <[EMAIL PROTECTED]> writes:
> The pkg_check_modules() macro works mostly fine (thanks a lot, btw,
> this saved me a lot of work), however I have one problem with it: once
> it checked whether the modules are available, it defines a variable
> __pkg_config_checked_ in CMakeCache.
22 matches
Mail list logo