> > Kishore, Jonnalagadda (IE10) wrote:
> > > Is there a variable with all the compile options concatenated? A
> > > variable with common CMAKE_C_FLAGS +
> CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
> > > ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
> > >
> > >
> > >
> > > I am looking for this for passing th
> Kishore, Jonnalagadda (IE10) wrote:
> > Is there a variable with all the compile options concatenated? A
> > variable with common CMAKE_C_FLAGS +
CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
> > ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
> >
> >
> >
> > I am looking for this for passing them to the assemble
I did try to do that. However, the generated target is empty and the
generarated header file is not part of the project. If I try to make it part
of another library (the one where it gets included) the library does not
pick the newest version of the file. The thing I do not know is how to use
A
Min Cu wrote:
Yes, that is more or less what I need. I have a project that generates
a header file which is included in other projects. However, once the
project is built when make is called the next time it does not get
rebuilt. So, I guess my question is "How do I make the custom target
run
Yes, that is more or less what I need. I have a project that generates a
header file which is included in other projects. However, once the project
is built when make is called the next time it does not get rebuilt. So, I
guess my question is "How do I make the custom target run every built?" Th
> That starts to be off-topic on this CMake list, so either we move it to the
> CppUnit list, or you can contact me directly.
For those interested in the topic or with similar problem -
I moved the discussion to
http://sourceforge.net/forum/forum.php?thread_id=1702314&forum_id=37108
Thanks,
Matthew Woehlke wrote:
Bill Hoffman wrote:
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, ot
Bill Hoffman wrote:
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
HS>
HS> #!/bin/sh
HS> for i in *.c; do
HS> echo
HS> done
HS>
HS> Something like that? You can write the proper file lists to an extra .cmake
HS> file and include that into the CMakeLists.txt file or use a template file.
Yes, and I'm able to write these
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
I also can't seem to
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure rate
in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
I also can't seem to find any output from th
On Monday 26 Mar 2007 at 11:08:07 pm, Filipe Sousa wrote:
> > What are variables where the information for each of the above is
> > stored? Especially for ADD_DEFINITIONS and INCLUDE_DIRECTORIES.
>
> GET_DIRECTORY_PROPERTY(defs DEFINITIONS)
> GET_DIRECTORY_PROPERTY(includes INCLUDE_DIRECTORIES)
I
Kishore, Jonnalagadda (IE10) wrote:
> Is there a variable with all the compile options concatenated? A
> variable with common CMAKE_C_FLAGS + CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
> ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
>
>
>
> I am looking for this for passing them to the assembler macro wher
Am Montag 26 März 2007 19:17 schrieb Michael Bieber:
> HS> Did you try adding a PROJECT call to every lib's CMakeLists.txt file?
> HS> Then run make -G ... on the top-level CmakeLists.txt file.
>
> No, I'm fiddling with a single lib for the moment.
>
>
> HS> It's in the FAQ why this is not a good i
HS> Did you try adding a PROJECT call to every lib's CMakeLists.txt file?
HS> Then run make -G ... on the top-level CmakeLists.txt file.
No, I'm fiddling with a single lib for the moment.
HS> It's in the FAQ why this is not a good idea (well, you will miss some good
HS> features) and you are for
Am Montag 26 März 2007 12:03 schrieb Michael Bieber:
> qmake is able to write VS projects for every lib and the executable
> preserving the given directory structure. How can I achieve the same thing
> with cmake? My globbing attempts turned the structure into plain
> header/source source groups.
I would really appreciate anyone who can throw more light to explain the
role of the PROJECT command.
Here is why. I have a CMakeLists.txt in top level source tree and it
contains:
MESSAGE("CMAKE_C_LINK_EXECUTABLE = ${CMAKE_C_LINK_EXECUTABLE}
FLAGS = ${FLAGS}
CMA
Is there a variable with all the compile options concatenated? A
variable with common CMAKE_C_FLAGS + CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
I am looking for this for passing them to the assembler macro where I
use ADD_CUSTOM_COMMAND.
What are variables
2007/3/26, Bill Hoffman <[EMAIL PROTECTED]>:
Philip Lowman wrote:
> Min Cu wrote:
>> I have a project which needs to be rebuild every time make is called
>> (whether the project has changed or not). How do I do it?
[...]
Well, I suppose you could do something like this.
Write a program t
Philip Lowman wrote:
Min Cu wrote:
I have a project which needs to be rebuild every time make is called
(whether the project has changed or not). How do I do it?
One simple approach would simply be to remove CMakeCache.txt, run
cmake from scratch and then type make.
That will not cause eve
Min Cu wrote:
I have a project which needs to be rebuild every time make is called
(whether the project has changed or not). How do I do it?
Thanks,
Min
_
Solve the Conspiracy and win fantastic prizes.
http://www.theconspiracyga
Min Cu wrote:
I have a project which needs to be rebuild every time make is called
(whether the project has changed or not). How do I do it?
One simple approach would simply be to remove CMakeCache.txt, run cmake
from scratch and then type make.
There's probably a better way though.
--
Phil
Bill Hoffman wrote:
Most files cmake writes out are copy if different. So, cmake writes a
file, then diff's it with the
file that was already there, and if they are different it gets rid of
the original and moves the new
file into place. This is to avoid too many reloads and other side
effects
[EMAIL PROTECTED] wrote:
Hi all!
I'm trying to integrate cppunit tests using cmake in our ims library and
cannot solve the problem how to build tests executables only by demand,
i.e. by calling 'make test'. I'm quite new to cmake and don't know if this
is possible at all, but I suppose it should
Patrick Gelin wrote:
In this case it should work.Can you create a small cmake test file:
CMakeLists.txt:---
add_library(foo foo.c)
--end CMakeLists.txt-
put that in a directory by itself. Then do this:
touch foo.c
mkdir b
cd b
cmake ..
And post all the output.
i
On Monday 26 March 2007 01:49:10 [EMAIL PROTECTED] wrote:
> Hi Pascal,
>
> wow, thank you for your response - that helped a lot!
Happy to hear it :-)
> After some struggles, I got it to register one test, and to execute it.
> Great. But, if I add two tests, both get registered, but only one gets
Hi all!
I'm trying to integrate cppunit tests using cmake in our ims library and
cannot solve the problem how to build tests executables only by demand,
i.e. by calling 'make test'. I'm quite new to cmake and don't know if this
is possible at all, but I suppose it should be possible :-)
I have fou
Precompiled headers are too good to bypass. Ideally, support for these
should be built in CMake.
After playing with 1260-PCHSupport.cmake for some time to get it working for
Windows, I realized that a much simpler approach would be possible.
Specifically, having to set & change the build type ever
@list,
I'm a new cmake user with a history in using qmake. The following seems
a FAQ to me, but I'm still unable to find a solution:
I have a 100 KLOC project here, splitted in some static libs and a single
executable.
Simplified source tree:
./lib_0
|
|- basic
|- gui
|- other_stuff_enc
Kishore, Jonnalagadda (IE10) wrote:
>> I have problems with ADD_DEFINITIONS : I have two target in my
>> CMakeLists which I'd like to have different -D flags. If I add
>> ADD_DEFINITIONS, it seems like both targets are affected. How coul I
> do
>> such thing ?
>
> You have two options.
>
> 1) Set
I have a project which needs to be rebuild every time make is called
(whether the project has changed or not). How do I do it?
Thanks,
Min
_
Solve the Conspiracy and win fantastic prizes.
http://www.theconspiracygame.co.uk/
___
31 matches
Mail list logo
