Re: [CMake] Packaging debug symbol files on Windows

2015-07-27 Thread J Decker
Debug also adds padding between functions and stack checking which can significantly add to code size for smaller libraries... or libraries with lots of tiny functions. On Mon, Jul 27, 2015 at 9:13 AM, Andreas Pakulat wrote: > Hi Nils, > > On Mon, Jul 27, 2015 at 3:58 PM, Nils Gladitz > wrote:

[CMake] FindPythonInterp.cmake and FindPythonLibs.cmake Modules Find Different Pythons

2015-07-27 Thread digitalriptide
When I execute FindPythonLibs.cmake and FindPythonInterp.cmake on the same system, they locate different Python installations. I am running OS X with cmake 3.2.3. FindPythonLibs picks up the system-provided python installation, while FindPythonInterp picks up the version of Python I installed throu

Re: [CMake] [cmake-developers] check_cxx_source_compiles and include directories

2015-07-27 Thread Roman Wüger
So, here is the piece of code which works Main CMakeLists.txt: project(MyProject) list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake) if (APPLE) set(CMAKE_CXX_EXTENSIONS OFF) # Use -std=c++11 instead of -std=gnu++11 endif() set(CMAKE_CXX_STANDARD 11) include(CheckCXXCom

[CMake] Cross compiling & conflicting declarations

2015-07-27 Thread Sepp Wolf
Hello, I'm using CMake 3.2.2 on Solaris 10 x86. I've built a toolchain to cross compile for SPARC, which is working fine for software with GNU autotools. But now I'm trying to compile Synergy, which is based on CMake, and I have lots of troubles with double declarations: [sepp@synergy /home/sepp/

Re: [CMake] Packaging debug symbol files on Windows

2015-07-27 Thread Andreas Pakulat
Hi Nils, On Mon, Jul 27, 2015 at 3:58 PM, Nils Gladitz wrote: > On 07/27/2015 03:46 PM, Andreas Pakulat wrote: > >> I've meanwhile also noticed that the default compiler flags that CMake >> uses include the debug information in the dll itself (dll size is >> doubled), so for now don't even have

Re: [CMake] Packaging debug symbol files on Windows

2015-07-27 Thread Nils Gladitz
On 07/27/2015 03:46 PM, Andreas Pakulat wrote: I've meanwhile also noticed that the default compiler flags that CMake uses include the debug information in the dll itself (dll size is doubled), so for now don't even have to have the separate pdb files packaged anymore (in this case the pdb info i

Re: [CMake] Packaging debug symbol files on Windows

2015-07-27 Thread Andreas Pakulat
Hi Nils, On Mon, Jul 27, 2015 at 3:12 PM, Nils Gladitz wrote: > On 07/27/2015 02:25 PM, Andreas Pakulat wrote: > >> Hi, >> >> I'm trying to generate a zip file (on Windows) for a shared library >> including the generated debug symbols in pdb files with CPack. >> Unfortunately CPack does not seem

Re: [CMake] Packaging debug symbol files on Windows

2015-07-27 Thread Nils Gladitz
On 07/27/2015 02:25 PM, Andreas Pakulat wrote: Hi, I'm trying to generate a zip file (on Windows) for a shared library including the generated debug symbols in pdb files with CPack. Unfortunately CPack does not seem to pick up the pdb files all by itself and after cross-reading the cpack docs in

[CMake] Packaging debug symbol files on Windows

2015-07-27 Thread Andreas Pakulat
Hi, I'm trying to generate a zip file (on Windows) for a shared library including the generated debug symbols in pdb files with CPack. Unfortunately CPack does not seem to pick up the pdb files all by itself and after cross-reading the cpack docs in the cmake wiki I didn't see any switch to enable

Re: [CMake] TI-C CMAKE_C_LINK_EXECUTABLE order

2015-07-27 Thread Florian Reinhard via CMake
Hi Falk, the TI Docs contains the following line: cl6x --run_linker {--rom_model | --ram_model} filenames [options] [--output_file= name.out] --library= library [lnk.cmd] therefore i'd suggest the following changes: set(CMAKE_C_LINK_EXECUTABLE " --run_linker --map_file=.map --output_file