Re: [CMake] rpath limitations of CMake for the Cygwin platform

2007-10-29 Thread Bill Hoffman
Alan W. Irwin wrote: I don't have access to Cygwin myself, but I have recently been getting PLplot feedback from one of our developers and also two of our more experienced users for that platform. From their detailed "make" and "make install" results it appears rpath is being completely ignored

[CMake] rpath limitations of CMake for the Cygwin platform

2007-10-29 Thread Alan W. Irwin
I don't have access to Cygwin myself, but I have recently been getting PLplot feedback from one of our developers and also two of our more experienced users for that platform. From their detailed "make" and "make install" results it appears rpath is being completely ignored both in the build tree

Re: [CMake] Trouble with CMake + Eclipse + SVN/CVS

2007-10-29 Thread Alexander Neundorf
On Sunday 28 October 2007, Eric Noulard wrote: > > I did update some Wiki pages and added a screencast describing > > (I hope) how to use eclipse with 2 projects: > > One for version handling > > One imported from CMake CDT4 generator > > Sorry here are the Wiki links: > http://www.cmake.org/Wiki/

Re: [CMake] Post CMake step

2007-10-29 Thread Brandon Van Every
On 10/29/07, Tal Blum <[EMAIL PROTECTED]> wrote: > > Is there a way to define a step in cmake that will do something after cmake > is run? Since I needed MSVC several solution files I used different > directories, each one with its own CMakeCashe.txt file. I want to create a > shortcut or a soft li

[CMake] Post CMake step

2007-10-29 Thread Tal Blum
Is there a way to define a step in cmake that will do something after cmake is run? Since I needed MSVC several solution files I used different directories, each one with its own CMakeCashe.txt file. I want to create a shortcut or a soft link to these files is there a way to run that command from w

Re: [CMake] library names

2007-10-29 Thread Mark Wyszomierski
You're right, I had one reference to "libutil" accidentally! Thanks, Mark On 10/29/07, Brandon Van Every <[EMAIL PROTECTED]> wrote: > On 10/29/07, Mark Wyszomierski <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I have a library project named "lib_util". > > > > When using CMake to build the library

Re: [CMake] Custom directories for QT4

2007-10-29 Thread Marcin Gil
Dnia poniedziałek, 29 października 2007, Andreas Pakulat napisał: > I may be overlooking something, but the usual use-case for this with > QMake is to either not clutter the source tree with buildfiles or to > have different output directories for different build-configurations. > > Neither of the

Re: [CMake] library names

2007-10-29 Thread Brandon Van Every
On 10/29/07, Mark Wyszomierski <[EMAIL PROTECTED]> wrote: > Hi, > > I have a library project named "lib_util". > > When using CMake to build the library (with g++), the output file is: > > liblib_util.a > > Now another sub project needs to link to that, and has the following > in CMakeLists.txt

Re: [CMake] ctest script and setting my own envvars

2007-10-29 Thread David Cole
It's a substitution thing This: SET (CTEST_ENVIRONMENT "RR_WARNINGS_COMMON=-Wall -Wextra" "RR_WARNINGS_C=${RR_WARNINGS_COMMON} -Wno-deprecated-declarations" ) doesn't work because RR_WARNINGS_COMMON is not defined as a CMake variable prior to the SET statement. This should work,

[CMake] library names

2007-10-29 Thread Mark Wyszomierski
Hi, I have a library project named "lib_util". When using CMake to build the library (with g++), the output file is: liblib_util.a Now another sub project needs to link to that, and has the following in CMakeLists.txt: target_link_libraries(my_app, lib_util) but when compiling my_app,

Re: [CMake] Custom directories for QT4

2007-10-29 Thread Mike Jackson
No.. and here is why. If you open the FindQt4.cmake file that Cmake installs and look for MACRO (QT4_WRAP_UI outfiles ) you can see exactly what cmake is going to do. MACRO (QT4_WRAP_UI outfiles ) FOREACH (it ${ARGN}) GET_FILENAME_COMPONENT(outfile ${it} NAME_WE) GET_FILENAM

[CMake] ctest script and setting my own envvars

2007-10-29 Thread Sean McBride
Hi all, If I create a ctest script (.cmake), can I set my own environment variables? I have the following: # set any extra envionment varibles here SET (CTEST_ENVIRONMENT "RR_WARNINGS_COMMON=-Wall -Wextra" "RR_WARNINGS_C=${RR_WARNINGS_COMMON} -Wno-deprecated-declarations" "RR_WARNINGS_CXX=${RR_W

Re: [CMake] Custom directories for QT4

2007-10-29 Thread Andreas Pakulat
On Montag, 29. Oktober 2007, Marcin Gil wrote: > Hi! > > Using qmake and it's project files one can define locations eg for > moc/ui parsed files. > The variables are UI_DIR for UI generated headers location and > MOC_DIR for moc generated files. > > Simply setting set (UI_DIR ui) doesn't work. > >

[CMake] Custom directories for QT4

2007-10-29 Thread Marcin Gil
Hi! Using qmake and it's project files one can define locations eg for moc/ui parsed files. The variables are UI_DIR for UI generated headers location and MOC_DIR for moc generated files. Simply setting set (UI_DIR ui) doesn't work. Is there a way to force generation of those files to directorie