[CMake] strip runtime paths from non-targets

[edA-qa mort-ora-y]

When copying executables/libraries under Windows CMake does some kind of
path stripping. I presume this is to clean up any absolute path references.

How can I get this to happen on DLLs which Cmake wasn't responsible for
building? That is, I need to copy a DLL built by another build process
(not under my control), and want the same patchup?

The core of my problem is trying to get the MySQL QT Plugin to work
correctly in an installed environment.

-- 
edA-qa mort-ora-y
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

BigTPoker - Poker fun and games

http://BigTPoker.com/

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Sign: Please digitally sign your emails.
Encrypt: I'm also happy to receive encrypted mail.



signature.asc
Description: OpenPGP digital signature
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Basic example of adding an MSVC project with ExternalProject_Add?

[Clifford Yapp]

I would like to use the ExternalProject_Add command to add a
pre-existing MSVC build system into a CMake generated MSVC project,
but I can't seem to find any examples of this and I haven't the least
idea what commands to supply for CONFIGURE/BUILD/etc. in order to
bring in the MSVC files.  Can anyone point me to a working example or
documentation spelling out how to do this?  Bonus points if it has
older project files that get updated to a newer Visual Studio.

Cheers,
CY
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Disallowing in-source builds

[aaron.meadows]

Here's what I ended up with:

 

function(AssureOutOfSourceBuilds)

  # make sure the user doesn't play dirty with symlinks

  get_filename_component(srcdir "${CMAKE_SOURCE_DIR}" REALPATH)

  get_filename_component(bindir "${CMAKE_BINARY_DIR}" REALPATH)

 

  # disallow in-source builds

  if(${srcdir} STREQUAL ${bindir})

message("##")

message("You are attempting to build in your Source Directory.")

message("You must run cmake from a build directory.")

message("##")

 

# attempt to remove cache and cache files... this actually fails to
work,

# but no hurt trying incase it starts working..

file(REMOVE_RECURSE "${CMAKE_SOURCE_DIR}/CMakeCache.txt"
"${CMAKE_SOURCE_DIR}/CMakeFiles")

 

