Re: [CMake] [Insight-developers] [ITK Community] Building Matlab Mex extensions that link to ITK?

[Tom Vercauteren]

Hi Kent,

A long time ago, I also submitted a patch to cmake to support mex file creation:
http://public.kitware.com/Bug/view.php?id=8207

It might have been pushed one step further in gerardus:
https://code.google.com/p/gerardus/source/browse/trunk/matlab/MatlabMakeMacros.cmake

It's closely related to what Matt proposed:
http://public.kitware.com/Bug/view.php?id=9240

At some point, I stopped using it because of issues with fPIC, static
libraries and linux 64 bit architecture (I was dealing not only with
ITK but a whole lot of different librairies as well)... It might need
some work to fix it but it might well still work if you are not using
libraries that Matlab also uses (e.g. QT).

Tom

On Tue, Nov 19, 2013 at 7:06 PM, Matt McCormick
 wrote:
> Hi Kent,
>
> I wrote this [1][2] a long time ago, but I have not used it recently.
> There is an ITK example.
>
> Hope this helps,
> Matt
>
> [1] http://www.cmake.org/Wiki/CMake/MatlabMex
> [2] http://github.com/thewtex/matlab-itk-import/tree/master
>
> On Tue, Nov 19, 2013 at 12:59 PM, Williams, Norman K
>  wrote:
>> Has anyone else come up with an elegant solution for this?
>>
>> If I want to call ITK from a Matlab MEX extension written in C++, I run
>> into problems with telling it the libraries with which to link.
>>
>> The ITK_LIBRARIES variable is a list of imported library targets which
>> CMake converts to actual library paths when it links a library or
>> executable.
>>
>> But to compile a MEX file, we're using a custom command along the lines of
>>
>>add_custom_command(OUTPUT ${MEX_PREFIX}.${MATLAB_MEX_EXT}
>>  COMMAND ${MATLAB_MEX_PATH} -cxx
>> ${CMAKE_CXX_FLAGS_Release} ${MEX_SRC_PATH}
>> ${ITK_INCLUDES} ${ITK_LIBRARIES}
>>  -I${Teem_INCLUDE_DIR} -L${Teem_LIBRARY_DIR}  -lteem
>> ${ZLIB_LIBRARY}
>>  DEPENDS ${MEX_SRC_PATH}
>>  IMPLICIT_DEPENDS C ${MEX_SRC_PATH}
>>  COMMENT "BUILDING MEX_FILE: ${MEX_SRC_PATH}" )
>>
>> But that doesn't work because CMake gives the target names in
>> ITK_LIBRARIES instead of the actual libraries.
>>
>> I tried this:
>>
>> find_package(ITK NO_MODULE REQUIRED)
>> include(${ITK_USE_FILE})
>>
>> set(ITK_LOCAL_LIBS)
>> foreach(lib ${ITK_LIBRARIES})
>>   get_target_property(_lib ${lib} IMPORTED_LOCATION)
>>
>>   list(APPEND ITK_LOCAL_LIBS ${_lib})endforeach()
>>
>> But all the IMPORTED_LOCATION for ITK libraries is _lib-NOTFOUND
>>
>>
>>
>> --
>> Kent Williams norman-k-willi...@uiowa.edu
>>
>>
>>
>>
>>
>>
>> 
>> Notice: This UI Health Care e-mail (including attachments) is covered by the 
>> Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential 
>> and may be legally privileged.  If you are not the intended recipient, you 
>> are hereby notified that any retention, dissemination, distribution, or 
>> copying of this communication is strictly prohibited.  Please reply to the 
>> sender that you have received the message in error, then delete it.  Thank 
>> you.
>> 
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.php
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>> ___
>> Community mailing list
>> commun...@itk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/community
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] Issue with copy_directoru command

[David Bariod]

Hello,

While using the ExternalProject module, I've found an issue with the
copy_directory command.
It seems the copy won't happen completely if somewhere in the tree there is
a symbolic link whose target does not exist.
Is it a known problem or should I open a bug report somewhere ?

Best regards,
David Bariod
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] CPACK_COMPONENT__DEPENDS doesn't work

[jeff]

Hello CMake group,

I'm trying to do a component-based install that will produce multiple packages, where one package depends on another. I am using cmake version 2.8.12.1. Have multiple packages working well but the dependencies have not been easy.

The variable CPACK_COMPONENT__DEPENDS, given by the command `cpack --help-variable-list`, as far as I can tell, does nothing. Surprisingly, what ended up doing the trick on an RPM-based system is:

