Re: [cmake-developers] New CPack test failing on OS X and Windows 7

2010-12-13 Thread Bill Hoffman
On 12/12/2010 1:22 PM, Eric Noulard wrote: Thank you. No more clue with that list now, beside the fact that there is no ZIP. May be my cpack execution call is buggy. With the extra trace now in place I should see if this is the case. Eric, should we roll back the change? Lots of tests are

Re: [cmake-developers] New CPack test failing on OS X and Windows 7

2010-12-13 Thread Bill Hoffman
On 12/13/2010 9:52 AM, Bill Hoffman wrote: On 12/12/2010 1:22 PM, Eric Noulard wrote: Thank you. No more clue with that list now, beside the fact that there is no ZIP. May be my cpack execution call is buggy. With the extra trace now in place I should see if this is the case. Eric, should

Re: [cmake-developers] New CPack test failing on OS X and Windows 7

2010-12-13 Thread Bill Hoffman
I am working of fixing this, but have run into an issue... I did get the test to run, now it fails like this: 78: CPack: Create package 78: CPack: - package: C:/Users/hoffman/Work/My Builds/CMake-vside/Tests/CPackComponentsForAll/buildZIP-NoComponent/MyLib-1.0.2-win32-Development.zip

[CMake] cmake qt4 opengl

2010-12-13 Thread luxInteg
Greetings, This is towards banishing my cmake/qt4 idiocy. my CMakeLists.txt has these:- FIND_PACKAGE( Qt4 REQUIRED ) set( QT_USE_OPENGL TRUE ) set( QT_USE_QTSVG TRUE ) SET( QT_USE_QTXML TRUE ) SET( QT_USE_QT3SUPPORT TRUE ) SET( QT_USE_QTNETWORK TRUE ) SET(

Re: [CMake] cmake qt4 opengl

2010-12-13 Thread Christian Ehrlicher
Original-Nachricht Datum: Mon, 13 Dec 2010 12:48:23 + Von: luxInteg An: cmake@cmake.org Betreff: [CMake] cmake qt4 opengl Greetings, This is towards banishing my cmake/qt4 idiocy. my CMakeLists.txt has these:- FIND_PACKAGE( Qt4 REQUIRED ) set(

[CMake] Component support in FindPackageHandleStandardArgs

2010-12-13 Thread Johannes Zarl
Hello list, During a recent discussion about find_package modules and components, the question came up how to best use FindPackageHandleStandardArgs (FPHSA) with components. One solution that currently works is to call FPHSA several times with the qualified component name as package name: #

[CMake] cmake find_package() returns?

2010-12-13 Thread luxInteg
Is there a way to interrogate a FindXXX.cmake file tofind out what it returns? ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check

Re: [CMake] cmake find_package() returns?

2010-12-13 Thread Ryan Pavlik
Not sure what you mean - usually there is documentation at the top of the file listing the variables that it sets. Ryan On Mon, Dec 13, 2010 at 2:34 PM, luxInteg lux-in...@btconnect.com wrote: Is there a way to interrogate a FindXXX.cmake file tofind out what it returns?

[CMake] Building a mega library after building smaller component libraries?

2010-12-13 Thread Clifford Yapp
Can anyone tell me what the best way is (without a whole lot of rebuilding) to take several individual libraries and combine them into a single large library? In our autotools Makefile.am, we have the following: libbrlcad_la_SOURCES = libbrlcad_la_LDFLAGS = -version-info 19:1 libbrlcad_la_LIBADD

[CMake] Multiple Configurations + Optional Targets Depending on Found Libraries

2010-12-13 Thread Gregory Peele ARA/CFD
I trying to support multiple configurations in a single binary directory (in my case for MSVC 2010) and ran into a situation that I'm not sure how to tackle. I have a library target which links against OpenSceneGraph. If OpenSceneGraph is not found, that target and everything that depends on

Re: [CMake] Building a mega library after building smaller component libraries?

2010-12-13 Thread Clifford Yapp
Ah, I'm informed that what I was after was this: http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_libraries.3F and I won't be able to duplicate this result with CMake (at least, using that mechanism.) CY On Mon, Dec 13, 2010 at 6:13 PM, Clifford Yapp cliffy...@gmail.com

Re: [CMake] Building a mega library after building smaller component libraries?

2010-12-13 Thread Alan W. Irwin
On 2010-12-13 18:13-0500 Clifford Yapp wrote: Can anyone tell me what the best way is (without a whole lot of rebuilding) to take several individual libraries and combine them into a single large library? It appears someone has already pointed you to the (lack of) convenience library

[Cmake-commits] CMake branch, next, updated. v2.8.3-829-g37929fe

2010-12-13 Thread Marcus D . Hanwell
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 37929fe34bdd226e05c78aa00a0f90a8d360fe4b (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.3-832-ga3f94a4

2010-12-13 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via a3f94a43b4b3db9a294801a3f810fcb6a4b59307 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.3-834-g1306474

2010-12-13 Thread Marcus D . Hanwell
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 1306474331ecf15bc048a4d0aff53f4f6ac4632d (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.3-836-g09c5aa7

2010-12-13 Thread Eric Noulard
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 09c5aa789ce9aef2337c25ab4c56133b0bf9c802 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.3-848-g67a4de1

2010-12-13 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 67a4de115fac38e526aea034b0aded4cdb55269a (commit) via