message(FATAL_ERROR "In-source builds are forbidden!")

  endif()

 

  # check for polluted source tree

  if(EXISTS ${CMAKE_SOURCE_DIR}/CMakeCache.txt OR EXISTS
${CMAKE_SOURCE_DIR}/CMakeFiles)

 
message("###
#")

message( "Found results from an in-source build in your source
directory.")

 
message("###
#")

 

# attempt to remove cache and cache files...

file(REMOVE_RECURSE "${CMAKE_SOURCE_DIR}/CMakeCache.txt"
"${CMAKE_SOURCE_DIR}/CMakeFiles")

 

message(FATAL_ERROR "Source Directory Cleaned, please rerun CMake.")

  endif()

endfunction()

 

It's basically exactly what you mentioned.  I changed the order of the
checks to allow it to check for an in-source build before dealing with
the consequences of such.  I added more logging and actual cleanup.

 

Thanks for all the help. If you have any suggestions on improving this,
please let me know.  Incidentally, removing the CMakeCache.txt and
CMakeFiles directory does not work during the in-source build, but does
during the check to insure there isn't anything left over from an in
source build.  I went ahead and removed the files there and then
fatal_error'd out to allow the right CMakeCache.txt to be loaded in the
build tree when cmake is next run.

 

Aaron C. Meadows 

 

-Original Message-
From: Michael Wild [mailto:them...@gmail.com] 
Sent: Thursday, October 07, 2010 2:20 AM
To: Meadows, Aaron C.; Meadows, Aaron C.
Cc: cmake@cmake.org
Subject: Re: [CMake] Disallowing in-source builds

 

 

On 6. Oct, 2010, at 20:10 , 
 wrote:

 

> Hi all.

> 

> 

> 

> Is there a good way to disallow in-source builds?  Ideally, I'd like
to

> prevent it before any cruft is written into the source tree.  I

> experimented with writing a function into my CMakelists file and
calling

> it.  The function checked if CMAKE_BINARY_DIR was equal to

> CMAKE_SOURCE_DIR and messaged a FATAL_ERROR if that was the case.
This

> works ok, but still generates a CMakeFiles directory and a

> CMakeCache.txt file.

 

I don't think there's a way to prevent that from happening. The bad
thing about this is that if the user doesn't clean away the in-source
CMakeCache.txt file, subsequent out-of-source builds will fail. Perhaps
you can do something like this:

 

# check for polluted source tree

if(EXISTS ${CMAKE_SOURCE_DIR}/CMakeCache.txt OR

EXISTS ${CMAKE_SOURCE_DIR}/CMakeFiles)

  message(FATAL_ERROR

"CMakeCache.txt or CMakeFiles exists in source directory!")

endif()

# make sure the user doesn't play dirty with symlinks

get_filename_component(srcdir "${CMAKE_SOURCE_DIR}" REALPATH)

get_filename_component(bindir "${CMAKE_BINARY_DIR}" REALPATH)

# disallow in-source builds

if(${srcdir} STREQUAL ${bindir})

  message(FATAL_ERROR "In-source builds are forbidden!")

endif()

 

> 

> The second half of the question is of course, is there an easy way to

> clean out a source tree if an in-source build was accidentally kicked

> off?  (short of dividing the files by their timestamp and removing the

> newer ones, etc..)

 

No, simply because CMake cannot. Your build system might have something
like the following:

 

execute_process(COMMAND echo "BOOM" > ${CMAKE_BINARY_DIR}/boom.txt
VERBATIM)

 

CMake never knows that the file boom.txt is written, and therefor can't
clean it away. The only reasonable way I know of is using git
(http://git-scm.com):

 

git clean -df

 

will remove all the files and directories that are not part of the
repository. With tar-ball builds it's easier. Just wipe the source tree
and unpack again.

 

 

Michael



This email was sent to you by Thomson Reuters, the global news and information 
company.
Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Thomson Reuters.

___
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 the CMake FAQ at: 

Re: [CMake] CMake Visual Studio 64bit flag?

[aaron.meadows]

Thanks for pointing that out.. not that it effects the example in the
slightest... they could have been "Bozo" and "Crusty" and still prove it
works.  =D

Aaron C. Meadows 

-Original Message-
From: John Drescher [mailto:dresche...@gmail.com] 
Sent: Friday, October 08, 2010 11:52 AM
To: Meadows, Aaron C.
Cc: e...@sf-mail.de; cmake@cmake.org
Subject: Re: [CMake] CMake Visual Studio 64bit flag?

On Fri, Oct 8, 2010 at 12:50 PM,  
wrote:
> Seems to work correctly from my tests:
>
>
>
> CMakeLists.txt:
>
> cmake_minimum_required (VERSION 2.8)
>
>
>
> project(test CXX)
>
> message( STATUS "CMAKE_GENERATOR: ${CMAKE_GENERATOR}")
>
> message( STATUS "CMAKE_CL_64: ${CMAKE_CL_64}")
>
>
>
>
>
>
>
> c:\dev2\Builds\test\x64>cmake -G "Visual Studio 8 2005" ../.
>
> -- Check for working CXX compiler using: Visual Studio 8 2005
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 -- works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- CMAKE_GENERATOR: Visual Studio 8 2005
>
> -- CMAKE_CL_64: 0
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: C:/dev2/Builds/test/x64
>
>
>
>
>
> c:\dev2\Builds\test\x86>cmake -G "Visual Studio 8 2005 Win64" ../.
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 Win64
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 Win64 --
works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- CMAKE_GENERATOR: Visual Studio 8 2005 Win64
>
> -- CMAKE_CL_64: 1
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: C:/dev2/Builds/test/x86
>
>

I believe you got your folder names backwards.
John


This email was sent to you by Thomson Reuters, the global news and information 
company.
Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Thomson Reuters.


___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[John Drescher]

On Fri, Oct 8, 2010 at 12:50 PM,   wrote:
> Seems to work correctly from my tests:
>
>
>
> CMakeLists.txt:
>
> cmake_minimum_required (VERSION 2.8)
>
>
>
> project(test CXX)
>
> message( STATUS "CMAKE_GENERATOR: ${CMAKE_GENERATOR}")
>
> message( STATUS "CMAKE_CL_64: ${CMAKE_CL_64}")
>
>
>
>
>
>
>
> c:\dev2\Builds\test\x64>cmake -G "Visual Studio 8 2005" ../.
>
> -- Check for working CXX compiler using: Visual Studio 8 2005
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 -- works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- CMAKE_GENERATOR: Visual Studio 8 2005
>
> -- CMAKE_CL_64: 0
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: C:/dev2/Builds/test/x64
>
>
>
>
>
> c:\dev2\Builds\test\x86>cmake -G "Visual Studio 8 2005 Win64" ../.
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 Win64
>
> -- Check for working CXX compiler using: Visual Studio 8 2005 Win64 -- works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- CMAKE_GENERATOR: Visual Studio 8 2005 Win64
>
> -- CMAKE_CL_64: 1
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: C:/dev2/Builds/test/x86
>
>

I believe you got your folder names backwards.
John
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[aaron.meadows]

Seems to work correctly from my tests:

 

CMakeLists.txt:

cmake_minimum_required (VERSION 2.8)

 

project(test CXX)

message( STATUS "CMAKE_GENERATOR: ${CMAKE_GENERATOR}")

message( STATUS "CMAKE_CL_64: ${CMAKE_CL_64}")

 

 

 

c:\dev2\Builds\test\x64>cmake -G "Visual Studio 8 2005" ../.

-- Check for working CXX compiler using: Visual Studio 8 2005

-- Check for working CXX compiler using: Visual Studio 8 2005 -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- CMAKE_GENERATOR: Visual Studio 8 2005

-- CMAKE_CL_64: 0

-- Configuring done

-- Generating done

-- Build files have been written to: C:/dev2/Builds/test/x64

 

 

c:\dev2\Builds\test\x86>cmake -G "Visual Studio 8 2005 Win64" ../.

-- Check for working CXX compiler using: Visual Studio 8 2005 Win64

-- Check for working CXX compiler using: Visual Studio 8 2005 Win64 --
works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- CMAKE_GENERATOR: Visual Studio 8 2005 Win64

-- CMAKE_CL_64: 1

-- Configuring done

-- Generating done

-- Build files have been written to: C:/dev2/Builds/test/x86

 

 

 

 

Aaron C. Meadows 

 

-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Rolf Eike Beer
Sent: Friday, October 08, 2010 11:33 AM
To: cmake@cmake.org
Subject: Re: [CMake] CMake Visual Studio 64bit flag?

 

Am Friday 08 October 2010 schrieb aaron.mead...@thomsonreuters.com:

> Is this not sufficient: (from "Variables That Describe the System")

> 

> CMAKE_CL_64: Using the 64 bit compiler from Microsoft

> 

> Set to true when using the 64 bit cl compiler from Microsoft.

> 

> This is what I'm intending on using, so if this won't work, I'll need
to

> know...

 

IIRC that doesn't work if you use the Studio generator (i.e. not
Makefiles). So 

this needs to be something like "if (CMAKE_CL_64 or CMAKE_GENERATOR
MATCHES 

Win64)"

 

Eike



This email was sent to you by Thomson Reuters, the global news and information 
company.
Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Thomson Reuters.

___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How would I use parallel make on ExternalProjects?

[Bill Hoffman]

On 10/8/2010 11:57 AM, kent williams wrote:

I think what I'm doing isn't clear to you.

I have a CMakeLists.txt that is essentially 'sourceless' -- it defines
a bunch of CMake variables, and then builds a bunch of prerequisites
and applications added with ExternalProject_add. It doesn't have any
add_subdirectory,add_executable, add_library etc of its own.

So at build time, the process tree is

make # the make of the top level
  make # build external project 1
  .
  .
  make # build external project n

If I use make -j4, for example, it would build 4 external projects in
parallel with make -j1.  If any of those projects is on the critical
path, and takes significantly longer to build than any other projects,
the build process bottlenecks doing the sequential build of that one
project.

My method -- changing the build command for the external projects to
use -j4 for example, will instead do a sequential series of parallel
sub-makes, instead of a parallel series of sequential submakes.

I've tried it both ways and this is how it works.



We have fixed things recently to address this.  The way it should be 
working:


make  # top level
 make # build external project 1
 .
 .
 make # build external project n

make -j4 at the top:

The make jobserver should take care of the rest and make sure that 4 
different things are always building at the same time.   This could be 
.o files from more than one external project if that is how it works out.


This is possible because $(MAKE) is used so when the external projects 
are run gmake will pass the jobserver information down to the next 
sub-make.  The jobserver will keep track of making sure no more than 4 
things are running at the same time.


-Bill
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[Rolf Eike Beer]

Am Friday 08 October 2010 schrieb aaron.mead...@thomsonreuters.com:
> Is this not sufficient: (from "Variables That Describe the System")
> 
> CMAKE_CL_64: Using the 64 bit compiler from Microsoft
> 
> Set to true when using the 64 bit cl compiler from Microsoft.
> 
> This is what I'm intending on using, so if this won't work, I'll need to
> know...

IIRC that doesn't work if you use the Studio generator (i.e. not Makefiles). So 
this needs to be something like "if (CMAKE_CL_64 or CMAKE_GENERATOR MATCHES 
Win64)"

Eike


signature.asc
Description: This is a digitally signed message part.
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[aaron.meadows]

Is this not sufficient: (from "Variables That Describe the System")

 

CMAKE_CL_64: Using the 64 bit compiler from Microsoft

 

Set to true when using the 64 bit cl compiler from Microsoft.

 

This is what I'm intending on using, so if this won't work, I'll need to
know...

 

Aaron C. Meadows 



From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Peter Clemenko
Sent: Friday, October 08, 2010 10:35 AM
To: cmake@cmake.org
Subject: [CMake] CMake Visual Studio 64bit flag?

 

Hello, I'm trying to work on creating a precompiled binary package for a
project I'm working on, and I was wondering if there was any way to
configure CMake to select a folder based on whether or not the 64bit
version of Visual studio was selected for the library path. The library
path would be something similar to:

 

lib

|-vs8

|--x86

|--x64

|-vs9

|--x86

|--x64

|-vs10

|--x86

|--x64

 

Is there any flag I can use in my Find.cmake files in order select the
library path based on if 64 bit or 32 bit is selected?

 

Thanks,

Peter



This email was sent to you by Thomson Reuters, the global news and information 
company.
Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Thomson Reuters.

___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[Mateusz Loskot]

Yes, you are right.
My mistake.

Thanks!
Mat


On 08/10/10 16:51, David Cole wrote:

Either you've got that reversed, or 4 should be 8... right?

lib64 should be for an 8-byte void* ...


On Fri, Oct 8, 2010 at 11:48 AM, Mateusz Loskot mailto:mate...@loskot.net>> wrote:

On 08/10/10 16:42, Michael Jackson wrote:

maybe SIZE_OF_VOID_POINTER of whatever that variable is in CMake?


In SOCI library, I use something like this:

if(UNIX AND CMAKE_SIZEOF_VOID_P EQUAL 4)
  set(SOCI_LIBDIR "lib64")
else()
  set(SOCI_LIBDIR "lib")
endif()

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org

___
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 the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake





--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How would I use parallel make on ExternalProjects?

[kent williams]

I think what I'm doing isn't clear to you.

I have a CMakeLists.txt that is essentially 'sourceless' -- it defines
a bunch of CMake variables, and then builds a bunch of prerequisites
and applications added with ExternalProject_add. It doesn't have any
add_subdirectory,add_executable, add_library etc of its own.

So at build time, the process tree is

make # the make of the top level
 make # build external project 1
 .
 .
 make # build external project n

If I use make -j4, for example, it would build 4 external projects in
parallel with make -j1.  If any of those projects is on the critical
path, and takes significantly longer to build than any other projects,
the build process bottlenecks doing the sequential build of that one
project.

My method -- changing the build command for the external projects to
use -j4 for example, will instead do a sequential series of parallel
sub-makes, instead of a parallel series of sequential submakes.

I've tried it both ways and this is how it works.

For the gentleman who suggested distcc -- thanks but no thanks for
these reasons: 1) it's something else to add to a very long list of
prerequisites for our software and 2) it requires a mostly homogenous
network of computers to farm compiles out to.  We have, by design, a
heterogenous network of OS X and different Linux versions, so that
we're testing on as many platforms as possible.