SET(CPACK_RPM_gui_PACKAGE_REQUIRES "my-lib >= 0.1.1")

Why does this work? This is inconsistent with the documentation. 

The bigger problem, I'm trying to solve at the moment, is how to make component dependencies work on Debian. I have tried every combination of cpack variable + component name and nothing stops an install with a message like, "Unable to install gui because it depends on my-lib" (because my-lib doesn't exist so it should halt the installer).

Does component-based install even work for Debian (actually, I'm on ubuntu but whatever)? I saw about two references to it on the entire Internet so a good resource is hard to find, currently. It would be idea if I can use CPACK_COMPONENT__DEPENDS for both deb and rpm but as I said, it doesn't work.


Thank you for any help/guidance. 

Jeff


 
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] Compiling with openmpi installed from macports

[Martin Pierre Hautefeuille]

Dear all,

I am trying to compile a piece of code, developed on Linux, on a Darwin system. 
I am using macports as a package manager with which I have installed openmpi. 
It seems that for some reasons, the mpi c compiler is not called mpicc when 
installed with macports but called openmpicc instead. Hence, the cmake command 
find_package(MPI) is unable to find the required mli library.

I pocked around on the internet and the best fix I have come up so far is as 
follows:
...
if(APPLE)
  set(MPI_C_COMPILER “openmpicc”)
endif(APPLE)
find_package(MPI)
…

Is there a better way to go about that?

Thanks a lot for your help!
Cheers,
Martin

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

Re: [CMake] building a library named 'general'

[Matthew Woehlke]

On 2013-11-19 19:07, Michael DiCuccio wrote:

Suppose you have a library named general:

-
add_library(general foo bar)
-

and then try to link it into an application:
-
add_executable(myapp baz)
target_link_libraries(myapp general)
-

cmake complains about the fact that 'general' is a reserved keyword, and I
have found no way to force or finagle linkage against a library named
'libgeneral'.


Name the target something else (e.g. 'libgeneral') and modify its 
OUTPUT_NAME? (See set_target_properties and the OUTPUT_NAME property.)


If all you need is to produce a 'libgeneral.so', that may suffice. If 
you also need the target name to be 'general'...


--
Matthew

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] building a library named 'general'

[Michael DiCuccio]

Hi!

I've come across an odd conundrum and need a little help resolving it.  I'm
porting a large toolkit to use CMake instead of an autoconf /
configure-based makefile system.  One problem we tripped across is a
library named 'libgeneral.so', built as part of the toolkit itself.  The
trouble is that the syltax of a CMakeLists.txt file does not permit linking
a library named general.

Suppose you have a library named general:

-
add_library(general foo bar)
-

...and then try to link it into an application:
-
add_executable(myapp baz)
target_link_libraries(myapp general)
-

cmake complains about the fact that 'general' is a reserved keyword, and I
have found no way to force or finagle linkage against a library named
'libgeneral'.

Any ideas?
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] externalproject_add and make -j >2 errors

[Witold E Wolski]

when I build the project with
cmake ../project
make
it builds

as soon as I am using
make -j 2

or greater
files within the project are being build before adding the dependencies finished


Maybe also someone can also give hint how to speed up or avoid the
update step, configure and build step on external_projects if they are already
build?

best
Witold




-- 
Witold Eryk Wolski
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

Re: [CMake] multi core project

[Williams, Norman K]

Add this:

set(proj CORE0)
ExternalProject_Add_Step(${proj} forcebuild
  COMMAND ${CMAKE_COMMAND} -E remove
  ${CMAKE_CURRENT_BUILD_DIR}/${proj}-prefix/src/${proj}-stamp/${proj}-build
  DEPENDEES configure
  DEPENDERS build
  ALWAYS 1
  )

ExternalProject keeps track of project phases based on 'stamp' files that
are created if a stage is completed successfully.
The stuff above removes the stamp for 'build' so that a build is forced
every time you run make (or the build tool of your choice).

You can also just build in the directory for CORE0 which the way you have
it set up would be
${CMAKE_CURRENT_BUILD_DIR}/${proj}-prefix/src/${proj}-build I believe.

We generally keep all our ExternalProject build directories grouped
together on the same level by setting the BINARY_DIR argument to
ExternalProject_add. This overrides (the way SOURCE_DIR does) the default
place where things get built.



--
Kent Williams norman-k-willi...@uiowa.edu






On 11/19/13 12:31 PM, "Arne Pagel"  wrote:

