Re: [CMake] -fPIC and precompiled header

2007-01-08 Thread Axel Roebel
On Saturday 06 January 2007 18:42, you wrote: > Am Freitag, den 05.01.2007, 01:14 +0100 schrieb Axel Roebel: > > GET_TARGET_PROPERTY(_targetType ${_PCH_current_target} TYPE) > > SET(PHC_MASTER_INCLUDE_FILE ${_input}) > > > > CONFIGURE_FILE(${PROJECT_SOURCE_DIR}/cmModules/PCHCheckDependencies.

Re: [CMake] -fPIC and precompiled header

2007-01-06 Thread Axel Roebel
On Saturday 06 January 2007 16:05, Axel Roebel wrote: > On Saturday 06 January 2007 11:29, you wrote: > > I will merge your changes today. Many thanks! > > > > NOTE: > > Consider that I'm not a maintainer. I'm just a developer who was annoyed > > by the long compile times when using boost. Feel enc

Re: [CMake] -fPIC and precompiled header

2007-01-04 Thread Axel Roebel
Hi Maik, Thanks for the Christmas present ;-) I tried your code with gcc. The following issues/suggestions came to my mind: 1) It seems to me (and it worked for me) that you don't need to have CMAKE_CURRENT_BINARY_DIR in the include path if you change the target cflags determination into

Re: [CMake] -fPIC and precompiled header

2006-12-23 Thread Maik Beckmann
Am Mittwoch, den 20.12.2006, 17:53 +0100 schrieb frederic heem: > Hi, > Is there a nice way to find out if a target is using -fPIC ? > Indeed, this information is needed for generating compiled header. > At the moment, a kludge is to use the following code: > > #If the target is a shared libr

[CMake] -fPIC and precompiled header

2006-12-20 Thread frederic heem
Hi, Is there a nice way to find out if a target is using -fPIC ? Indeed, this information is needed for generating compiled header. At the moment, a kludge is to use the following code: #If the target is a shared library, add -fPIC to compile GET_TARGET_PROPERTY(_targetType ${_targetName}