On 28.07.10 19:19:08, Óscar Fuentes wrote:
> For creating a file at build time with a content like this:
>
> #define foo "bar"
>
> I use this on Linux:
>
> add_custom_command(OUTPUT buildobj.h
> COMMAND ${CMAKE_COMMAND} -E echo "\\#define foo \\\"bar\\\""
> > buildobj.h
> )
>
> but that d
On 29.07.10 08:37:36, Michael Wild wrote:
>
> On 29. Jul, 2010, at 6:37 , Óscar Fuentes wrote:
>
> > Michael Wild writes:
> >
> > [snip]
> >
> >> Perhaps you need to tell us what it is that you are trying to achieve,
> >> because I suspect that you are over-thinking things and that there is
>
On 29. Jul, 2010, at 7:51 , Dieter Oberkofler wrote:
> A couple of questions regarding the warning levels when compiling:
> 1) Is there a "preferred" way to change the warning level in CMake?
> 2) What is the default warning level CMake is using when compiling and how
> can it be defined?
> Thank
On 29. Jul, 2010, at 6:37 , Óscar Fuentes wrote:
> Michael Wild writes:
>
> [snip]
>
>> Perhaps you need to tell us what it is that you are trying to achieve,
>> because I suspect that you are over-thinking things and that there is
>> a much simpler solution. E.g. what should buildobj.h contai
A couple of questions regarding the warning levels when compiling:
1) Is there a "preferred" way to change the warning level in CMake?
2) What is the default warning level CMake is using when compiling and how
can it be defined?
Thank you,
-D
___
Powered
Michael Wild writes:
[snip]
> Perhaps you need to tell us what it is that you are trying to achieve,
> because I suspect that you are over-thinking things and that there is
> a much simpler solution. E.g. what should buildobj.h contain
> (semantically, not the exact strings), and why is it only
On 29. Jul, 2010, at 4:19 , Óscar Fuentes wrote:
> Eric Noulard
> writes:
>
>> I think you are wrong.
>>
>> May be you can try the attach script.
>>
>> try:
>> cmake -DYOURSTRING="I like # \ it" -DTHE_FILE=toto.txt -P writeany.cmake
>>
>> You shouldn't have "quite" problem with the previous
Eric Noulard
writes:
> I think you are wrong.
>
> May be you can try the attach script.
>
> try:
> cmake -DYOURSTRING="I like # \ it" -DTHE_FILE=toto.txt -P writeany.cmake
>
> You shouldn't have "quite" problem with the previous approach.
I tried this on Linux:
add_custom_command(OUTPUT ${EMACS
On Wednesday 28 Jul 2010 10:01:42 pm Eric Noulard wrote:
> 2010/7/28 Kishore :
> >> bash-completion 1:1.2-2
> >
> > bash-completion 1:1.1-3ubuntu2
>
> I think I know why. The missing functions may comes with bash-completion
> 1.2 you have 1.1.
>
> Would you try the attach file it should wo
Alexander Neundorf writes:
> ...not sure about that dot here.
>
> Do you have something like
> include_directories ( . )
> in your CMakeLists.txt ?
Okay, problem solved. I was adding the directories with
add_definitions(-I...)
instead of include_directories(...)
Thank you, Alex.
[snip]
All,
I am having a problem generating the Java wrappers for VTK 5.6.0 using
CMAKE 2.8.2. The problem is the shared libraries are all prefixed with
"lib" (the unix style specification), even though I am using WinXP. the
System.loadLibrary("vtkCommonJava") which should be portable between
JVM's
Got it - was using a VTK macro for third_party inclusion that was
using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
Thanks!
CY
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/openso
On Thursday 29 July 2010, Óscar Fuentes wrote:
> Óscar Fuentes writes:
> > Alexander Neundorf
> >
> > writes:
> >>> In the C.includescache file config.h is mentioned, twice. So the
> >>> dependency scanner detects the file, but then it is ignored. The
> >>> config.h file is in D:/dev/other/emacs/
Óscar Fuentes writes:
> Alexander Neundorf
> writes:
>
>>> In the C.includescache file config.h is mentioned, twice. So the
>>> dependency scanner detects the file, but then it is ignored. The
>>> config.h file is in D:/dev/other/emacs/qbuild/src/config.h (the build
>>> directory.) This is an ex
Alexander Neundorf
writes:
>> In the C.includescache file config.h is mentioned, twice. So the
>> dependency scanner detects the file, but then it is ignored. The
>> config.h file is in D:/dev/other/emacs/qbuild/src/config.h (the build
>> directory.) This is an excerpt of C.includescache:
>>
>> D
2010/7/28 Clifford Yapp :
> Ironically, I now see this issue (almost exactly) was discussed long ago:
>
> http://www.cmake.org/pipermail/cmake/2005-September/007204.html
>
> However, when I try:
>
> get_directory_property(PNG_LIB_NAME DIRECTORY src/other/libpng
> DEFINITION PNG_LIB_NAME)
> MESSAGE(
Ironically, I now see this issue (almost exactly) was discussed long ago:
http://www.cmake.org/pipermail/cmake/2005-September/007204.html
However, when I try:
get_directory_property(PNG_LIB_NAME DIRECTORY src/other/libpng
DEFINITION PNG_LIB_NAME)
MESSAGE("getdirprop: ${PNG_LIB_NAME}")
I get not
On Tuesday 27 July 2010, j wrote:
> Hi there,
>
> I have a CMakeLists.txt that succesfully describes a project
> that can be built for XCode MACOSX10.6.sdk and Microsoft Visual
> studio. So far so good. Now I'm trying to generate an XCode project
> for the iPhone-3.2.sdk which doesn't seem to work.
On Wednesday 28 July 2010, Óscar Fuentes wrote:
> Eric Noulard writes:
> > 2010/7/28 Óscar Fuentes :
> >> I'm using cmake 2.8.2 on Linux/make and on Windows/make-mingw32
> >>
> >> The project configures a template config.cmake producing config.h. That
> >> header is included by all C files on the
2010/7/28 Óscar Fuentes :
> Eric Noulard
> writes:
>
> [snip]
>
>> if you need build
>> time creation of the file then you may write a CMake script
>> "generateMyFile.cmake" which contains such commands and use
>>
>> add_custom_command( ...
>> COMMAND ${CMAKE_COMMAND} -P generateMyFile.cmake
>>
Today, I discovered than in the special case of a substituted
PROJECT_SOURCE_DIR,
all build files for subdir packages are created in PROJECT_SOURCE_DIR
and not at the PROJECT_BINARY_DIR.
I use windows cmd shell
subst w: z:/some/deep/path/to/source/dir
Than I create a new build dir:
Am Wednesday 28 July 2010 schrieb Óscar Fuentes:
> Eric Noulard
> writes:
>
> [snip]
>
> > if you need build
> >
time creation of the file then you may write a CMake script
> >
"generateMyFile.cmake" which contains such commands and use
> >
> >
add_custom_command( ...
> >
> > COMMAND ${CMAKE
Eric Noulard
writes:
[snip]
> if you need build
> time creation of the file then you may write a CMake script
> "generateMyFile.cmake" which contains such commands and use
>
> add_custom_command( ...
> COMMAND ${CMAKE_COMMAND} -P generateMyFile.cmake
>...)
That approach justs shifts t
2010/7/28 Óscar Fuentes :
> For creating a file at build time with a content like this:
>
> #define foo "bar"
>
> I use this on Linux:
>
> add_custom_command(OUTPUT buildobj.h
> COMMAND ${CMAKE_COMMAND} -E echo "\\#define foo \\\"bar\\\""
> > buildobj.h
> )
>
> but that doesn't work on Windows,
For creating a file at build time with a content like this:
#define foo "bar"
I use this on Linux:
add_custom_command(OUTPUT buildobj.h
COMMAND ${CMAKE_COMMAND} -E echo "\\#define foo \\\"bar\\\""
> buildobj.h
)
but that doesn't work on Windows, because it outpus:
\#define foo "bar"
Rem
OK, I've had more time to play with CMake and subdirectory
CMakeList.txt files, and I'm getting close to the behavior I want. I
can conditionally override key variables to use either local or system
versions of a library, and I can trigger the builds conditionally as
well. Using the strings defin
2010/2/13 Thawan Kooburat :
> Hi,
>
> I created a patch for CPack Debian generator. Here is the list of my
> modification
>
> - Automatically generate dependency list if dpkg-shlibdeps utility is
> presented.
> 1. Detect if dpkg-shlibdeps is existed in the system
> 2. Use "find" and "f
2010/7/28 Kishore :
>>
>> bash-completion 1:1.2-2
>
> bash-completion 1:1.1-3ubuntu2
I think I know why. The missing functions may comes with bash-completion 1.2
you have 1.1.
Would you try the attach file it should work with 1.1 (and 1.2)
--
Erk
Membre de l'April - « promouvoir et défen
I think if you look in the actual cmake project itself there are tests
for doing installs. Not sure if that is what you are after or not.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack..
The easiest way to separate output is to wrap your test in a cmake -P
script, and then inside that call execute_process to run the "real test" and
use its facilities to capture output into variables or redirect output to
files.
There is no redirection of output using add_test arguments.
HTH,
Dav
Eric Noulard writes:
> 2010/7/28 Óscar Fuentes :
>> I'm using cmake 2.8.2 on Linux/make and on Windows/make-mingw32
>>
>> The project configures a template config.cmake producing config.h. That
>> header is included by all C files on the project.
>>
>> While building in-source, touching config.h
Hi,
I'd like to run some static analysis tool from CTest. (2.8.1)
I've added enable_testing() and add_test() calls in my CMakeLists.txt
file, and the static analysis tool is invoked as expected, however:
* CTest discards both the tool standard output and tool standard
error stream when ran with
On Wednesday 28 Jul 2010 7:07:20 pm Eric Noulard wrote:
> 2010/7/28 Kishore :
> > On Tuesday 27 Jul 2010 6:05:59 pm Eric Noulard wrote:
> >> 2010/7/27 Eric Noulard :
> >> > Here comes a proposal for a bash completion for cmake. Should work
> >> > with almost any cmake version because it's using cma
Hi all,
I have some tests that require running a CPack install before they can
be run. I'm sure I can figure out a way to do this, but just wondered if there
was any common recipe out there for doing it? My google-fu and CMake wiki
search didn't turn up anything obvious.
Thanks,
Kelly
2010/7/28 Kishore :
> On Tuesday 27 Jul 2010 6:05:59 pm Eric Noulard wrote:
>> 2010/7/27 Eric Noulard :
>> > Here comes a proposal for a bash completion for cmake. Should work with
>> > almost any cmake version because it's using cmake command to retrieve
>> > completion.
>> >
>> > Prerequisite: Yo
On 07/27/2010 06:48 PM, Russell Harmon wrote:
> We're looking to use cmake on a project which has some dependencies
> which are not properly picked up by cmake's dependency scanner. I'm not
> looking to fix the scanner, because I feel the scanner is fundamentally
> broken:
Yes, it certainly has so
On 28. Jul, 2010, at 10:57 , Ingolf Steinbach wrote:
> 2010/7/28 Michael Wild :
>> Are those libraries only "convenience" libraries? I.e. are you ever going to
>> install them? If not, just list the source-files in the top-level
>> CMakeLists.txt:
>>
>>
>> add_executable(super-duper
>> modul
2010/7/28 Michael Wild :
> Are those libraries only "convenience" libraries? I.e. are you ever going to
> install them? If not, just list the source-files in the top-level
> CMakeLists.txt:
>
>
> add_executable(super-duper
> modul1/modul1.c
> module2/module2.c
> )
Even if they are not going t
On 28. Jul, 2010, at 9:32 , Matthias Goesswein wrote:
> Am 27.07.2010 20:01, schrieb Alexander Neundorf:
>> On Tuesday 27 July 2010, Matthias Gwein wrote:
>>> Hello!
>>>
>>> I'm using cmake 2.8.2 and I'd like to build a library of libraries and
>>> i have no additional source code.
>>> I tried s
Am 27.07.2010 20:01, schrieb Alexander Neundorf:
On Tuesday 27 July 2010, Matthias Gwein wrote:
Hello!
I'm using cmake 2.8.2 and I'd like to build a library of libraries and
i have no additional source code.
I tried something like that:
add_library(mylib )
target_link_libraries(mylib lib1 lib2
40 matches
Mail list logo