>Dear all,
>
>I just tried to use the ExternalProject_Add for this multicore project,
>having different separate
>camke projects for each core
>
>Now I have 2 Problems:
>
>1.)
>with the ExternalProject_Add and a given source dir it seams that my
>external projects are not
>rebuild if I made some changes there. Is there some nice way to rebuild
>the exeternal project all
>the time?
>
>This is how I call the External Project now:
>
>ExternalProject_Add(
>   CORE0
>
>   SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/core0
>
>   CMAKE_ARGS
>-DCMAKE_TOOLCHAIN_FILE=${CMAKE_CURRENT_SOURCE_DIR}/MyToolChain.cmake
>
>   UPDATE_COMMAND ""
>   INSTALL_COMMAND ""
>)
>
>
>2.)
>Since there is some code generation involved which produces a number of
>randomly named c files I
>have to use a globbing function to get all source files.
>This inherits, that before each build, I have to call "make
>rebuild_cache", in order to scan for
>these new C files. (Is ther maybe a smarter way to do this?)
>So I have to include also this step within the build, I tried
>ExternalProject_Add_Step, but so far I
>couldn't get it running make in the  dir.
>
>
>
>Any suggestion for me?
>
>
>
>
>
>
>--
>
>Powered by www.kitware.com
>
>Please keep messages on-topic and check the CMake FAQ at:
>http://www.cmake.org/Wiki/CMake_FAQ
>
>Kitware offers various services to support the CMake community. For more
>information on each offering, please visit:
>
>CMake Support: http://cmake.org/cmake/help/support.html
>CMake Consulting: http://cmake.org/cmake/help/consulting.html
>CMake Training Courses: http://cmake.org/cmake/help/training.html
>
>Visit other Kitware open-source projects at
>http://www.kitware.com/opensource/opensource.html
>
>Follow this link to subscribe/unsubscribe:
>http://www.cmake.org/mailman/listinfo/cmake




Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

Re: [CMake] multi core project

[Arne Pagel]

Dear all,

I just tried to use the ExternalProject_Add for this multicore project, having 
different separate
camke projects for each core

Now I have 2 Problems:

1.)
with the ExternalProject_Add and a given source dir it seams that my external 
projects are not
rebuild if I made some changes there. Is there some nice way to rebuild the 
exeternal project all
the time?

This is how I call the External Project now:

ExternalProject_Add(
   CORE0

   SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/core0

   CMAKE_ARGS 
-DCMAKE_TOOLCHAIN_FILE=${CMAKE_CURRENT_SOURCE_DIR}/MyToolChain.cmake

   UPDATE_COMMAND ""
   INSTALL_COMMAND ""
)


2.)
Since there is some code generation involved which produces a number of 
randomly named c files I
have to use a globbing function to get all source files.
This inherits, that before each build, I have to call "make rebuild_cache", in 
order to scan for
these new C files. (Is ther maybe a smarter way to do this?)
So I have to include also this step within the build, I tried 
ExternalProject_Add_Step, but so far I
couldn't get it running make in the  dir.



Any suggestion for me?






--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] Building Matlab Mex extensions that link to ITK?

[Williams, Norman K]

Has anyone else come up with an elegant solution for this?

If I want to call ITK from a Matlab MEX extension written in C++, I run
into problems with telling it the libraries with which to link.

The ITK_LIBRARIES variable is a list of imported library targets which
CMake converts to actual library paths when it links a library or
executable.

But to compile a MEX file, we're using a custom command along the lines of

   add_custom_command(OUTPUT ${MEX_PREFIX}.${MATLAB_MEX_EXT}
 COMMAND ${MATLAB_MEX_PATH} -cxx
${CMAKE_CXX_FLAGS_Release} ${MEX_SRC_PATH}
${ITK_INCLUDES} ${ITK_LIBRARIES}
 -I${Teem_INCLUDE_DIR} -L${Teem_LIBRARY_DIR}  -lteem
${ZLIB_LIBRARY}
 DEPENDS ${MEX_SRC_PATH}
 IMPLICIT_DEPENDS C ${MEX_SRC_PATH}
 COMMENT "BUILDING MEX_FILE: ${MEX_SRC_PATH}" )

But that doesn't work because CMake gives the target names in
ITK_LIBRARIES instead of the actual libraries.

I tried this:

find_package(ITK NO_MODULE REQUIRED)
include(${ITK_USE_FILE})

