Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Alan W. Irwin wrote: It appears the 2.4.5 version of UsePkgConfig.cmake is what you need. I therefore believe the current approach in cvs (although it works consistently for PLplot for 2.4.5 and cvs version) is attempting the impossible; emulate the old behaviour by using the modern macros with

Re: [CMake] Weird if nesting problem

On 2006-12-05 20:05-0800 Brandon J. Van Every wrote: Alan W. Irwin wrote: On 2006-12-05 14:44-0700 James Bigler wrote: CMake barfs on the first IF(EXISTS ${PARSER_EXECUTABLE}), probably because it is trying to evaluate if this expression is part of the ENDIF or something. It does this with 2

Re: [CMake] Weird if nesting problem

Alan W. Irwin wrote: On 2006-12-05 14:44-0700 James Bigler wrote: CMake barfs on the first IF(EXISTS ${PARSER_EXECUTABLE}), probably because it is trying to evaluate if this expression is part of the ENDIF or something. It does this with 2.2.3, 2.4.3, 2.4.5 on Linux. Try IF(EXISTS ${PARSER_E

Re: [CMake] Weird if nesting problem

James Bigler wrote: FIND_PROGRAM(PARSER_EXECUTABLE NAMES my_parser PATHS ${PARSER_DIR} ) IF(EXISTS ${PARSER_EXECUTABLE}) SET(PARSERS_FOUND 1) ELSE(EXISTS ${PARSER_EXECUTABLE}) SET(PARSERS_FOUND 0) ENDIF(EXISTS ${PARSER_EXECUTABLE}) CMake Error: Error in cmake code at

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 2006-12-05 20:09-0500 Bill Hoffman wrote: Alan W. Irwin wrote: Therefore, I suggest the following improved proposal to take care of these compatibility issues exactly. 1) Copy the 2.4.5 UsePkgConfig.cmake which defines the PKGCONFIG macro to CVS with the only change being to add a message t

Re: [CMake] more on an executable dependency on external library

Crni Gorac wrote: OK, I've tried in the meantime various arrangements with ADD_CUSTOM_TARGET(), but seems hard to employ it to have CMake to put following simple dependency of an executable "foo" on system library "libbar.a" into generated Makefile: foo: /usr/local/lib/libbar.a There exists of c

Re: [CMake] Re: Library linkage spewage under Makefiles (make -s)

James Bigler wrote: I found one way around it, and perhaps this is the way it should have been done with respect to cmake created makefiles: SET(CMAKE_VERBOSE_MAKEFILES OFF) Then from the command line you can turn on chattiness like so: make VERBOSE=1 I've tested this with 2.2.3 and 2.4.5.

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Alan W. Irwin wrote: On 2006-12-05 23:51+0100 Michel Hermier wrote: Alan W. Irwin wrote: On 2006-12-05 22:31+0100 Michel Hermier wrote: Do you have a case where something works in CMake-2.4.4, but does not work in CVS CMake that uses UsePkgConfig.cmake? If so, we will fix it. If this is n

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 2006-12-05 23:51+0100 Michel Hermier wrote: Alan W. Irwin wrote: On 2006-12-05 22:31+0100 Michel Hermier wrote: Do you have a case where something works in CMake-2.4.4, but does not work in CVS CMake that uses UsePkgConfig.cmake? If so, we will fix it. If this is new stuff, we can not c

Re: [CMake] FindPerlLibs.cmake and FindSwig.cmake outdated!

On 12/5/06, Axel Roebel <[EMAIL PROTECTED]> wrote: Hi, I just started to add swig support to our project http://sourceforge.net/projects/sdif. The project supports swig bindings to perl, python and java. I instantly tried the available cmake modules: notably FindSWIG.cmake and FindPerlLibs.cmak

[CMake] FindPerlLibs.cmake and FindSwig.cmake outdated!

Hi, I just started to add swig support to our project http://sourceforge.net/projects/sdif. The project supports swig bindings to perl, python and java. I instantly tried the available cmake modules: notably FindSWIG.cmake and FindPerlLibs.cmake I was pretty astonished to find that these two

[CMake] Re: Library linkage spewage under Makefiles (make -s)

James Bigler wrote: James Bigler wrote: In 2.2 when you specified SET(CMAKE_VERBOSE_MAKEFILE ON) and then did "make -s" you got some nice looking output of what you were building. Now with 2.4 it's all pretty and colored (nice!), but whenever I link a library I get what appears to be the cont

Re: [CMake] Weird if nesting problem

On 2006-12-05 14:44-0700 James Bigler wrote: CMake barfs on the first IF(EXISTS ${PARSER_EXECUTABLE}), probably because it is trying to evaluate if this expression is part of the ENDIF or something. It does this with 2.2.3, 2.4.3, 2.4.5 on Linux. Try IF(EXISTS ${PARSER_EXECUTABLE}) ==> IF(EXI

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Alan W. Irwin wrote: On 2006-12-05 22:31+0100 Michel Hermier wrote: Do you have a case where something works in CMake-2.4.4, but does not work in CVS CMake that uses UsePkgConfig.cmake? If so, we will fix it. If this is new stuff, we can not change UsePkgConfig.cmake because it will break o

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 2006-12-05 16:54-0500 Bill Hoffman wrote: I checked the generation of the qca.pc file and it was not updated for 2 month so it was definitely working before the update. And to be really sure I reverted to the old file, and now it works again for me and when I look at the code again, it defi

[CMake] Re: Library linkage spewage under Makefiles (make -s)

James Bigler wrote: In 2.2 when you specified SET(CMAKE_VERBOSE_MAKEFILE ON) and then did "make -s" you got some nice looking output of what you were building. Now with 2.4 it's all pretty and colored (nice!), but whenever I link a library I get what appears to be the contents of link.txt: L

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 2006-12-05 22:31+0100 Michel Hermier wrote: Do you have a case where something works in CMake-2.4.4, but does not work in CVS CMake that uses UsePkgConfig.cmake? If so, we will fix it. If this is new stuff, we can not change UsePkgConfig.cmake because it will break old code. There shoul

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Michel Hermier wrote: Bill Hoffman wrote: Michel Hermier wrote: I'm not sure of it, but in usage it seems every one expects it to be a list, else it's a nonsense to use the returned value everywhere I explained before. The error was triggered for me while checking a package with a parent

[CMake] Library linkage spewage under Makefiles (make -s)

In 2.2 when you specified SET(CMAKE_VERBOSE_MAKEFILE ON) and then did "make -s" you got some nice looking output of what you were building. Now with 2.4 it's all pretty and colored (nice!), but whenever I link a library I get what appears to be the contents of link.txt: Linking CXX shared lib

Re: [CMake] Deleting a variable

James Bigler wrote: > Message: 8 > Date: Tue, 05 Dec 2006 00:48:31 -0800 > From: "Brandon J. Van Every" <[EMAIL PROTECTED]> > Subject: Re: [CMake] Deleting a variable > To: cmake > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > James Bigler wrot

[CMake] more on an executable dependency on external library

OK, I've tried in the meantime various arrangements with ADD_CUSTOM_TARGET(), but seems hard to employ it to have CMake to put following simple dependency of an executable "foo" on system library "libbar.a" into generated Makefile: foo: /usr/local/lib/libbar.a There exists of course ADD_EXECUTABL

[CMake] Weird if nesting problem

I have this little block of code that is causing problems. Note that I bumped up the version number in order to get cmake 2.4 to go the else block. # You need at least version 2.4 for this to work. IF("${CMAKE_MAJOR_VERSION}.${CMAKE_M

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Bill Hoffman wrote: Michel Hermier wrote: I'm not sure of it, but in usage it seems every one expects it to be a list, else it's a nonsense to use the returned value everywhere I explained before. The error was triggered for me while checking a package with a parent package dependency (QCA

Fwd: [CMake] Deleting a variable

... -- Forwarded message -- From: Tristan Carel <[EMAIL PROTECTED]> Date: Dec 5, 2006 4:12 PM Subject: Re: [CMake] Deleting a variable To: James Bigler <[EMAIL PROTECTED]> On 12/5/06, James Bigler <[EMAIL PROTECTED]> wrote: > Message: 8 > Date: Tue, 05 Dec 2006 00:48:31 -0800

Re: [CMake] cmake command-line

Brian Little wrote: How do you run cmake on the command-line and have it run to completion? I have to run it more than once for it to find all the variables and then spit out the build files. Is there a switch to tell it to run until it is down? Right now to get around it, I have a batch fi

Re: [CMake] Deleting a variable

> Message: 8 > Date: Tue, 05 Dec 2006 00:48:31 -0800 > From: "Brandon J. Van Every" <[EMAIL PROTECTED]> > Subject: Re: [CMake] Deleting a variable > To: cmake > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > James Bigler wrote: > > > > > > I want

[CMake] cmake command-line

How do you run cmake on the command-line and have it run to completion? I have to run it more than once for it to find all the variables and then spit out the build files. Is there a switch to tell it to run until it is down? Right now to get around it, I have a batch file that runs cmake a

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Michel Hermier wrote: I'm not sure of it, but in usage it seems every one expects it to be a list, else it's a nonsense to use the returned value everywhere I explained before. The error was triggered for me while checking a package with a parent package dependency (QCA2 in trunk). So maybe

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Alan W. Irwin wrote: On 2006-12-05 13:32-0500 Bill Hoffman wrote: OTOH, if they decide to revert my patch from CVS and break backwards compatibility with previous releases, then I (and lots of other CMake users) will have to adjust our use of the PKGCONFIG module. I am not actually a fanatic

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Bill Hoffman wrote: Michel Hermier wrote: Hi, I'm experiencing a string against list issue PKGCONFIG new code. When using it we (in KDE) do things like: PKGCONFIG(lib libIncDir libLinkDir libLinkFlags LibCFlags) FIND_PATH(LIB_INCLUDE_DIR libfile.h ${linInkDir}) FIND_LIBRARY(LIB_LIBRARIES NAME

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 2006-12-05 13:32-0500 Bill Hoffman wrote: A patch was submitted because PlPlot did not work with the changes... Here is the comment: # To be compatible with obsolete module must return blank-delimited strings. # Also, lead with a blank (for TRUE/FALSE compatibility, 2.4.4 appears to

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

Michel Hermier wrote: Hi, I'm experiencing a string against list issue PKGCONFIG new code. When using it we (in KDE) do things like: PKGCONFIG(lib libIncDir libLinkDir libLinkFlags LibCFlags) FIND_PATH(LIB_INCLUDE_DIR libfile.h ${linInkDir}) FIND_LIBRARY(LIB_LIBRARIES NAMES libnames ... PATH $

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On Tuesday, 5 December 2006 18:31, Michel Hermier wrote: > Is there a macro to split a string to a list, so that > the compatibility macro at least could get fixed ? > Maybe a utility commands like STRING SPLIT/JOIN should be added for that > ? and maybe there are other more usage for it ? $ cmake

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

David Cole wrote: On 12/4/06, *Michel Hermier* <[EMAIL PROTECTED] > wrote: set (FOO "foo bar") dump (${FOO}) Here FOO is a string that contains a space... set (FOO foo bar) dump (${FOO}) Here FOO is a list with two elements. If it were printed a

Re: [CMake] SET_SOURCE_FILES_PROPERTIES and configurations

On 12/5/06, Luca Cappa <[EMAIL PROTECTED]> wrote: Hello On Tue, 05 Dec 2006 16:57:18 +0100, Tristan Carel <[EMAIL PROTECTED]> wrote: > On 12/5/06, Luca Cappa <[EMAIL PROTECTED]> wrote: >> >> The problem is that I cannot use different flags (perhaps >> _COMPILE_FLAGS) to generate two different p

Re: [CMake] SET_SOURCE_FILES_PROPERTIES and configurations

Hello On Tue, 05 Dec 2006 16:57:18 +0100, Tristan Carel <[EMAIL PROTECTED]> wrote: On 12/5/06, Luca Cappa <[EMAIL PROTECTED]> wrote: The problem is that I cannot use different flags (perhaps _COMPILE_FLAGS) to generate two different precompiled files, one for DEBUG and one for the RELEASE

Re: [CMake] SET_SOURCE_FILES_PROPERTIES and configurations

On 12/5/06, Luca Cappa <[EMAIL PROTECTED]> wrote: Hello, Hi, I am using cmake 2.4.5 with msvc 2005. I am setting this flag for all the source files i want to use precompilated headers with. SET(PREC_FLAG "/Yu") IF(MSVC) FOREACH (FILENAME ${LIB_SRC}) IF ("${FILENAME}" MATCHES "cpp")

[CMake] SET_SOURCE_FILES_PROPERTIES and configurations

Hello, I am using cmake 2.4.5 with msvc 2005. I am setting this flag for all the source files i want to use precompilated headers with. SET(PREC_FLAG "/Yu") IF(MSVC) FOREACH (FILENAME ${LIB_SRC}) IF ("${FILENAME}" MATCHES "cpp") SET_SOURCE_FILES_PROPERTIES(${FILENAME} COMPILE_FLAGS

Re: [CMake] Bug+Fix in FindwxWidgets.cmake

Hi Alex, How about something like: IF (WIN32) ... handle all win variants here ELSE (WIN32) ... and all non-win variants here ENDIF (WIN32) This won't work, the reason is: there are two ways to compile wxWidgets - either via configure (which produces wx-config) or via provided makefiles (o

Re: [CMake] PKGCONFIG backward compatibility on CVS trunk.

On 12/4/06, Michel Hermier <[EMAIL PROTECTED]> wrote: set (FOO "foo bar") dump (${FOO}) Here FOO is a string that contains a space... set (FOO foo bar) dump (${FOO}) Here FOO is a list with two elements. If it were printed as a string it would be "foo;bar" HTH, David __

[CMake] Advanced cmake in Nepomuk-KDE: changing vars at build time

Hi, I have the following problem: In the Nepomuk-KDE module (for reference see the KDE svn at trunk/playground/base/nepomuk-kde/kmetadata) I have a library and a tool that creates a bunch of source and header files from an RDF ontology. I don't have the full list of sources and headers beforeh

Re: [CMake] Deleting a variable

James Bigler wrote: I want the variable to disappear from the list when running ccmake. This didn't seem to do anything. How about SET(myvar CACHE INTERNAL "Don't show this") See the docs for SET. Cheers, Brandon Van Every ___ CMake mailing list

Re: [CMake] How to set the install directory for MacOSX/PackageMaker

Hello again, is anyone of you building packages with CPack for MacOSX? Do you think it is a problem that you cannot change the installation-root of a PackageMaker package? I've looked at CPack's source code which sets the installation root-dir of PackageMaker installers to "/usr" by default. It i