On Thu, Oct 7, 2010 at 11:29 AM, Bill Hoffman  wrote:
> ITK will not do a sequential build.  The -j N gets passed down to all the
> sub projects as well. It will run N build rules at the same time from VTK,
> ITK and everything else.    Just like it was all one big project...
>
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[David Cole]

Either you've got that reversed, or 4 should be 8... right?

lib64 should be for an 8-byte void* ...


On Fri, Oct 8, 2010 at 11:48 AM, Mateusz Loskot  wrote:

> On 08/10/10 16:42, Michael Jackson wrote:
>
>> maybe SIZE_OF_VOID_POINTER of whatever that variable is in CMake?
>>
>
> In SOCI library, I use something like this:
>
> if(UNIX AND CMAKE_SIZEOF_VOID_P EQUAL 4)
>  set(SOCI_LIBDIR "lib64")
> else()
>  set(SOCI_LIBDIR "lib")
> endif()
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> Charter Member of OSGeo, http://osgeo.org
> Member of ACCU, http://accu.org
>
> ___
> 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 the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CPack with MSI support?

[Bill Hoffman]

On 10/8/2010 3:32 AM, NoRulez wrote:

Hello,

does CPack have msi support also, or if no, is it planned?



Nothing planned, but if someone wanted to contribute something that 
would be welcomed.