set(ITK_LOCAL_LIBS)
foreach(lib ${ITK_LIBRARIES})
  get_target_property(_lib ${lib} IMPORTED_LOCATION)

  list(APPEND ITK_LOCAL_LIBS ${_lib})endforeach()

But all the IMPORTED_LOCATION for ITK libraries is _lib-NOTFOUND



--
Kent Williams norman-k-willi...@uiowa.edu







Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

Re: [CMake] Select the Visual C++ Compiler November 2013 CTP with CMake generated projects?

[Thompson, K T]

That did the trick.  Thank you.

I was looking to set the Toolset from within the GUI, but it doesn't appear 
that CMake current supports this operation.

-kt

From: Petr Kmoch [mailto:petr.km...@gmail.com]
Sent: Tuesday, November 19, 2013 9:28 AM
To: Thompson, K T
Cc: cmake@cmake.org
Subject: Re: [CMake] Select the Visual C++ Compiler November 2013 CTP with 
CMake generated projects?

Hi Kelly.
This should be possible using CMake's command-line option -T which specifies 
the toolset to use.

Petr

On Tue, Nov 19, 2013 at 4:41 PM, Thompson, K T 
mailto:k...@lanl.gov>> wrote:
Hi,
Is there a way to tell CMake to generate Visual Studio 2013 projects that use 
the November 2013 CTP version of the compiler [1]?  It looks like I can modify 
each project in my VS solution manually [2] but this is not particularly 
convenient when CMake is used to generate the solution files.
[1] 
http://blogs.msdn.com/b/vcblog/archive/2013/11/18/announcing-the-visual-c-compiler-november-2013-ctp.aspx
[2] For each project, edit the properties and set "Platform Toolset" to "Visual 
C++ Compiler Nov 2013 CTP (CTP_Nov2013)".

-kt
Kelly Thompson
k...@lanl.gov


--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

Re: [CMake] Select the Visual C++ Compiler November 2013 CTP with CMake generated projects?

[Petr Kmoch]

Hi Kelly.

This should be possible using CMake's command-line option -T which
specifies the toolset to use.

Petr


On Tue, Nov 19, 2013 at 4:41 PM, Thompson, K T  wrote:

>  Hi,
>
> Is there a way to tell CMake to generate Visual Studio 2013 projects that
> use the November 2013 CTP version of the compiler [1]?  It looks like I can
> modify each project in my VS solution manually [2] but this is not
> particularly convenient when CMake is used to generate the solution files.
>
> [1]
> http://blogs.msdn.com/b/vcblog/archive/2013/11/18/announcing-the-visual-c-compiler-november-2013-ctp.aspx
>
> [2] For each project, edit the properties and set "Platform Toolset" to
> "Visual C++ Compiler Nov 2013 CTP (CTP_Nov2013)".
>
>
>
> -kt
>
> Kelly Thompson
>
> k...@lanl.gov
>
>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] Select the Visual C++ Compiler November 2013 CTP with CMake generated projects?

[Thompson, K T]

Hi,
Is there a way to tell CMake to generate Visual Studio 2013 projects that use 
the November 2013 CTP version of the compiler [1]?  It looks like I can modify 
each project in my VS solution manually [2] but this is not particularly 
convenient when CMake is used to generate the solution files.
[1] 
http://blogs.msdn.com/b/vcblog/archive/2013/11/18/announcing-the-visual-c-compiler-november-2013-ctp.aspx
[2] For each project, edit the properties and set "Platform Toolset" to "Visual 
C++ Compiler Nov 2013 CTP (CTP_Nov2013)".

-kt
Kelly Thompson
k...@lanl.gov

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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

[CMake] Stripping debug information of shared libraries on install/packaging

[Stefan Peters]

Hello,

I am using cmake on a Qt project and we're using google-breakpad for 
crash reporting. Therefore I am making release builds with debug 
information which are extracted later by the breakpad tools. Works fine, 
but I still have one problem on linux. On packaging the debug 
information are only stripped from the binaries, but not from the 
project-internal shared libraries (which are also targets of the 
project). I am using "set(CPACK_STRIP_FILES ON)".


The only solution I found is to include 2 post-build commands:

1.) if release-build-for-customers: run the breakpad tools
2.) if release-build-for-customers: strip all symbols

But this would require some more steps to the whole build process and 
perhaps there is a easier way to get rid of the symbols.


Regards,
  Stefan

--
Stefan Peters
Verified Systems International GmbH
Am Fallturm 1 (Eingang E, 3. OG)
28359 Bremen, Germany
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

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