date:20140806

[CMake] [ANNOUNCE] CMake 3.0.1 Released

2014-08-06 Thread Robert Maynard

We are pleased to announce that CMake 3.0.1 is now available for download.

The change log page for this bug-fix only release is here:
  http://public.kitware.com/Bug/roadmap_page.php?version_id=123
Please use the latest release from our download page:
  http://cmake.org/cmake/resources/software.html

Thanks for your support!

-
Changes in 3.0.1 since 3.0.0:

Adam Strzelecki (1):
  Ninja: Remove CMake includes from explicit depends (#14972)

Bob E (1):
  KWSys SystemInformation: No SA_RESTART on QNX

Brad King (10):
  cmake: Fix read-after-free while checking command-line arguments
  Fortran: Add support for GNU >= 4.9 compressed modules (#14975)
  bootstrap: Clarify name of configured source directory
  bootstrap: Fix "make test" and "make package" targets (#14989)
  UseSWIG: Fix check for noproxy flag (#14990)
  CMakeExpandImportedTargets: Do not read property on non-target (#15008)
  MSVC: Fix linking of DLLs on WinCE (#15013)
  Xcode: Fix static library creation for Xcode 6 (#15038)
  Check*CompilerFlag: Avoid ';' in common pattern (#15048)
  CMake 3.0.1

Chuck Atkins (1):
  cmcurl: Fix a build failure with the Cray compiler on Linux (#15026)

Mathieu MARACHE (1):
  FindQt4: Add nativewifi and qtga plugins

Stephen Kelly (1):
  QNX: Add missing flags for configurations and artifact creation.

Tim Blechmann (1):
  OS X: Install CFBundles as complete directories
-- 

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://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Windows Path Issues

2014-08-06 Thread Daniel Schepler

Maybe you need to set it to C:/software/propgcc/bin/propeller-elf-gcc.exe 
instead?  (Or ${WHATEVER_PATH}/propeller-elf-gcc${CMAKE_EXECUTABLE_SUFFIX} .)
--
Daniel

From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of da...@zemon.name
Sent: Wednesday, August 06, 2014 8:50 AM
To: cmake@cmake.org
Subject: Re: [CMake] Windows Path Issues

I've run it from CMD this time instead of Git Bash. Same results:

C:\Users\IGEN006\WORKSPACE_C_CPP\PropWare>cmake -G "Unix Makefiles" .
-- The C compiler identification is GNU 4.6.1
-- The CXX compiler identification is GNU 4.6.1
-- The COGCXX compiler identification is GNU 4.6.1
-- The ECOGC compiler identification is GNU 4.6.1
-- The ECOGCXX compiler identification is GNU 4.6.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/software/propgcc/bin/propeller-elf-gcc
CMake Error at CMakeLists.txt:6 (project):

  The CMAKE_C_COMPILER:

C:/software/propgcc/bin/propeller-elf-gcc

  is not a full path to an existing compiler tool.

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.

Any ideas are greatly appreciated.

Thanks,

David

-Original Message-
From: da...@zemon.name
Sent: Tuesday, August 5, 2014 3:34pm
To: "Ivan Hrasko" mailto:abhra...@gmail.com>>
Cc: cmake@cmake.org
Subject: Re: [CMake] Windows Path Issues

Sorry about that. I am using "Git Bash" which is definitely a confusing 
environment. The compiler is PropGCC - the target is an embedded system. 
PropGCC ships with GNU Make 3.81 (and "make --version" confirms that is the 
version of make in my PATH).

Perhaps the output of "bash --version" will help:

bash-3.1$ bash --version
GNU bash, version 3.1.0(1)-release (i686-pc-msys)
Copyright (C) 2005 Free Software Foundation, Inc.
bash-3.1$

Thanks,

David

-Original Message-
From: "Ivan Hrasko" mailto:abhra...@gmail.com>>
Sent: Tuesday, August 5, 2014 2:26pm
To: da...@zemon.name
Cc: cmake@cmake.org
Subject: Re: [CMake] Windows Path Issues
1. What your environment exactly is? It does not look like Windows only 
(because I see in your log: bash-3.1$ cmake -G "Unix Makefiles" . ), so I 
expect you are using something like Cygwin and when you use this kind of 
environment you can
have problems with paths. For example C:/software/propgcc/bin/propeller-elf-gcc 
is not a valid path for Cygwin, because cygwin uses /cygdrive/ in its path for 
things which are located in Windows.
2. When I use cmake on Windows (just Windows, cmd, not Cygwin or else) I use 
"MinGW Makefiles" not "Unix Makefiles" with GNU compilers.

2014-08-05 19:56 GMT+02:00 mailto:da...@zemon.name>>:

I'm generally a Linux guy but need this project to work on all three main 
platforms.

I have my toolchain file working nicely in Linux, but for some reason I'm 
getting an error on Windows. Here's top of the console output:

bash-3.1$ cmake -G "Unix Makefiles" .
-- The C compiler identification is GNU 4.6.1
-- The CXX compiler identification is GNU 4.6.1
-- The COGCXX compiler identification is GNU 4.6.1
-- The ECOGC compiler identification is GNU 4.6.1
-- The ECOGCXX compiler identification is GNU 4.6.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/software/propgcc/bin/propeller-elf-gcc
CMake Error at CMakeLists.txt:6 (project):
  The CMAKE_C_COMPILER:

C:/software/propgcc/bin/propeller-elf-gcc

  is not a full path to an existing compiler tool.

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.

This doesn't make too much sense to me. Anyone know why it would find the 
compiler at first and then loose it? The path that it lists is perfectly valid.

Thanks,

David

--

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://public.kitware.com/mailman/listinfo/cmake

--
Ivan Hrasko
mailto:abhra...@gmail.com>>
-- 

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: htt

Re: [CMake] Windows Path Issues

2014-08-06 Thread David Cole via CMake


What's in your toolchain file?

Is the file at "C:/software/propgcc/bin/propeller-elf-gcc" named 
propeller-elf-gcc.exe? Should there be a ".exe" in the compiler file 
name?


What "GNU make" are you using? (The primary ones well tested for use 
with CMake on Windows are MinGW and MSYS...)


Can you build anything with "Unix Makefiles" in a non-MSYS-shell 
Windows environment?


Seems like you'd want to use either "MSYS Makefiles" or "MinGW 
Makefiles" depending on your environment.



HTH,
David C.

--

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://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Windows Path Issues

2014-08-06 Thread david


I've run it from CMD this time instead of Git Bash. Same results:


C:\Users\IGEN006\WORKSPACE_C_CPP\PropWare>cmake -G "Unix Makefiles" .
-- The C compiler identification is GNU 4.6.1
-- The CXX compiler identification is GNU 4.6.1
-- The COGCXX compiler identification is GNU 4.6.1
-- The ECOGC compiler identification is GNU 4.6.1
-- The ECOGCXX compiler identification is GNU 4.6.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/software/propgcc/bin/propeller-elf-gcc
CMake Error at CMakeLists.txt:6 (project):
 
  The CMAKE_C_COMPILER:
 
C:/software/propgcc/bin/propeller-elf-gcc
  is not a full path to an existing compiler tool.
 
  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.
 
Any ideas are greatly appreciated.
 
Thanks,
David



-Original Message-
From: da...@zemon.name
Sent: Tuesday, August 5, 2014 3:34pm
To: "Ivan Hrasko" 
Cc: cmake@cmake.org
Subject: Re: [CMake] Windows Path Issues



Sorry about that. I am using "Git Bash" which is definitely a confusing 
environment. The compiler is PropGCC - the target is an embedded system. 
PropGCC ships with GNU Make 3.81 (and "make --version" confirms that is the 
version of make in my PATH).
 
Perhaps the output of "bash --version" will help:
 
bash-3.1$ bash --version
GNU bash, version 3.1.0(1)-release (i686-pc-msys)
Copyright (C) 2005 Free Software Foundation, Inc.
bash-3.1$
 
Thanks,
David


-Original Message-
From: "Ivan Hrasko" 
Sent: Tuesday, August 5, 2014 2:26pm
To: da...@zemon.name
Cc: cmake@cmake.org
Subject: Re: [CMake] Windows Path Issues




1. What your environment exactly is? It does not look like Windows only 
(because I see in your log: bash-3.1$ cmake -G "Unix Makefiles" . ), so I 
expect you are using something like Cygwin and when you use this kind of 
environment you can
have problems with paths. For example C:/software/propgcc/bin/propeller-elf-gcc 
is not a valid path for Cygwin, because cygwin uses /cygdrive/ in its path for 
things which are located in Windows.
2. When I use cmake on Windows (just Windows, cmd, not Cygwin or else) I use 
"MinGW Makefiles" not "Unix Makefiles" with GNU compilers.



2014-08-05 19:56 GMT+02:00 <[ da...@zemon.name ]( mailto:da...@zemon.name )>:

I'm generally a Linux guy but need this project to work on all three main 
platforms.
 
I have my toolchain file working nicely in Linux, but for some reason I'm 
getting an error on Windows. Here's top of the console output:
 
bash-3.1$ cmake -G "Unix Makefiles" . 
-- The C compiler identification is GNU 4.6.1
-- The CXX compiler identification is GNU 4.6.1
 -- The COGCXX compiler identification is GNU 4.6.1
-- The ECOGC compiler identification is GNU 4.6.1
-- The ECOGCXX compiler identification is GNU 4.6.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/software/propgcc/bin/propeller-elf-gcc
 CMake Error at CMakeLists.txt:6 (project):
  The CMAKE_C_COMPILER:
 
C:/software/propgcc/bin/propeller-elf-gcc
 
  is not a full path to an existing compiler tool.
 
  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
   the compiler, or to the compiler name if it is in the PATH.
 
This doesn't make too much sense to me. Anyone know why it would find the 
compiler at first and then loose it? The path that it lists is perfectly valid.
 
Thanks,
David
--

 Powered by [ www.kitware.com ]( http://www.kitware.com )

 Please keep messages on-topic and check the CMake FAQ at: [ 
http://www.cmake.org/Wiki/CMake_FAQ ]( 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 ]( 
http://cmake.org/cmake/help/support.html )
 CMake Consulting: [ http://cmake.org/cmake/help/consulting.html ]( 
http://cmake.org/cmake/help/consulting.html )
 CMake Training Courses: [ http://cmake.org/cmake/help/training.html ]( 
http://cmake.org/cmake/help/training.html )

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

 Follow this link to subscribe/unsubscribe:
[ http://public.kitware.com/mailman/listinfo/cmake ]( 
http://public.kitware.com/mailman/listinfo/cmake )


-- 

Ivan Hrasko
<[ abhra...@gmail.com ]( mailto:abhra...@gmail.com )>-- 

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: ht

[CMake] A potential fix for issue #0014656

2014-08-06 Thread Nicolas Bock

Hi,

I have modified the existing FindOpenMP.cmake code and added a Fortran
test. In addition I copied CheckCSourceCompiles.cmake to compile
Fortran code, which is needed by the Fortran test in FindOpenMP.cmake.
Please find the two scripts attached.

Could a CMake developer look the two scripts over and give me feedback
on their quality?

Thanks already,

nick
# - Finds OpenMP support
# This module can be used to detect OpenMP support in a compiler.
# If the compiler supports OpenMP, the flags required to compile with
# OpenMP support are returned in variables for the different languages.
# The variables may be empty if the compiler does not need a special
# flag to support OpenMP.
#
# The following variables are set:
#   OpenMP_C_FLAGS - flags to add to the C compiler for OpenMP support
#   OpenMP_CXX_FLAGS - flags to add to the CXX compiler for OpenMP support
#   OpenMP_Fortran_FLAGS - flags to add to the Fortran compiler for OpenMP support
#   OPENMP_FOUND - true if openmp is detected
#
# Supported compilers can be found at http://openmp.org/wp/openmp-compilers/

#=
# Copyright 2009 Kitware, Inc.
# Copyright 2008-2009 André Rigland Brodtkorb 
# Copyright 2012 Rolf Eike Beer 
#
# Distributed under the OSI-approved BSD License (the "License");
# see accompanying file Copyright.txt for details.
#
# This software is distributed WITHOUT ANY WARRANTY; without even the
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
# See the License for more information.
#=
# (To distribute this file outside of CMake, substitute the full
#  License text for the above reference.)

set(_OPENMP_REQUIRED_VARS)

function(_OPENMP_FLAG_CANDIDATES LANG)
  set(OpenMP_FLAG_CANDIDATES
#Empty, if compiler automatically accepts openmp
" "
#GNU
"-fopenmp"
#Microsoft Visual Studio
"/openmp"
#Intel windows
"-Qopenmp"
#PathScale, Intel
"-openmp"
#Sun
"-xopenmp"
#HP
"+Oopenmp"
#IBM XL C/c++
"-qsmp"
#Portland Group, MIPSpro
"-mp"
  )

  set(OMP_FLAG_GNU "-fopenmp")
  set(OMP_FLAG_HP "+Oopenmp")
  if(WIN32)
set(OMP_FLAG_Intel "-Qopenmp")
  else()
set(OMP_FLAG_Intel "-openmp")
  endif()
  set(OMP_FLAG_MIPSpro "-mp")
  set(OMP_FLAG_MSVC "/openmp")
  set(OMP_FLAG_PathScale "-openmp")
  set(OMP_FLAG_PGI "-mp")
  set(OMP_FLAG_SunPro "-xopenmp")
  set(OMP_FLAG_XL "-qsmp")
  set(OMP_FLAG_Cray " ")

  # Move the flag that matches the compiler to the head of the list,
  # this is faster and doesn't clutter the output that much. If that
  # flag doesn't work we will still try all.
  if(OMP_FLAG_${CMAKE_${LANG}_COMPILER_ID})
list(REMOVE_ITEM OpenMP_FLAG_CANDIDATES "${OMP_FLAG_${CMAKE_${LANG}_COMPILER_ID}}")
list(INSERT OpenMP_FLAG_CANDIDATES 0 "${OMP_FLAG_${CMAKE_${LANG}_COMPILER_ID}}")
  endif()

  set(OpenMP_${LANG}_FLAG_CANDIDATES "${OpenMP_FLAG_CANDIDATES}" PARENT_SCOPE)
endfunction()

# sample openmp source code to test
set(OpenMP_C_TEST_SOURCE
"
#include 
int main() {
#ifdef _OPENMP
  return 0;
#else
  breaks_on_purpose
#endif
}
")

# same in Fortran
set(OpenMP_Fortran_TEST_SOURCE
  "
program test
use omp_lib
integer :: n
n = omp_get_num_threads()
end program test
  "
  )

# check c compiler
if(CMAKE_C_COMPILER_LOADED)
  # if these are set then do not try to find them again,
  # by avoiding any try_compiles for the flags
  if(OpenMP_C_FLAGS)
unset(OpenMP_C_FLAG_CANDIDATES)
  else()
_OPENMP_FLAG_CANDIDATES("C")
include(CheckCSourceCompiles)
  endif()

  foreach(FLAG IN LISTS OpenMP_C_FLAG_CANDIDATES)
set(SAFE_CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS}")
set(CMAKE_REQUIRED_FLAGS "${FLAG}")
unset(OpenMP_FLAG_DETECTED CACHE)
message(STATUS "Try OpenMP C flag = [${FLAG}]")
check_c_source_compiles("${OpenMP_C_TEST_SOURCE}" OpenMP_FLAG_DETECTED)
set(CMAKE_REQUIRED_FLAGS "${SAFE_CMAKE_REQUIRED_FLAGS}")
if(OpenMP_FLAG_DETECTED)
  set(OpenMP_C_FLAGS_INTERNAL "${FLAG}")
  break()
endif()
  endforeach()

  set(OpenMP_C_FLAGS "${OpenMP_C_FLAGS_INTERNAL}"
CACHE STRING "C compiler flags for OpenMP parallization")

  list(APPEND _OPENMP_REQUIRED_VARS OpenMP_C_FLAGS)
  unset(OpenMP_C_FLAG_CANDIDATES)
endif()

# check cxx compiler
if(CMAKE_CXX_COMPILER_LOADED)
  # if these are set then do not try to find them again,
  # by avoiding any try_compiles for the flags
  if(OpenMP_CXX_FLAGS)
unset(OpenMP_CXX_FLAG_CANDIDATES)
  else()
_OPENMP_FLAG_CANDIDATES("CXX")
include(CheckCXXSourceCompiles)

# use the same source for CXX as C for now
set(OpenMP_CXX_TEST_SOURCE ${OpenMP_C_TEST_SOURCE})
  endif()

  foreach(FLAG IN LISTS OpenMP_CXX_FLAG_CANDIDATES)
set(SAFE_CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS}")
set(CMAKE_REQUIRED_FLAGS "${FLAG}")
unset(OpenMP_FLAG_DETECTED CACHE)
message(STATUS "Try OpenMP CXX flag = [${FLA

[CMake] "make package_source" with only symlinks in a subdirectory fails

2014-08-06 Thread Andre Naujoks

Hi.

I reported this bug to the debian bug-tracker some time ago, but there
seems to be no activity regarding this.
So I report this here as well and hope for someone to respond. I created
a patch (see below), which works for me,
but might change things in a completely wrong place.

I am on cmake version 2.8.12.1 (debian version 2.8.12.1-1.6)

This is the text of the debian bug report
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749892):



If I try to create a source package with cmake via CPack and "make
package_source" and there is a directory in the sources, that only
contains symlinks (only one in my case), the generation of the
source package fails with:

CPack Error: Cannot create symlink:  --> 

where source and destination are the file/symlink names of course.

It seems CPack tries to create the paths for the destination only if
it copies files and not when creating symlinks.

The following patch fixes this for me. I don't know, if this is
actually the right place to put this, but it should point to the
exact problem.


diff -Naur cmake-2.8.12.1_orig/Source/kwsys/SystemTools.cxx
cmake-2.8.12.1/Source/kwsys/SystemTools.cxx
--- cmake-2.8.12.1_orig/Source/kwsys/SystemTools.cxx2013-11-05
20:07:23.0 +0100
+++ cmake-2.8.12.1/Source/kwsys/SystemTools.cxx 2014-05-30
14:25:23.912154919 +0200
@@ -2835,6 +2835,9 @@
 #else
 bool SystemTools::CreateSymlink(const char* origName, const char* newName)
 {
+  kwsys_stl::string destination_dir = newName;
+  destination_dir = GetFilenamePath(destination_dir);
+  MakeDirectory(destination_dir.c_str());
   return symlink(origName, newName) >= 0;
 }
 #endif




Regards
  Andre
-- 

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://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Combining several static libraries into a single static library

2014-08-06 Thread David Cole via CMake

Seems like your best bet using CMake would be to use OBJECT libraries 
for your Project01 through Project99 -- and then use STATIC libraries 
for your ReleaseLibraries, which combine the objects of the appropriate 
project libraries...


You may need to use dummy source files for the static libs, depending 
on your build environment. See the Tests/ObjectLibrary/CMakeLists.txt 
in the CMake source tree for an example of all the different 
workarounds there are for older Visual Studios and Xcode...


http://cmake.org/gitweb?p=cmake.git;a=blob;f=Tests/ObjectLibrary/CMakeLists.txt;h=0aeefaa48753feec0c5e0af2f850b32d6cd28279;hb=55d6aa36a522f2dd7849ccd53d9e743a88f8c7a1

Another alternative would be to use STATIC libraries all the way 
through and let CMake do its transitive linking thing via 
target_link_libraries, but then your executables that link to them 
would need access to all of the static libraries including the 
Project01 to Project99 ones, even at the very client level where you 
are no doubt trying to simplify the build experience for those that 
require your release libraries. Good luck!



HTH,
David C.

--

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://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Ctest and custom measurements

2014-08-06 Thread ycollette . nospam

Hello,

I make a patch (against maint branch) to allow detection of:
.
Instead of only:
...

Where can I add some documentation related to this ?

Best regards,

YC

- Mail original -
De: "ycollette nospam" 
À: "David Cole" 
Cc: cmake@cmake.org
Envoyé: Mercredi 30 Juillet 2014 18:07:08
Objet: Re: [CMake] Ctest and custom measurements

OK, I will try to make a patch.

YC

- Mail original -
De: "David Cole" 
À: "ycollette nospam" 
Cc: cmake@cmake.org
Envoyé: Mercredi 30 Juillet 2014 17:42:07
Objet: Re: [CMake] Ctest and custom measurements

> By the way, this should be better documented in the cmake / ctest
> documentation.
> And we should be allowed to add measurements like these in the log:
> Log message - date - 0.1

I agree on both points. I would go even farther and say what you were
trying to do originally should have "just worked"...


> Do I fill a bug report for this ?

You can. Although it would be more effective if you could contribute a
patch to improve the docs, or to implement the code required to improve
the DartMeasurement parsing so it's not necessarily at the beginning of
the line, or even to accept "NamedMeasurement" values directly from the
output...

Are you able to submit patches that do any of this? Do you have the
time or the inclination?


:-)
David C.



-- 

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://public.kitware.com/mailman/listinfo/cmakediff --git a/Source/CTest/cmCTestTestHandler.cxx b/Source/CTest/cmCTestTestHandler.cxx
index 497774d..c44d630 100644
--- a/Source/CTest/cmCTestTestHandler.cxx
+++ b/Source/CTest/cmCTestTestHandler.cxx
@@ -410,12 +410,12 @@ cmCTestTestHandler::cmCTestTestHandler()
 
   this->LogFile = 0;
 
-  // regex to detect ...
+  // regex to detect .
   this->DartStuff.compile(
-"()");
-  // regex to detect each individual ...
+"(.*.*)");
+  // regex to detect each individual .
   this->DartStuff1.compile(
-"()");
+"(.*.*)");
 }
 
 //--
-- 

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://public.kitware.com/mailman/listinfo/cmake

[CMake] CMake 3.0, Qt 5, plugins and multiple executables inside OS X Bundle

2014-08-06 Thread Romain Leguay


Hello everyone,

I have a Qt application that search for another Qt applications and some 
plugins too. On Windows, I just create the executables in the same 
folder but on Mac OS X, I can't do that: I must create a bundle like this:

MyApplication.app/
Contents/
Frameworks/
**all qt library**
**all application dependencies**
libPluginInterface.dylib
Resources/
   **application icon**
MacOS/
MyApplication
subApplication1
subApplication2
PlugIns/
 **all my plugins** (.dylib)

When I'll open MyApplication.app, I'd like to launch MyApplication 
executable.


For now, my applications and plugins are store like this:
Project/
CMakeLists.txt
MyApplication/
CMakeLists.txt
 **source_files**
PluginInterface/
CMakeLists.txt
 **source_files**
subApplication1/
CMakeLists.txt
**source_files**
subApplication2/
CMakeLists.txt
**source_files**
 plugins/
CMakeLists.txt
plugin1/
CMakeLists.txt
**source_files**

MyApplication and all the plugins depends on PluginInterface (a shared 
library).


For now, I have many difficulties about the link path. I don't 
understand very well how to use @rpath for my libraries.


So, my first question: is-it possible to do something like this?
Second, can you show me some examples about this please?

Thank you.

Romain
--

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://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Help cmake First project

2014-08-06 Thread Angeliki Chrysochou

Hi Rodrigo,

Glad that it is working for you now. I just wanted to mention that I never
had to set the language as properties to the source files since cmake
detects it from the suffix of the source files you list, or at least I
never had a case where the language was not properly detected.

Other than that I agree with Hendrik's suggestions as well!

Cheers,
Angeliki






On Wed, Aug 6, 2014 at 5:54 AM, Hendrik Sattler 
wrote:

> Hi,
>
> -lm does not belong to CMAKE_CXX_FLAGS as it is a linker option to link
> libm.
> Use
> target_link_libraries(protpred-Gromacs-NSGA2 m)
> instead. (Don't search for libm, the linker knows where it is.)
>
> It is also more common to use a variable for the list of source files.
> That would make it also possible to set the compile language for all files
> in one command without listing files twice.
>
> Adding headers and not just .c/.cpp/.cxx files makes it easier when using
> an IDE.
>
>
> On 5. August 2014 22:13:54 MESZ, Rodrigo Faccioli <
> rodrigo.facci...@gmail.com> wrote:
> >Hi,
> >
> >I am thankfull for all help. Now, it is working :-)
> >
> >Radovan, thank you to try to run and your comments.
> >
> >My CMakeList.txt is showed below. I would like to know about best
> >practice
> >to make a CMakeList. If agree, I will compile others executables of my
> >project based on how I compiled this executable. In [1] contains my
> >full
> >project.
> >
> >cmake_minimum_required(VERSION 2.8)
> >
> ># project Information
> >project(2pg_cartesian)
> >set(PROJECT_VERSION "1.0")
> >
> ># Set compiler flags
> >SET ( CMAKE_CXX_FLAGS "-lm -pedantic")
> >
> >#Set CXX compiler for all files below
> >set_source_files_properties(include/LoadConfig.h PROPERTIES LANGUAGE
> >CXX )
> >set_source_files_properties(src/protpred-Gromacs-NSGA2.c  PROPERTIES
> >LANGUAGE CXX )
> >set_source_files_properties(src/LoadConfig.cpp  PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/ea_mono.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/topology.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/pdbio.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/protein.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/futil.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/pdbatom.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/messages.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/topologyio.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/topologylib.c  PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/randomlib.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/vector_math.c  PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/string_owner.c  PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/math_owner.c   PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/osutil.c   PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/load_parameters.c  PROPERTIES LANGUAGE
> >CXX )
> >set_source_files_properties(src/objective.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/aminoacids.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/aminoacids_io.c  PROPERTIES LANGUAGE
> >CXX )
> >set_source_files_properties(src/populationio.c  PROPERTIES LANGUAGE CXX
> >)
> >set_source_files_properties(src/rotation.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/solution.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/gromacs_objectives.c  PROPERTIES
> >LANGUAGE
> >CXX )
> >set_source_files_properties(src/solutionio.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/algorithms.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/ea_nsga2.c  PROPERTIES LANGUAGE CXX )
> >set_source_files_properties(src/dominance.c PROPERTIES LANGUAGE CXX )
> >
> ># set include
> >include_directories(include)
> >
> ># add libries
> >add_library(2PG-NSGA2_lib STATIC
> >src/LoadConfig.cpp
> >src/ea_mono.c
> >src/topology.c
> >src/pdbio.c
> >src/protein.c
> >src/futil.c
> >src/pdbatom.c
> >src/messages.c
> >src/topologyio.c
> >src/topologylib.c
> >src/randomlib.c
> >src/vector_math.c
> >src/string_owner.c
> >src/math_owner.c
> >src/osutil.c
> >src/load_parameters.c
> >src/objective.c
> >src/aminoacids.c
> >src/aminoacids_io.c
> >src/populationio.c
> >src/rotation.c
> >src/solution.c
> >src/gromacs_objectives.c
> >src/solutionio.c
> >src/algorithms.c
> >src/ea_nsga2.c
> >src/dominance.c
> >) #end of 2PG-NSGA2_lib
> >
> ># add target
> >add_executable(protpred-Gromacs-NSGA2 src/protpred-Gromacs-NSGA2.c)
> >target_link_libraries(protpred-Gromacs-NSGA2 2PG-NSGA2_lib)
> >
> ># install
> >install(TARGETS protpred-Gromacs-NSGA2 DESTINATION bin)
> >
> >[1] https://dl.dropboxusercontent.com/u/4270818/2pg_cartesian_cmake.zip
> >
> >Best regards,
> >
> >--
> >Rodrigo Antonio Faccioli, Ph.D
> >Development Software for Structural Bioinformatics
> >Barao de Maua University
> >University of S

[CMake] Combining several static libraries into a single static library

2014-08-06 Thread Johan Laneau

Hi,

I am in the process of deploying CMake into the build process of our 
department. I got already quite a lot of it working but I get stuck at one 
point: I can't see how we can combine several static libraries into a single 
static library with CMake.

I'll give some background first, to help you understand my problem. Our code is 
split up in more than 100 projects. Echo of those project is built into static 
libraries. In our department we work with static libraries because we target 
embedded systems that don't have support shared libraries, so shared libraries 
are not allowed. The static libraries can have dependencies on other projects. 
We build these project on many different platforms so CMake will definitely 
help in our build system.
With our current build system, we combine these static libraries into  "Release 
libraries". "Release libraries" are a combination of all required static 
libraries (no dependencies left anymore) into a single static library without 
any new code being added. This makes it very easy to release the combined 
functionality to a 3rd Party (such as another department or customer). We have 
a lot of "Release Libraries" with different combinations of the projects 
because we target different applications.

So I could simplify our build structure as below:
/Project01 (Static library)
/Project02 (Static library)
/Project03 (Static library)
...
/Project99 (Static library)
/ReleaseLibrary01 (Static library links e.g. Project01, Project02 and Project03)
/ReleaseLibrary02 (Static library links e.g. Project01, Project02 and Project04)
/ReleaseLibrary02 (Static library links e.g. Project05, Project06 and Project99)
/...

We already succeeded in building all our projects into static libraries with 
CMake. We also succeeded in building our test applications based upon those 
static libraries including the resolution of the dependencies (CMake is easy 
for this).
But we are not able to build our "Release Libraries". Simply adding a target 
with add_library for the "Release Library" does not work.

What I already read so far is that there are several workarounds: (e.g. rebuild 
the "Release Library" with the source of all dependent projects, unpack all 
libraries and repack again with platform specific commands, etc.). Some 
references I found are: 
https://svn.jmodelica.org/FMILibrary/trunk/Config.cmake/mergestaticlibs.cmake, 
https://code.google.com/p/toadlet/source/browse/cmake/Modules/MergeStaticLibraries.cmake,
 http://www.cmake.org/pipermail/cmake/2011-February/043002.html. I also saw 
that CMake supports an OBJECT library which might be helpful.

All of this seems very clumsy to me and I can't find any convergence on the 
best way to approach this. Is there any good reference where it is guided how 
to combine static libraries into a single static library with CMake ?

Thanks already for the support.

Johan Laneau
Software Architect, NXP Software

Interleuvenlaan 80, B-3001 Leuven, Belgium
Phone: +32 495 354 839, Fax: +32 16 390 855
E-mail: johan.lan...@nxp.com, 
http://www.nxpsoftware.com


-- 

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://public.kitware.com/mailman/listinfo/cmake

[CMake] [ANNOUNCE] CMake 3.0.1 Released

Re: [CMake] Windows Path Issues

Re: [CMake] Windows Path Issues

Re: [CMake] Windows Path Issues

[CMake] A potential fix for issue #0014656

[CMake] "make package_source" with only symlinks in a subdirectory fails

Re: [CMake] Combining several static libraries into a single static library

Re: [CMake] Ctest and custom measurements

[CMake] CMake 3.0, Qt 5, plugins and multiple executables inside OS X Bundle

Re: [CMake] Help cmake First project

[CMake] Combining several static libraries into a single static library

11 matches

Site Navigation

Mail list logo

Footer information