-Bill
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[Mateusz Loskot]

On 08/10/10 16:42, Michael Jackson wrote:

maybe SIZE_OF_VOID_POINTER of whatever that variable is in CMake?


In SOCI library, I use something like this:

if(UNIX AND CMAKE_SIZEOF_VOID_P EQUAL 4)
  set(SOCI_LIBDIR "lib64")
else()
  set(SOCI_LIBDIR "lib")
endif()

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake Visual Studio 64bit flag?

[Michael Jackson]

maybe SIZE_OF_VOID_POINTER of whatever that variable is in CMake?
___
Mike Jackson  www.bluequartz.net
Principal Software Engineer   mike.jack...@bluequartz.net
BlueQuartz Software   Dayton, Ohio



On Oct 8, 2010, at 11:35 AM, Peter Clemenko wrote:

Hello, I'm trying to work on creating a precompiled binary package  
for a project I'm working on, and I was wondering if there was any  
way to configure CMake to select a folder based on whether or not  
the 64bit version of Visual studio was selected for the library  
path. The library path would be something similar to:


lib
|-vs8
|--x86
|--x64
|-vs9
|--x86
|--x64
|-vs10
|--x86
|--x64

Is there any flag I can use in my Find.cmake files in order select  
the library path based on if 64 bit or 32 bit is selected?


Thanks,
Peter
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] CMake Visual Studio 64bit flag?

[Peter Clemenko]

Hello, I'm trying to work on creating a precompiled binary package for a
project I'm working on, and I was wondering if there was any way to
configure CMake to select a folder based on whether or not the 64bit version
of Visual studio was selected for the library path. The library path would
be something similar to:

lib
|-vs8
|--x86
|--x64
|-vs9
|--x86
|--x64
|-vs10
|--x86
|--x64

Is there any flag I can use in my Find.cmake files in order select the
library path based on if 64 bit or 32 bit is selected?

Thanks,
Peter
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to depend on an ExternalProject

[Michael Hertling]

On 10/08/2010 12:50 PM, Michael Wild wrote:
> 
> On 8. Oct, 2010, at 12:13 , Rolf Eike Beer wrote:
> 
>>>
>>> On 8. Oct, 2010, at 10:50 , Rolf Eike Beer wrote:
>>>
 Hi,

 I have a problem with ExternalProject and how to depend on that. I'm not
 absolutely sure I got the CMakeLists.txt right, so I first ask here
 before
 filing a bug report.

 The idea is like this: we have an project that generates a couple of
 files. In a special configuration of another project we need those files
 as input for a special build step. Those step will take those files,
 mangle them and will generate a source file at the end. This is then
 added
 as usual to a library (in my example below to a executable, but that
 doesn't matter). When I run the example below I get:

 [ 80%] Built target Subdir_Build
 make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'.
 Stop.
>>
>> [...]
>>
>>> Subdir_Build is a top-level target, and the custom-command can only depend
>>> on files. You need to add a custom target that depends on main.c and then
>>> add a dependency of that custom target on Subdir_Build.
>>
>> The documentation of add_custom_command has this sentence:
>>
>> If DEPENDS specifies any target (created by an ADD_* command) a
>> target-level dependency is created to make sure the target is built
>> before any target using this custom command.
>>
>> So if I can't depend on a target this is extremely confusing. Even worse:
>> the dependency itself _works_, i.e. Subdir_Build always get's properly
>> build before the depending target. But even then depending target fails.
>>
>> Eike
> 
> Does it work with the custom target? Because that's how it works for me. But 
> I agree that either the documentation is wrong or there is a bug...

AFAIK, the external project is incorporated as a custom target, and
custom targets are not suited as prerequisites of a custom command's
output whereas ordinary targets, i.e. executables and libraries, are:

CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(CUSTOMDEPENDS C)
FILE(WRITE ${CMAKE_BINARY_DIR}/f.c "void f(void){}\n")
ADD_LIBRARY(f SHARED f.c)
ADD_CUSTOM_TARGET(t ${CMAKE_COMMAND} -E echo "Building custom target t")
ADD_CUSTOM_COMMAND(
OUTPUT timestamp1
COMMAND ${CMAKE_COMMAND} -E touch timestamp1
DEPENDS f
)
ADD_CUSTOM_COMMAND(
OUTPUT timestamp2
COMMAND ${CMAKE_COMMAND} -E touch timestamp2
DEPENDS t
)
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c "int main(void){return 0;}\n")
ADD_EXECUTABLE(main1 EXCLUDE_FROM_ALL main.c timestamp1)
ADD_EXECUTABLE(main2 EXCLUDE_FROM_ALL main.c timestamp2)

On *nix, I can see main1 getting built, and it gets rebuilt along f and
timestamp1 if f.c is touched. In contrast, building main2 fails due to
the missing rule for the custom target t although t can be built on the
direct way. Of course, you can succeed with an additional custom target
in junction with explicitly declared dependencies, but IMO, too, this
shortcoming of custom targets w.r.t. custom commands should be
mentioned in the documentation - or considered as a bug.

Recently, IIRC, I've seen a similar configuration work with a custom
target declared in another CMakeLists.txt as the one containing the
depending custom command, but currently, I can't reproduce it. :(
Perhaps, the CMake developers can give us a hint in this matter.

Regards,

Michael
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Is there a tool pretty much like cmake for Java?

[Andreas Schneider]

On Thursday 07 October 2010 21:32:51 Bill Hoffman wrote:
> The other issue is VS builds.  At one point, I had some magic, cmake
> language to custom command converter thing going for this, but I am
> thinking it might be broken.   If we did a pure custom-command version,
> it would work in the IDE's (Xcode and VS) with no problem.  Right now,
> your stuff will likely only work with makefiles.
> 
> -Bill

I hit several problems using a custom command version.

a) 

add_jar(osutil_java ${osutil_java_SRCS})
set_target_properties(osutil_java PROPERTIES OUTPUT_NAME osutil)

doesn't work for me.

get_target_property(FOO osutil_java OUTPUT_NAME)

is empty.

b)

I can't use osutil_java in another CMakeLists.txt as a dependency.

Here is my function add_jar()

http://git.cynapses.org/users/asn/pki.git/tree/cmake/Modules/UseJava.cmake?h=cmake


-- andreas

___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to depend on an ExternalProject

[Michael Wild]

On 8. Oct, 2010, at 12:13 , Rolf Eike Beer wrote:

>> 
>> On 8. Oct, 2010, at 10:50 , Rolf Eike Beer wrote:
>> 
>>> Hi,
>>> 
>>> I have a problem with ExternalProject and how to depend on that. I'm not
>>> absolutely sure I got the CMakeLists.txt right, so I first ask here
>>> before
>>> filing a bug report.
>>> 
>>> The idea is like this: we have an project that generates a couple of
>>> files. In a special configuration of another project we need those files
>>> as input for a special build step. Those step will take those files,
>>> mangle them and will generate a source file at the end. This is then
>>> added
>>> as usual to a library (in my example below to a executable, but that
>>> doesn't matter). When I run the example below I get:
>>> 
>>> [ 80%] Built target Subdir_Build
>>> make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'.
>>> Stop.
> 
> [...]
> 
>> Subdir_Build is a top-level target, and the custom-command can only depend
>> on files. You need to add a custom target that depends on main.c and then
>> add a dependency of that custom target on Subdir_Build.
> 
> The documentation of add_custom_command has this sentence:
> 
> If DEPENDS specifies any target (created by an ADD_* command) a
> target-level dependency is created to make sure the target is built
> before any target using this custom command.
> 
> So if I can't depend on a target this is extremely confusing. Even worse:
> the dependency itself _works_, i.e. Subdir_Build always get's properly
> build before the depending target. But even then depending target fails.
> 
> Eike

Does it work with the custom target? Because that's how it works for me. But I 
agree that either the documentation is wrong or there is a bug...

Michael

--
There is always a well-known solution to every human problem -- neat, 
plausible, and wrong.
H. L. Mencken



PGP.sig
Description: This is a digitally signed message part
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to depend on an ExternalProject

[Rolf Eike Beer]

>
> On 8. Oct, 2010, at 10:50 , Rolf Eike Beer wrote:
>
>> Hi,
>>
>> I have a problem with ExternalProject and how to depend on that. I'm not
>> absolutely sure I got the CMakeLists.txt right, so I first ask here
>> before
>> filing a bug report.
>>
>> The idea is like this: we have an project that generates a couple of
>> files. In a special configuration of another project we need those files
>> as input for a special build step. Those step will take those files,
>> mangle them and will generate a source file at the end. This is then
>> added
>> as usual to a library (in my example below to a executable, but that
>> doesn't matter). When I run the example below I get:
>>
>> [ 80%] Built target Subdir_Build
>> make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'.
>> Stop.

[...]

> Subdir_Build is a top-level target, and the custom-command can only depend
> on files. You need to add a custom target that depends on main.c and then
> add a dependency of that custom target on Subdir_Build.

The documentation of add_custom_command has this sentence:

 If DEPENDS specifies any target (created by an ADD_* command) a
target-level dependency is created to make sure the target is built
before any target using this custom command.

So if I can't depend on a target this is extremely confusing. Even worse:
the dependency itself _works_, i.e. Subdir_Build always get's properly
build before the depending target. But even then depending target fails.

Eike
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to depend on an ExternalProject

[Michael Wild]

On 8. Oct, 2010, at 10:50 , Rolf Eike Beer wrote:

> Hi,
> 
> I have a problem with ExternalProject and how to depend on that. I'm not
> absolutely sure I got the CMakeLists.txt right, so I first ask here before
> filing a bug report.
> 
> The idea is like this: we have an project that generates a couple of
> files. In a special configuration of another project we need those files
> as input for a special build step. Those step will take those files,
> mangle them and will generate a source file at the end. This is then added
> as usual to a library (in my example below to a executable, but that
> doesn't matter). When I run the example below I get:
> 
> [ 80%] Built target Subdir_Build
> make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'. 
> Stop.
> 
> I've tested this with 2.8.2 and 2.8.3-rc2.
> 
> Put this into CMakeLists.txt
> === snip ===
> PROJECT(MaindirThing C)
> 
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8.2)
> 
> INCLUDE(ExternalProject)
> 
> ExternalProject_Add(Subdir_Build
>   PREFIX "${CMAKE_CURRENT_BINARY_DIR}/build_subdir"
>   SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/subdir"
>   CMAKE_ARGS
> "-DCMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install"
>   INSTALL_DIR "${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install"
> )
> 
> ADD_CUSTOM_COMMAND(
>   OUTPUT "main.c"
>   COMMAND ${CMAKE_COMMAND}
>   ARGS -E copy ${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install/foo
> ${CMAKE_CURRENT_BINARY_DIR}/main.c
>   DEPENDS Subdir_Build
> )
> 
> ADD_EXECUTABLE(simple_exe main.c)
> === snap ===
> 
> And this goes to subdir/CMakeLists.txt
> === snip ===
> PROJECT(SubdirThing NONE)
> 
> CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
> 
> FILE(WRITE ${CMAKE_CURRENT_BINARY_DIR}/foo_file "int main(void)\n{\n 
> return 0;\n}\n")
> 
> INSTALL(FILES ${CMAKE_CURRENT_BINARY_DIR}/foo_file DESTINATION .)
> === snap ===
> 
> Side note: I would have expected that CMAKE_INSTALL_PREFIX is set to
> INSTALL_DIR if the external project is a cmake one.
> 
> Eike

Hi Eike

Subdir_Build is a top-level target, and the custom-command can only depend on 
files. You need to add a custom target that depends on main.c and then add a 
dependency of that custom target on Subdir_Build.

HTH

Michael

--
There is always a well-known solution to every human problem -- neat, 
plausible, and wrong.
H. L. Mencken

___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How would I use parallel make on ExternalProjects?

[fatman]

> There is one problem with that, which is what I'm trying to address:
> load balancing.  If your project builds ITK, VTK, and sundry other
> prerequisite libraries, it will spawn 4 sequential builds.  In
> practice this means everything except ITK (which we build with
> wrapping on) finishes, and then ITK chugs along doing its sequential
> build.
> 
> If I do what I'm talking about, I'd sequentially conduct parallel
> builds of ITK VTK etc.  In which case the big hairy libraries, like
> ITK with wrapping, get built in parallel.

Have you considered distcc? It's essentially a compiler load balancer
and fairly mature by now. I don't think it works on Windows though, so
if you need that it might not be what you want.
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] How to depend on an ExternalProject

[Rolf Eike Beer]

Hi,

I have a problem with ExternalProject and how to depend on that. I'm not
absolutely sure I got the CMakeLists.txt right, so I first ask here before
filing a bug report.

The idea is like this: we have an project that generates a couple of
files. In a special configuration of another project we need those files
as input for a special build step. Those step will take those files,
mangle them and will generate a source file at the end. This is then added
as usual to a library (in my example below to a executable, but that
doesn't matter). When I run the example below I get:

[ 80%] Built target Subdir_Build
make[2]: *** No rule to make target `Subdir_Build', needed by `main.c'. 
Stop.

I've tested this with 2.8.2 and 2.8.3-rc2.

Put this into CMakeLists.txt
=== snip ===
PROJECT(MaindirThing C)

CMAKE_MINIMUM_REQUIRED(VERSION 2.8.2)

INCLUDE(ExternalProject)

ExternalProject_Add(Subdir_Build
PREFIX "${CMAKE_CURRENT_BINARY_DIR}/build_subdir"
SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/subdir"
CMAKE_ARGS
"-DCMAKE_INSTALL_PREFIX=${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install"
INSTALL_DIR "${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install"
)

ADD_CUSTOM_COMMAND(
OUTPUT "main.c"
COMMAND ${CMAKE_COMMAND}
ARGS -E copy ${CMAKE_CURRENT_BINARY_DIR}/build_subdir/install/foo
${CMAKE_CURRENT_BINARY_DIR}/main.c
DEPENDS Subdir_Build
)

ADD_EXECUTABLE(simple_exe main.c)
=== snap ===

And this goes to subdir/CMakeLists.txt
=== snip ===
PROJECT(SubdirThing NONE)

CMAKE_MINIMUM_REQUIRED(VERSION 2.6)

FILE(WRITE ${CMAKE_CURRENT_BINARY_DIR}/foo_file "int main(void)\n{\n 
return 0;\n}\n")

INSTALL(FILES ${CMAKE_CURRENT_BINARY_DIR}/foo_file DESTINATION .)
=== snap ===

Side note: I would have expected that CMAKE_INSTALL_PREFIX is set to
INSTALL_DIR if the external project is a cmake one.

Eike
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] CPack with MSI support?

[NoRulez]

Hello,

does CPack have msi support also, or if no, is it planned?

Thanks in advance
Best Regards
NoRulez
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] How to determine the number of processors available from CMake code

[Michael Wild]

Would be nice to have this as a module: http://cmake.org/Bug/view.php?id=11302


On 8. Oct, 2010, at 24:41 , David Cole wrote:

> Thanks!
> 
> On Thu, Oct 7, 2010 at 6:08 PM, Mark Moll  wrote:
> 
>> On OS X, this command might be easier / faster:
>> 
>> sysctl -n hw.ncpu
>> 
>> On Oct 7, 2010, at 3:50 PM, David Cole wrote:
>> 
>>> I just posted a short blog article demonstrating how to figure out the
>> number of processors available for a "make -j" or a scripted ctest_build
>> call (with the "Unix Makefiles" generator) on Linux, Mac and Windows. Please
>> let me know if you have any ideas for how it might be improved or extended.
>>> 
>>> http://www.kitware.com/blog/home/post/63
>>> 
>>> 
>>> Cheers,
>>> David
>>> 
>>> 
>>> Blog text copied here, too, for search-ability on the mailing list
>> archives:
>>> 
>> ==
>>> At the end of this script snippet, the CMake variable PROCESSOR_COUNT has
>> a value appropriate for passing to make's -j for parallel builds.
>>> 
>>> When used in a ctest -S script, you can call...
>>> 
>>> if(PROCESSOR_COUNT)
>>>  set(CTEST_BUILD_FLAGS "-j${PROCESSOR_COUNT}")
>>> endif()
>>> 
>>> ...to enable parallel builds with "Unix Makefiles" and the ctest_build
>> command.
>>> 
>>> 
>>> Here's the snippet:
>>> if(NOT DEFINED PROCESSOR_COUNT)
>>>  # Unknown:
>>>  set(PROCESSOR_COUNT 0)
>>> 
>>>  # Linux:
>>>  set(cpuinfo_file "/proc/cpuinfo")
>>>  if(EXISTS "${cpuinfo_file}")
>>>file(STRINGS "${cpuinfo_file}" procs REGEX "^processor.: [0-9]+$")
>>>list(LENGTH procs PROCESSOR_COUNT)
>>>  endif()
>>> 
>>>  # Mac:
>>>  if(APPLE)
>>>find_program(cmd_sys_pro "system_profiler")
>>>if(cmd_sys_pro)
>>>  execute_process(COMMAND ${cmd_sys_pro} OUTPUT_VARIABLE info)
>>>  string(REGEX REPLACE "^.*Total Number Of Cores: ([0-9]+).*$" "\\1"
>>>PROCESSOR_COUNT "${info}")
>>>endif()
>>>  endif()
>>> 
>>>  # Windows:
>>>  if(WIN32)
>>>set(PROCESSOR_COUNT "$ENV{NUMBER_OF_PROCESSORS}")
>>>  endif()
>>> endif()
>>> 
>>> ___
>>> 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 the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.cmake.org/mailman/listinfo/cmake
>> 
>> --
>> Mark Moll
>> 
>> 
>> 
>> 
> ___
> 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 the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake

--
There is always a well-known solution to every human problem -- neat, 
plausible, and wrong.
H. L. Mencken



PGP.sig
Description: This is a digitally signed message part
___
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 the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake