Re: [cmake-developers] [CMake] 2.8.11-rc3 generator expression error

2013-04-25 Thread Brad King
On 04/25/2013 03:34 AM, Stephen Kelly wrote:
 I haven't had time to investigate fully, but this patch should 'fix' the 
 problem:
[snip]
 I'll investigate later to see if it's the right fix and why.

Great!  I've turned that patch into this commit:

 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de9d4a63

See commit message for an explanation that makes sense to me.

Since these generator expressions are constructed and evaluated
internally to CMake and never exposed it should be easy to
adjust how this works in the future.  Therefore I'm going to
take this as the fix for 2.8.11-rc4 if it is clean on the test
dashboard tonight.

When you have time to investigate in more detail, please
extend this topic with a test case covering

 target_link_libraries(B debug A)

where A is a target instead of an external library name.
Amazingly/apparently we do not have this in the test suite yet.

Thanks,
-Brad
--

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


Re: [cmake-developers] [CMake] 2.8.11-rc3 generator expression error

2013-04-25 Thread Brad King
On 04/25/2013 11:02 AM, Stephen Kelly wrote:
 Brad King wrote:
 Great!  I've turned that patch into this commit:

  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de9d4a63

 See commit message for an explanation that makes sense to me.
 
 The commit message is correct, but it's not the whole story. We also need to 
 validate the it-Value as a target name acceptable to TARGET_PROPERTY.
 
 I've pushed the fix-multi-config-tll-include-dirs branch to my clone.

That's a much more detailed explanation, thanks.

Pre-evaluating the expression as Debug regardless of the
configuration involved feels like a hack.  Since this all occurs
at generate time already anyway, why are we constructing a genex
only to evaluate it immediately elsewhere in the generator code?

Why can't GetIncludeDirectories just evaluate it-Value as a
genex with the current configuration, and if it is a valid target
name then lookup its INTERFACE_INCLUDE_DIRECTORIES and use that
immediately?

Thanks,
-Brad
--

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


Re: [cmake-developers] [CMake] 2.8.11-rc3 generator expression error

2013-04-25 Thread Stephen Kelly
Brad King wrote:

 I've pushed the fix-multi-config-tll-include-dirs branch to my clone.
 
 That's a much more detailed explanation, thanks.
 
 Pre-evaluating the expression as Debug regardless of the
 configuration involved feels like a hack.  Since this all occurs
 at generate time already anyway, why are we constructing a genex
 only to evaluate it immediately elsewhere in the generator code?
 
 Why can't GetIncludeDirectories just evaluate it-Value as a
 genex with the current configuration, and if it is a valid target
 name then lookup its INTERFACE_INCLUDE_DIRECTORIES and use that
 immediately?

Good question. Reading the code, I can't see any reason it needs to be that 
way. It's possible that when I implemented that I was focussed on re-using 
the code in the processIncludeDirectories function.

Changing it as you describe would probably make the caching easier too 
because the includes could be cached directly. This is an area where we had 
performance problems before when running cmake on the llvm repo.

Thanks,

Steve.


--

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


Re: [cmake-developers] [CMake] 2.8.11-rc3 generator expression error

2013-04-25 Thread Brad King
On 4/25/2013 6:15 PM, Stephen Kelly wrote:
 Brad King wrote:
 Why can't GetIncludeDirectories just evaluate it-Value as a
 genex with the current configuration, and if it is a valid target
 name then lookup its INTERFACE_INCLUDE_DIRECTORIES and use that
 immediately?
 
 Good question. Reading the code, I can't see any reason it needs to be that 
 way.

I looked into implementing this and realized that we're not propagating
usage requirements from the entire link closure, only from the direct
dependencies.  In an earlier design iteration the transitive requirements
were brought in by evaluation of the interface properties themselves.
Now that tll() doesn't touch the properties and the requirements are
simply appended during generation we need to use the full link closure.

I've drafted a change to convert cmTarget::GetIncludeDirectories and
cmTarget::GetCompileDefinitions over to share a common internal usage
requirements API that uses GetLinkInformation to get the transitive link
closure and looks up the INTERFACE_* properties in every linked target.
The caching is simplified because we never need to clear it since these
are now only called during generation and never during configuration.

I'll report back after doing more testing.

Thanks,
-Brad
--

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


[CMake] Cygwin Boost find error

2013-04-25 Thread Lloyd
Hi,
I am building a project in both Windows 7 and Cygwin. I am using boost
libraries in the project and it works correctly in windows

FIND_PACKAGE(Boost REQUIRED COMPONENTS unit_test_framework)

When I try to configure in cygwin it returns error saying that could not
find boost. From Cygwin installer i have installed boost (both source as
well as the library version). Still cmake could not find it. I also tried
to locate the library, but could not find it. Can you please tell me the
default location of boost in cygwin? or is there a way to locate the
install paths of libraries?

I think it is not possible to use the Windows version of boost with cygwin
as I am using different compilers (Visual studio in windows and gcc in
cygwin).

Thanks,
  Lloyd
--

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] 2.8.11-rc3 generator expression error

2013-04-25 Thread Stephen Kelly
Brad King wrote:

 $ cmake .. -GXcode
 ...
 CMake Error at CMakeLists.txt:5 (target_link_libraries):
   Error evaluating generator expression:
 
 $TARGET_PROPERTY:$$CONFIG:DEBUG:A,INTERFACE_INCLUDE_DIRECTORIES
 
   $TARGET_PROPERTY:tgt,prop expression requires a non-empty target name.
 ...

I haven't had time to investigate fully, but this patch should 'fix' the 
problem:

diff --git a/Source/cmTarget.cxx b/Source/cmTarget.cxx
index 66c22b1..8174ac2 100644
--- a/Source/cmTarget.cxx
+++ b/Source/cmTarget.cxx
@@ -2947,8 +2947,8 @@ std::vectorstd::string 
cmTarget::GetIncludeDirectories(const char *config)
   }
   cmGeneratorExpression ge(it-Backtrace);
   cmsys::auto_ptrcmCompiledGeneratorExpression cge = ge.Parse(
-  $TARGET_PROPERTY: +
-  it-Value + 
,INTERFACE_INCLUDE_DIRECTORIES);
+  $$BOOL: + it-Value + :$TARGET_PROPERTY: +
+  it-Value + 
,INTERFACE_INCLUDE_DIRECTORIES);
 
   this-Internal-
CachedLinkInterfaceIncludeDirectoriesEntries.push_back(
 new cmTargetInternals::IncludeDirectoriesEntry(cge,


I'll investigate later to see if it's the right fix and why.

Thanks,

Steve.


--

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] [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

2013-04-25 Thread Biddiscombe, John A.
Ward


Currently, using find_package(HDF5 NO_MODULE) results in Visual Studio 
attempting to link against the shared libraries (.dll) themselves, instead of 
the associated import libraries (.lib).  I'm still trying to figure out why 
this is, exactly, but in the mean time I am using the work-around mentioned in 
your previous email.


Using find_package(HDF5 NO_MODULE) does not do this at all. If you 
find_package(HDF5) and allow the FindHDF5.cmake supplied with cmake to run, 
then it picks up the dll instread of the lib. I tried this on a new version of 
cmake and it appears to be a new 'bug' - but if you use the NO_MODULE approach 
then you use on the the hdf-config.cmake supplied when hdf5 is installed and 
this does not happen.

If it is happening, then you need to go through your CMakeLists.txt and remove 
any ${HDF5_C_LIBRARY} type of references and instead just link to hdf5, the 
target is defined as imported and all these errors go away. I presume this is 
the fix you are referring to.

The trouble arises when you must support a cmake version of hdf5 (easy) and an 
old style non cmake install of hdf5, (pain in the arse).
AFAICT there is a bug in the findhdf5.cmake supplied with cmake itself which 
reports all these libraries as

HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.dll
Instead of
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.lib

(just tested with cmake 2.8.11-rc3 and hdf5 cmake branch from svn updated a few 
minutes ago)

I'm CC'ing the cmake list and Will (the maintainer of the findhdf5) just in 
case they have some feedback that's useful.

Looking at the findhdf5 module, it's not obvious to me where this value is set, 
so I won't attempt a fix (yet), but it'd be nice if we could get a fix into 
cmake before the next release- which is quite soon I guess since they're on rc3.

JB

--

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] Problem with CMAKE_AUTOMOC files not being regenerated or cleaned

2013-04-25 Thread Glenn Coombs
Hi,

I have a Qt4 program that I'm working on and ran into an issue yesterday
with the automoc cpp files.  I had added a new slot and connected a
comboxbox currentIndexChanged signal to it but when I ran the program I
could see messages on stdout complaining that my slot didn't exist.  I
tracked the problem down to the fact that the moc_ctrlBasic.cpp file was
not being regenerated.  If I look in my cmake build directory I currently
have 8 moc cpp files:

./moc_ctrlBasic.cpp
./moc_ctrlmenu.cpp
./moc_infoWin.cpp
./moc_qglDisplay.cpp
./moc_qglMultiWindow.cpp
./moc_qglWindow.cpp
./moc_videoGeneric.cpp
./yuv_player_automoc.cpp

I am using CMake 2.8.10.1 with Visual Studio 11 and when I do a clean
solution these 8 moc cpp files are not deleted.  In order to get my new
slot recognised I had to manually delete these moc files and then after a
rebuild everything worked as expected.  None of my cpp files #include
moc_xxx.cpp but that isn't necessary from my reading of the AUTOMOC
property (i.e. ctrlBasic.cpp only does a #include ctrlBasic.h).  What am
I doing wrong in my CMakeLists.txt file which looks like this:

cmake_minimum_required(VERSION 2.8.9 FATAL_ERROR)

project(yuv_player)

find_package(OpenGL REQUIRED)

find_package(Qt4 REQUIRED)
set(QT_USE_QTMAIN true)
set(QT_USE_QTOPENGL true)
include(${QT_USE_FILE})

set(CMAKE_AUTOMOC true)

if (MSVC)
add_definitions(/MP)# build in parallel
# disable the security warnings for fopen, scanf etc.
add_definitions(/D_CRT_SECURE_NO_WARNINGS /D_SCL_SECURE_NO_WARNINGS)
endif()

set(sources
main.cpp
yuv_tools.cpp
ctrlMenu/ctrlBasic.cpp
ctrlMenu/ctrlmenu.cpp
multiWindow/qglMultiWindow.cpp
multiWindow/qglDisplay.cpp
multiWindow/qglWindow.cpp
utils/readYuv.cpp
utils/readOut2.cpp
video_tools.cpp
ctrlMenu/infoWin.cpp
videoGeneric.cpp
)

set(headers
yuv_tools.h
ctrlMenu/ctrlBasic.h
ctrlMenu/ctrlmenu.h
ctrlMenu/infoWin.h
multiWindow/qglDisplay.h
multiWindow/qglMultiWindow.h
multiWindow/qglWindow.h
utils/readYuv.h
utils/readOut2.h
video_tools.h
ctrlMenu/infoWin.h
videoGeneric.h
defs.h
)

include_directories(
.
multiWindow
ctrlMenu
)

add_executable(yuv_player WIN32 ${sources} ${headers})

target_link_libraries(yuv_player ${QT_LIBRARIES} ${OPENGL_LIBRARIES})

--
Glenn
--

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] Cygwin Boost find error

2013-04-25 Thread Lloyd
Thanks the link helped me to solved the problem. Sorry, I shall avoid
irrelevant posts in the future


On Thu, Apr 25, 2013 at 12:30 PM, marco atzeri marco.atz...@gmail.comwrote:

 On 4/25/2013 8:54 AM, Lloyd wrote:

 Hi,
 I am building a project in both Windows 7 and Cygwin. I am using boost
 libraries in the project and it works correctly in windows

 FIND_PACKAGE(Boost REQUIRED COMPONENTS unit_test_framework)

 When I try to configure in cygwin it returns error saying that could not
 find boost. From Cygwin installer i have installed boost (both source as
 well as the library version). Still cmake could not find it. I also
 tried to locate the library, but could not find it. Can you please tell
 me the default location of boost in cygwin? or is there a way to locate
 the install paths of libraries?


 this is more a question for cygwin help list,
 anyway the development headers and libraries location
 are reported here:

 http://cygwin.com/packages/**libboost-devel/libboost-devel-**1.50.0-1http://cygwin.com/packages/libboost-devel/libboost-devel-1.50.0-1



 I think it is not possible to use the Windows version of boost with
 cygwin as I am using different compilers (Visual studio in windows and
 gcc in cygwin).


 correct. gcc4 package for cygwin


 Thanks,
Lloyd




 --

 Powered by www.kitware.com

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

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

 Follow this link to subscribe/unsubscribe:
 http://www.cmake.org/mailman/**listinfo/cmakehttp://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] Can't get CTEST_CUSTOM_ERROR_MATCH to work with CTest launchers

2013-04-25 Thread Nils Gladitz
One list entry in my CTEST_CUSTOM_ERROR_MATCH is FAILED:  (in my 
CTestCustom.cmake.in which is used to generate CTestCustom.cmake in the 
build directory).


With CTEST_USE_LAUNCHERS enabled this does not seem to match errors from 
custom commands e.g.:

FAILED: cmd.exe /c  [...]

On my CDash installation I see 0 build errors.

When I disable CTEST_USE_LAUNCHERS the error shows up on the dashboard 
and the FAILED:  line is highlighted indicating that a match has been 
made.


Is this by design (e.g. not implemented for launchers) or may I be 
missing something?
Is there e.g. extra work required for CTEST_CUSTOM_ERROR_MATCH to reach 
the launcher?


Nils

--
Nils Gladitz, B.Sc.
DICOM, Konnektivität und Entwicklung

Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
GERMANY
Handelsregister Nr. / Trade Register No. B3100 Göttingen
Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland

Tel: 0049 (0)551 634181-28
E-Mail: glad...@scivis.de
Web: www.scivis.de

--

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] Cygwin Boost find error

2013-04-25 Thread marco atzeri

On 4/25/2013 10:07 AM, Lloyd wrote:

Thanks the link helped me to solved the problem. Sorry, I shall avoid
irrelevant posts in the future



It is not irrelevant, but you have more chance to have the right answer
on the cygwin help list.

Regards
Marco


--

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] [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

2013-04-25 Thread Biddiscombe, John A.
Just to follow up my earlier mail,

HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.dll
Instead of
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.lib

Should have read
HDF5_C_LIBRARY C:/Program Files/HDF5/lib/hdf5_D.lib
To fix the problem a bit more obustly.

Trying to fix that left me with a problem of detecting 
debug/release/shared/static and I ended up rewriting the routine inside findhdf5
Here's a patch which I think improves the module somewhat. If someone could 
take a look at the diff and give me some feedback I'd be most grateful

Thanks

JB




0001-Fix-some-problems-with-FindHDF5-with-windows-shared-.patch
Description: 0001-Fix-some-problems-with-FindHDF5-with-windows-shared-.patch
--

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] [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

2013-04-25 Thread Michael Jackson
You tell the difference between debug  release by the naming of the library 
itself. All the debug libraries have a _D in them or some such thing like 
that.

For the Static/Dynamic there is a #define in one of the HDF5 headers (if built 
with CMake) that says how it was built. My own FindHDF5 does a try/compile 
for that #define to determine which libraries should be linked against and 
possibly included in deployments.

___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.jack...@bluequartz.net  www.bluequartz.net

On Apr 25, 2013, at 6:54 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:

 Just to follow up my earlier mail,
  
 HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.dll
 Instead of
 HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.lib
  
 Should have read
 HDF5_C_LIBRARY C:/Program Files/HDF5/lib/hdf5_D.lib
 To fix the problem a bit more obustly.
  
 Trying to fix that left me with a problem of detecting 
 debug/release/shared/static and I ended up rewriting the routine inside 
 findhdf5
 Here’s a patch which I think improves the module somewhat. If someone could 
 take a look at the diff and give me some feedback I’d be most grateful
  
 Thanks
  
 JB
  
  
 0001-Fix-some-problems-with-FindHDF5-with-windows-shared-.patch--
 
 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] MINGW and strip .dll.a files

2013-04-25 Thread Gregoire Aujay
Hello,

I am just forwarding our discussion to the mailing list. We did not use reply 
to all.

Highligth:
So, I see no point in striping the .dll.a file. But, of course, I might be 
wrong. Please, anybody can check this?


Regards,
Gregoire

From: Daniel Franzini [mailto:daniel.franz...@gmail.com]
Sent: jeudi 25 avril 2013 13:30
To: Gregoire Aujay
Subject: Re: [CMake] MINGW and strip .dll.a files

The strip program just removes unused symbols from any object code.

This is Win32/Mingw specific stuff (MSVC have the same stuff but they use their 
own object format).

When you compile a DLL, you have two options:

1.) hand write your own LoadLibrary/FreeLibrary code and just distribute the 
DLL with your
exe (or other DLL)

2.) static-link your exe against the dll.a file which is generated by the 
linker and is win32 specific magic code that have stubs to the functions it 
will call from the DLL.

Either way you have to distribute the DLL with your exe.

The .dll.a (called import library) file is generated by the linker with 
appropriate options and it is reported to be buggy in the past. I'm not sure 
nowadays.

So, I see no point in striping the .dll.a file. But, of course, I might be 
wrong. Please, anybody can check this?
On Thu, Apr 25, 2013 at 4:42 AM, Gregoire Aujay 
gau...@movea.commailto:gau...@movea.com wrote:
Hello ;

So you agree that CMake should not strip .dll.a files.

Currently that is what is done in the cmake_install.cmake files, e.g. I get 
(CMake 2.8.10.2):

IF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT} STREQUAL 
Unspecified)
  FILE(INSTALL DESTINATION ${CMAKE_INSTALL_PREFIX}/release/lib TYPE 
STATIC_LIBRARY OPTIONAL FILES XX/release/lib/libmyLib.dll.a)
  IF(EXISTS $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/release/lib/ libmyLib.dll.a 
AND
 NOT IS_SYMLINK $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/release/lib/ 
libmyLib.dll.a)
IF(CMAKE_INSTALL_DO_STRIP)
  EXECUTE_PROCESS(COMMAND YY/bin/strip.exe 
$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/release/lib/ libmyLib.dll.a)
ENDIF(CMAKE_INSTALL_DO_STRIP)
  ENDIF()
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR ${CMAKE_INSTALL_COMPONENT} STREQUAL 
Unspecified)


Unless someone tells me it is done intentionally I will file a bug.


Regards,
Gregoire

From: Daniel Franzini 
[mailto:daniel.franz...@gmail.commailto:daniel.franz...@gmail.com]
Sent: mercredi 24 avril 2013 19:52
To: Gregoire Aujay
Subject: Re: [CMake] MINGW and strip .dll.a files

AFAIK, the dll.a file is a import library

It contains code that magically calls the DLL functions without having you to 
write LoadLibrary/FreeLibrary code.

Why are you stripping it anyway? The import libray should be linked as-is with 
your binary and them strip the binary.

NOTE: it does not contain the actual DLL code. It only have stubs that calls 
DLL functions.
On Wed, Apr 24, 2013 at 10:58 AM, Gregoire Aujay 
gau...@movea.commailto:gau...@movea.com wrote:
Hello,

I am trying to package a stripped library built with MINGW.

When I activate strip during install or pack, I get link error (unresolved 
symbols) when using this library.
When I strip using -s option, everything is fine.

The difference is that my .dll.a is smaller when I use CMake strip feature. Gcc 
does not seem to strip the .dll.a file.

Is it a good approach to strip the .dll.a file ?

Regards,
Gregoire

--

Powered by www.kitware.comhttp://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



--
Daniel

Let us change our traditional attitude to the construction of programs. 
Instead of imagining that our main task is to instruct a computer what to do, 
let us concentrate rather on explaining to human beings what we want a computer 
to do. (Donald Knuth)

Yes, technogeeks can be funny, even if only to each other. 
(http://www.boogieonline.com/revolution/science/humor/)

Man is driven to create; I know I really love to create things. And while I'm 
not good at painting, drawing, or music, I can write software. (Yukihiro 
Matsumoto, a.k.a. ``Matz'')



--
Daniel

Let us change our traditional attitude to the construction of programs. 
Instead of imagining that our main task is to instruct a computer what to do, 
let us concentrate rather on explaining to human beings what we want a computer 
to do. (Donald Knuth)

Yes, technogeeks can be funny, even if only to each other. 
(http://www.boogieonline.com/revolution/science/humor/)

Man is driven to create; I know I really love to create things. And while I'm 
not good at painting, drawing, or music, I can write software. (Yukihiro 
Matsumoto, a.k.a. ``Matz'')
--

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: 

[CMake] coverage using gcov failed

2013-04-25 Thread Lloyd
Hi,

I am trying cmake in cygwin for code coverage analysis using gcov. My
source code is arranged as follows

CMakeLists.txt  src  tests

./src:
CMakeLists.txt  lib  main.cpp

./src/lib:
reverse

./src/lib/reverse:
CMakeLists.txt  reverse.cpp  reverse.h

./tests:
CMakeLists.txt  test_rev.cpp  test_runner.cpp



My main make file is also given below

#Root cmake file
cmake_minimum_required (VERSION 2.6)
PROJECT (Tutorial)
SET (DO_TEST false CACHE BOOL Enable Testing?)
SET (DO_CODE_COVERAGE false CACHE BOOL Enable Code coverage?)

if(DO_CODE_COVERAGE)
MESSAGE (STATUS Code coverage is enabled)
SET(CMAKE_CXX_FLAGS=-g -O0 -Wall -W -Wshadow -Wunused-variable
-Wunused-parameter -Wunused-function -Wunused -Wno-system-headers
-Wno-deprecated -Woverloaded-virtual -Wwrite-strings -fprofile-arcs
-ftest-coverage)
SET(CMAKE_C_FLAGS=-g -O0 -Wall -W -fprofile-arcs -ftest-coverage)
SET(CMAKE_SHARED_LINKER_FLAGS=-fprofile-arcs -ftest-coverage)
SET(CMAKE_EXE_LINKER_FLAGS=-fprofile-arcs -ftest-coverage)
endif(DO_CODE_COVERAGE)

ADD_SUBDIRECTORY(src/lib/reverse)
ADD_SUBDIRECTORY(src)

#Testing related code
if(DO_TEST)
MESSAGE (STATUS Testing is enabled)
ADD_SUBDIRECTORY(tests)
#ENABLE_TESTING()
include( CTest )
ADD_TEST(NAME Test WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/src/Debug COMMAND
test_rev)
endif(DO_TEST)


And the major portion of the cmake file of test executable is also given
below.


#Cmake file of Tests
cmake_minimum_required (VERSION 2.6)

SET(TST_SRC test_rev.cpp test_runner.cpp)

FIND_PACKAGE(Boost REQUIRED COMPONENTS unit_test_framework)

INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}../../src/lib/reverse)
ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK)
ADD_EXECUTABLE(test_rev ${TST_SRC})
TARGET_LINK_LIBRARIES(test_rev ${Boost_LIBRARIES})
TARGET_LINK_LIBRARIES(test_rev Reverse)
if(DO_CODE_COVERAGE)
MESSAGE(Yes code coverage in test)
TARGET_LINK_LIBRARIES(test_rev gcov)
endif(DO_CODE_COVERAGE)

When I run, I get the following error

$ make ExperimentalCoverage
   Site: llvm
   Build name: CYGWIN-c++.exe
Performing coverage
 Cannot find any coverage files. Ignoring Coverage request.
Built target ExperimentalCoverage

Why is the coverage files are not created?

Thanks,
  Lloyd
--

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] QT, CMake and ITK

2013-04-25 Thread Gabriel Santiago
Now, the only lib available to me is
ITKIOFactoryRegistration/itkImageIOFactoryRegisterManager.h...


On 24 April 2013 16:48, Gabriel Santiago santiago.eletr...@gmail.comwrote:

 Still not working... It could be something with the installation of ITK? I
 used to use it within Eclipse with no problem at all... But now it seems
 that some .h files are missing...


 On 24 April 2013 16:38, John Drescher dresche...@gmail.com wrote:

 On Wed, Apr 24, 2013 at 3:31 PM, Gabriel Santiago
 santiago.eletr...@gmail.com wrote:
  Actually my CMake is 2.8.7, ITK is 3.20.1 and QT is the latest...
 

 I believe this file should work. Although I really do not have any
 more time to help if it does not.

 project(test)

 cmake_minimum_required(VERSION 2.8 FATAL_ERROR)

 find_package(Qt4 REQUIRED)
 include(${QT_USE_FILE})

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

 set( qtproject_SRCS main.cpp)

 set(qtproject_UIS mainwindow.ui)

 QT4_WRAP_UI(qtproject_UIS_H ${qtproject_UIS})

 include_directories(${CMAKE_CURRENT_BINARY_DIR})

 add_executable(test ${qtproject_SRCS} ${qtproject_UIS_H})

 TARGET_LINK_LIBRARIES(test ${ITK_LIBRARIES} ${QT_LIBRARIES} )

 John




 --
 Gabriel Santiago

 ~As long as I live so long do I learn~
 Ramakhrishna




-- 
Gabriel Santiago

~As long as I live so long do I learn~
Ramakhrishna
--

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] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

2013-04-25 Thread Matthias Kretz
Hi,

I have several checks in my project that make cmake error out with 
FATAL_ERROR. This is submitted as error to the dashboard. In reality it would 
be an error if this error would not appear - and it is the expected result if 
cmake errors out. Is there a possiblity to invert the result of the configure 
step for certain system setups?

Alternatively I'd skip the CTEST_CONFIGURE call in the ctest script and just 
submit Notes that elaborate on the abort. But that doesn't show up on the 
dashboard at all.

Any ideas?

Cheers,
Matthias

-- 

Matthias Kretz (Germany)
http://kretzfamily.de/

--

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] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

2013-04-25 Thread Bill Hoffman

On 4/25/2013 9:15 AM, Matthias Kretz wrote:

Hi,

I have several checks in my project that make cmake error out with
FATAL_ERROR. This is submitted as error to the dashboard. In reality it would
be an error if this error would not appear - and it is the expected result if
cmake errors out. Is there a possiblity to invert the result of the configure
step for certain system setups?

Alternatively I'd skip the CTEST_CONFIGURE call in the ctest script and just
submit Notes that elaborate on the abort. But that doesn't show up on the
dashboard at all.

Any ideas?
Is this for an individual test?  If so, you can use the regex matching 
instead of return code to determine pass fail.  Would that work?


-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] coverage using gcov failed

2013-04-25 Thread Bill Hoffman

On 4/25/2013 8:26 AM, Lloyd wrote:

Hi,

I am trying cmake in cygwin for code coverage analysis using gcov. My
source code is arranged as follows

CMakeLists.txt  src  tests

./src:
CMakeLists.txt  lib  main.cpp

./src/lib:
reverse

./src/lib/reverse:
CMakeLists.txt  reverse.cpp  reverse.h

./tests:
CMakeLists.txt  test_rev.cpp  test_runner.cpp



My main make file is also given below

#Root cmake file
cmake_minimum_required (VERSION 2.6)
PROJECT (Tutorial)
SET (DO_TEST false CACHE BOOL Enable Testing?)
SET (DO_CODE_COVERAGE false CACHE BOOL Enable Code coverage?)

if(DO_CODE_COVERAGE)
MESSAGE (STATUS Code coverage is enabled)
SET(CMAKE_CXX_FLAGS=-g -O0 -Wall -W -Wshadow -Wunused-variable
-Wunused-parameter -Wunused-function -Wunused -Wno-system-headers
-Wno-deprecated -Woverloaded-virtual -Wwrite-strings -fprofile-arcs
-ftest-coverage)
SET(CMAKE_C_FLAGS=-g -O0 -Wall -W -fprofile-arcs -ftest-coverage)
SET(CMAKE_SHARED_LINKER_FLAGS=-fprofile-arcs -ftest-coverage)
SET(CMAKE_EXE_LINKER_FLAGS=-fprofile-arcs -ftest-coverage)
endif(DO_CODE_COVERAGE)

ADD_SUBDIRECTORY(src/lib/reverse)
ADD_SUBDIRECTORY(src)

#Testing related code
if(DO_TEST)
MESSAGE (STATUS Testing is enabled)
ADD_SUBDIRECTORY(tests)
#ENABLE_TESTING()
include( CTest )
ADD_TEST(NAME Test WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/src/Debug
COMMAND test_rev)
endif(DO_TEST)


And the major portion of the cmake file of test executable is also given
below.


#Cmake file of Tests
cmake_minimum_required (VERSION 2.6)

SET(TST_SRC test_rev.cpp test_runner.cpp)

FIND_PACKAGE(Boost REQUIRED COMPONENTS unit_test_framework)

INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}../../src/lib/reverse)
ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK)
ADD_EXECUTABLE(test_rev ${TST_SRC})
TARGET_LINK_LIBRARIES(test_rev ${Boost_LIBRARIES})
TARGET_LINK_LIBRARIES(test_rev Reverse)
if(DO_CODE_COVERAGE)
MESSAGE(Yes code coverage in test)
TARGET_LINK_LIBRARIES(test_rev gcov)
endif(DO_CODE_COVERAGE)

When I run, I get the following error

$ make ExperimentalCoverage
Site: llvm
Build name: CYGWIN-c++.exe
Performing coverage
  Cannot find any coverage files. Ignoring Coverage request.
Built target ExperimentalCoverage

Why is the coverage files are not created?



I don't see any add_test calls.  So, you are not running any code, so 
there is no code covered.


-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] coverage using gcov failed

2013-04-25 Thread Bill Hoffman

On 4/25/2013 9:47 AM, Bill Hoffman wrote:


I don't see any add_test calls.  So, you are not running any code, so
there is no code covered.

-Bill

I see it now.

Can you run:

ctest -D Experimental -VV

-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] coverage using gcov failed

2013-04-25 Thread Bill Hoffman

On 4/25/2013 9:52 AM, Bill Hoffman wrote:

I see it now.

Can you run:

ctest -D Experimental -VV

OK, never mind I know what is wrong...

make ExperimentalCoverage just does the coverage part.
make Experimental
make ExpermentalCoverage should work.

Or

cd buildtree
ctest -T all


Available options are:
  ctest -T all
  ctest -T start
  ctest -T update
  ctest -T configure
  ctest -T build
  ctest -T test
  ctest -T coverage
  ctest -T memcheck
  ctest -T notes
  ctest -T submit


-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] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

2013-04-25 Thread Matthias Kretz
On Thursday 25 April 2013 09:46:03 Bill Hoffman wrote:
 On 4/25/2013 9:15 AM, Matthias Kretz wrote:
  I have several checks in my project that make cmake error out with
  FATAL_ERROR. This is submitted as error to the dashboard. In reality it
  would be an error if this error would not appear - and it is the expected
  result if cmake errors out. Is there a possiblity to invert the result of
  the configure step for certain system setups?
  
  Alternatively I'd skip the CTEST_CONFIGURE call in the ctest script and
  just submit Notes that elaborate on the abort. But that doesn't show up
  on the dashboard at all.
  
  Any ideas?
 
 Is this for an individual test?  If so, you can use the regex matching
 instead of return code to determine pass fail.  Would that work?

I'm not sure we're talking about the same thing. I'm talking about 
ctest_configure - i.e. before build or tests. IIUC you're talking about regex 
matching at ctest_test?

Also note that CTEST_CUSTOM_ERROR_EXCEPTION has no effect (and it's documented 
to be used for ctest_build only).

Cheers,
Matthias

-- 

Matthias Kretz (Germany)
http://kretzfamily.de/

--

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] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

2013-04-25 Thread Bill Hoffman

On 4/25/2013 10:05 AM, Matthias Kretz wrote:

I'm not sure we're talking about the same thing. I'm talking about
ctest_configure - i.e. before build or tests. IIUC you're talking about regex
matching at ctest_test?
But, if you have a FATAL_ERROR in the configure step, no build files 
will be created and you won't even get a build of the software to test. 
  I thought you might have test cases that were complete projects.   I 
don't think you can change this.  It is not just the error in the 
output, it is that cmake returns an error code when run.  Basically the 
configure command fails.


-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] 2.8.11-rc3 generator expression error

2013-04-25 Thread Brad King
On 04/25/2013 03:34 AM, Stephen Kelly wrote:
 I haven't had time to investigate fully, but this patch should 'fix' the 
 problem:
[snip]
 I'll investigate later to see if it's the right fix and why.

Great!  I've turned that patch into this commit:

 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de9d4a63

See commit message for an explanation that makes sense to me.

Since these generator expressions are constructed and evaluated
internally to CMake and never exposed it should be easy to
adjust how this works in the future.  Therefore I'm going to
take this as the fix for 2.8.11-rc4 if it is clean on the test
dashboard tonight.

When you have time to investigate in more detail, please
extend this topic with a test case covering

 target_link_libraries(B debug A)

where A is a target instead of an external library name.
Amazingly/apparently we do not have this in the test suite yet.

Thanks,
-Brad
--

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] 2.8.11-rc3 generator expression error

2013-04-25 Thread Stephen Kelly
Brad King wrote:

 On 04/25/2013 03:34 AM, Stephen Kelly wrote:
 I haven't had time to investigate fully, but this patch should 'fix' the
 problem:
 [snip]
 I'll investigate later to see if it's the right fix and why.
 
 Great!  I've turned that patch into this commit:
 
  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de9d4a63
 
 See commit message for an explanation that makes sense to me.

The commit message is correct, but it's not the whole story. We also need to 
validate the it-Value as a target name acceptable to TARGET_PROPERTY.

I've pushed the fix-multi-config-tll-include-dirs branch to my clone.

Thanks,

Steve.

--

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] 2.8.11-rc3 generator expression error

2013-04-25 Thread Paul Smith
On Thu, 2013-04-25 at 17:02 +0200, Stephen Kelly wrote:
 I've pushed the fix-multi-config-tll-include-dirs branch to my clone.

Thanks for your efforts on this guys.  I've backed up to 2.8.10.2 with
the two patches cherry-picked via git for the generate.stamp issue.  So
far I haven't seen that problem recur.  I'll let you know if I see it
again.


I'm willing to try out rc4 with this new generator issue fixed, when
it's available.

Cheers!

--

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] Can't get CTEST_CUSTOM_ERROR_MATCH to work with CTest launchers

2013-04-25 Thread Jean-Christophe Fillion-Robin
Hi Nils,

Since CTEST_USE_LAUNCHERS is ignored when used with generator different
from Make or Ninja  [1], it seems strange that it impacts your windows
build. Which generator are you using ?

Hth
Jc

[1]
https://github.com/Kitware/CMake/blob/master/Modules/CTestUseLaunchers.cmake#L38-40


On Thu, Apr 25, 2013 at 4:44 AM, Nils Gladitz glad...@sci-vis.de wrote:

 One list entry in my CTEST_CUSTOM_ERROR_MATCH is FAILED:  (in my
 CTestCustom.cmake.in which is used to generate CTestCustom.cmake in the
 build directory).

 With CTEST_USE_LAUNCHERS enabled this does not seem to match errors from
 custom commands e.g.:
 FAILED: cmd.exe /c  [...]

 On my CDash installation I see 0 build errors.

 When I disable CTEST_USE_LAUNCHERS the error shows up on the dashboard and
 the FAILED:  line is highlighted indicating that a match has been made.

 Is this by design (e.g. not implemented for launchers) or may I be missing
 something?
 Is there e.g. extra work required for CTEST_CUSTOM_ERROR_MATCH to reach
 the launcher?

 Nils

 --
 Nils Gladitz, B.Sc.
 DICOM, Konnektivität und Entwicklung

 Scivis wissenschaftliche Bildverarbeitung GmbH
 Bertha-von-Suttner-Str. 5
 D-37085 Göttingen
 GERMANY
 Handelsregister Nr. / Trade Register No. B3100 Göttingen
 Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland

 Tel: 0049 (0)551 634181-28
 E-Mail: glad...@scivis.de
 Web: www.scivis.de

 --

 Powered by www.kitware.com

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

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

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




-- 
+1 919 869 8849
--

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] Details on MSVS Win64 LNK1112 static library link (archiver/librarian) issue

2013-04-25 Thread Andreas Mohr
Hi,

I've added a new note to
0011240: VS 2010 Win64 does not correctly set /MACHINE:x64 in the solution 
project files
  http://public.kitware.com/Bug/view.php?id=11240

(e.g. zlib Win64 is a prominent case of breakage here)

If some of the CMake platform setup wizards would happen to want to
have a look at this case... (some sizeable infrastructure extension
probably required)

Thanks,

Andreas Mohr
--

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] Can't get CTEST_CUSTOM_ERROR_MATCH to work with CTest launchers

2013-04-25 Thread Nils Gladitz

Hey Jean-Christophe,

I currently use CMake 2.8.11-rc3 with the Ninja generator on windows.

Nils

On 25.04.2013 17:30, Jean-Christophe Fillion-Robin wrote:

Hi Nils,

Since CTEST_USE_LAUNCHERS is ignored when used with generator 
different from Make or Ninja  [1], it seems strange that it 
impacts your windows build. Which generator are you using ?


Hth
Jc

[1] 
https://github.com/Kitware/CMake/blob/master/Modules/CTestUseLaunchers.cmake#L38-40



On Thu, Apr 25, 2013 at 4:44 AM, Nils Gladitz glad...@sci-vis.de 
mailto:glad...@sci-vis.de wrote:


One list entry in my CTEST_CUSTOM_ERROR_MATCH is FAILED:  (in my
CTestCustom.cmake.in http://CTestCustom.cmake.in which is used
to generate CTestCustom.cmake in the build directory).

With CTEST_USE_LAUNCHERS enabled this does not seem to match
errors from custom commands e.g.:
FAILED: cmd.exe /c  [...]

On my CDash installation I see 0 build errors.

When I disable CTEST_USE_LAUNCHERS the error shows up on the
dashboard and the FAILED:  line is highlighted indicating that a
match has been made.

Is this by design (e.g. not implemented for launchers) or may I be
missing something?
Is there e.g. extra work required for CTEST_CUSTOM_ERROR_MATCH to
reach the launcher?

Nils

-- 
Nils Gladitz, B.Sc.

DICOM, Konnektivität und Entwicklung

Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
GERMANY
Handelsregister Nr. / Trade Register No. B3100 Göttingen
Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland

Tel: 0049 (0)551 634181-28
E-Mail: glad...@scivis.de mailto:glad...@scivis.de
Web: www.scivis.de http://www.scivis.de

--

Powered by www.kitware.com http://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




--
+1 919 869 8849


--

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] Can't get CTEST_CUSTOM_ERROR_MATCH to work with CTest launchers

2013-04-25 Thread Jean-Christophe Fillion-Robin
This is probably caused by commit 965358fcf [1]

Can the problem be reproduced using Ninja on Unix platform ?

[1]
https://github.com/Kitware/CMake/commit/965358fcf64cf1a3693bcdd66f723729e0614ef6


On Thu, Apr 25, 2013 at 12:41 PM, Nils Gladitz glad...@sci-vis.de wrote:

  Hey Jean-Christophe,

 I currently use CMake 2.8.11-rc3 with the Ninja generator on windows.

 Nils


 On 25.04.2013 17:30, Jean-Christophe Fillion-Robin wrote:

 Hi Nils,

  Since CTEST_USE_LAUNCHERS is ignored when used with generator different
 from Make or Ninja  [1], it seems strange that it impacts your windows
 build. Which generator are you using ?

  Hth
 Jc

  [1]
 https://github.com/Kitware/CMake/blob/master/Modules/CTestUseLaunchers.cmake#L38-40


 On Thu, Apr 25, 2013 at 4:44 AM, Nils Gladitz glad...@sci-vis.de wrote:

 One list entry in my CTEST_CUSTOM_ERROR_MATCH is FAILED:  (in my
 CTestCustom.cmake.in which is used to generate CTestCustom.cmake in the
 build directory).

 With CTEST_USE_LAUNCHERS enabled this does not seem to match errors from
 custom commands e.g.:
 FAILED: cmd.exe /c  [...]

 On my CDash installation I see 0 build errors.

 When I disable CTEST_USE_LAUNCHERS the error shows up on the dashboard
 and the FAILED:  line is highlighted indicating that a match has been
 made.

 Is this by design (e.g. not implemented for launchers) or may I be
 missing something?
 Is there e.g. extra work required for CTEST_CUSTOM_ERROR_MATCH to reach
 the launcher?

 Nils

 --
 Nils Gladitz, B.Sc.
 DICOM, Konnektivität und Entwicklung

 Scivis wissenschaftliche Bildverarbeitung GmbH
 Bertha-von-Suttner-Str. 5
 D-37085 Göttingen
 GERMANY
 Handelsregister Nr. / Trade Register No. B3100 Göttingen
 Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe Engeland

 Tel: 0049 (0)551 634181-28
 E-Mail: glad...@scivis.de
 Web: www.scivis.de

 --

 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




  --
 +1 919 869 8849





-- 
+1 919 869 8849
--

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] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

2013-04-25 Thread Alexander Neundorf
On Thursday 25 April 2013, Matthias Kretz wrote:
 On Thursday 25 April 2013 09:46:03 Bill Hoffman wrote:
  On 4/25/2013 9:15 AM, Matthias Kretz wrote:
   I have several checks in my project that make cmake error out with
   FATAL_ERROR. This is submitted as error to the dashboard. In reality it
   would be an error if this error would not appear - and it is the
   expected result if cmake errors out. Is there a possiblity to invert
   the result of the configure step for certain system setups?
   
   Alternatively I'd skip the CTEST_CONFIGURE call in the ctest script and
   just submit Notes that elaborate on the abort. But that doesn't show up
   on the dashboard at all.
   
   Any ideas?
  
  Is this for an individual test?  If so, you can use the regex matching
  instead of return code to determine pass fail.  Would that work?
 
 I'm not sure we're talking about the same thing. I'm talking about
 ctest_configure - i.e. before build or tests. IIUC you're talking about
 regex matching at ctest_test?

so the good result is if the configure step of your project fails ?

Alex
--

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 script profiler

2013-04-25 Thread Alexander Neundorf
On Wednesday 24 April 2013, Bill Hoffman wrote:
...
  Without measuring anything, there is something else I thought about:
  there are now a bunch of useful, quite complex macros coming with cmake,
  which are used quite often: e.g. ExternalProject,
  cmake_parse_arguments(),
  find_package_handle_standard_args().
  Every find-module or every macro which wants to use them, needs to
  include() them. I haven't measured anything, but maybe reading and
  parsing those relatively big files multiple times also consumes some
  time.
  This could be stripped off if cmake would include some modules by
  default, so that as a user I could simply use them like built-in
  commands, without the need to include() them again.
 
 I am pretty sure we cache the read of an include, so multiple includes
 of the same file should not be that expensive.   

I had a quick look.
cmIncludeCommand calls cmMakefile::ReadListFile().
This then first tries to find the file, and then creates a variable  
cmListFile named cacheFile, and calls cacheFile.ParseFile().
This class is contained in cmListFileCache.h/cxx, which OTOH does not contain 
a class named cmListFileCache.
I don't see any caching going on.
There is a variable ModifiedTime set, but never used.
strace on a example file which include()s three times the same file in a row 
also shows that the file is read 3 times.

Seems it was indeed removed in 2006:
commit 4259971961aff5e6423eb72a4fad8acf7af79653
Author: Andy Cedilnik andy.cedil...@kitware.com
Date:   Tue Feb 7 08:49:42 2006 -0500

ENH: Since list file cache does not make much sense any more (because of 
proper list file parsing), and it actually adds unnecessary complications and 
make ctest scripting not work, take it out

And added by you 5 years before :-)

commit 5edd7673e1c7182c748584839ab1dec9712150b3
Author: Bill Hoffman bill.hoff...@kitware.com
Date:   Tue Aug 28 18:28:31 2001 -0400

ENH: add caching for the input CMakeList.txt files, 2X speed up


...
  Inside cmake, arguments are handed over quite often as const char*, and
  then converted again to std::string. Everytime this is done the end of
  the string has to be searched, memory allocated and copied. Again, I
  haven't measured (but I can remember vaguely from some profiling a few
  years ago), maybe things would be faster if in more places const
  std::string would be used internally, this would get rid of quite some
  strlen() calls.
 
 I don' think this is true.  In fact, in the ninja generator it is
 spending the bulk of its time creating and destroying strings and it
 uses std:string much more frequently than the rest of cmake.   Again,
 this would require careful profiling before it could be determined if
 this would help or not.

Interesting. Yes, this would need profiling, as I said, I was just guessing.
Maybe it's those functions which return a std::string ?
In theory those should result in two strings, first the temporary one is 
created, and then this is copied into the target one.
Creating a std::string from a std::string should be faster than creating one 
from a char*.
I just noticed that the Ninja generator files don't follow the CMake style of 
indenting curly braces in relatively big parts, more a KR style.


Alex
--

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] Can't get CTEST_CUSTOM_ERROR_MATCH to work with CTest launchers

2013-04-25 Thread Nils Gladitz
I was able to reproduce the problem with Ninja on Ubuntu and CMake 
2.8.11-rc2.


I set up a test project for which I set CTEST_CUSTOM_ERROR_MATCH to 
FooBar.


It has three custom commands with different outputs and exit codes:

CustomCommand1: this is a FooBar message (exit success)
CustomCommand2: this is a fatal error (exit failure)
CustomCommand3: this is a FooBar fatal error (exit failure)

These are the results that I got (numbers in braces indicate which 
custom commands produce output visible on CDash):


Ninja (Launchers enabled): 0 Build Errors
Ninja (Launchers disabled): 4 Build Errors (1, 2, 3)

Unix Makefiles (Launchers enabled): 2 Build Errors (2, 3)
Unix Makefiles (Launchers disabled): 4 Build Errors (1, 2, 3)

For Unix Makefiles this seems to work better though not quite as I 
expected either.
(I expected CustomCommand1 to trigger an error even though the exit code 
is 0 due to it having FooBar in the output).


But if this is by design it would be nice to have at least the commands 
with failed exit status show up with Ninja like they do with Makefiles.


Hope this helps to diagnose the problem.

Nils

On 04/25/2013 07:04 PM, Jean-Christophe Fillion-Robin wrote:

This is probably caused by commit 965358fcf [1]

Can the problem be reproduced using Ninja on Unix platform ?

[1] 
https://github.com/Kitware/CMake/commit/965358fcf64cf1a3693bcdd66f723729e0614ef6



On Thu, Apr 25, 2013 at 12:41 PM, Nils Gladitz glad...@sci-vis.de 
mailto:glad...@sci-vis.de wrote:


Hey Jean-Christophe,

I currently use CMake 2.8.11-rc3 with the Ninja generator on windows.

Nils


On 25.04.2013 17 tel:25.04.2013%2017:30, Jean-Christophe
Fillion-Robin wrote:

Hi Nils,

Since CTEST_USE_LAUNCHERS is ignored when used with generator
different from Make or Ninja  [1], it seems strange that it
impacts your windows build. Which generator are you using ?

Hth
Jc

[1]

https://github.com/Kitware/CMake/blob/master/Modules/CTestUseLaunchers.cmake#L38-40


On Thu, Apr 25, 2013 at 4:44 AM, Nils Gladitz glad...@sci-vis.de
mailto:glad...@sci-vis.de wrote:

One list entry in my CTEST_CUSTOM_ERROR_MATCH is FAILED: 
(in my CTestCustom.cmake.in http://CTestCustom.cmake.in
which is used to generate CTestCustom.cmake in the build
directory).

With CTEST_USE_LAUNCHERS enabled this does not seem to match
errors from custom commands e.g.:
FAILED: cmd.exe /c  [...]

On my CDash installation I see 0 build errors.

When I disable CTEST_USE_LAUNCHERS the error shows up on the
dashboard and the FAILED:  line is highlighted indicating
that a match has been made.

Is this by design (e.g. not implemented for launchers) or may
I be missing something?
Is there e.g. extra work required for
CTEST_CUSTOM_ERROR_MATCH to reach the launcher?

Nils

-- 
Nils Gladitz, B.Sc.

DICOM, Konnektivität und Entwicklung

Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
GERMANY
Handelsregister Nr. / Trade Register No. B3100 Göttingen
Geschäftsführer / Managing Directors Dr. Gernot Ebel, Dr. Uwe
Engeland

Tel: 0049 (0)551 634181-28
E-Mail: glad...@scivis.de mailto:glad...@scivis.de
Web: www.scivis.de http://www.scivis.de

--

Powered by www.kitware.com http://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




-- 
+1 919 869 8849 tel:%2B1%20919%20869%208849





--
+1 919 869 8849


--

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 script profiler

2013-04-25 Thread Kyle Heath
Volo,

Thanks for sharing your cmake-profile-stats tool... I found it very useful.
 With this tool and about ~10 minutes of tweaking, my configure phase runs
~4x faster!

@Bill: I hope similar profiling features will be included in a future
release!

Cheers,
Kyle

PS: I added a small extension to your script to print a cumulative summary
of time spent in each function.  This helped me find the hotspots quickly.
 I posted the modified script here:
https://code.google.com/p/cmake-profile-stats/issues/detail?id=1



On Wed, Apr 24, 2013 at 9:13 PM, Volo Zyko volo.z...@gmail.com wrote:

 We have executables and libraries and a lot of custom targets (the project
 is organized so that we export headers during the build - not the best idea
 in the world). However, I finished (more or less) the script for building
 time stats from the cmake's trace and we (with my colleague) found the
 slowest part. In our cmake scripts we have a bunch of sub-projects which
 produce libraries and also we have an utility function with which we define
 dependencies between those sub-projects. Then we define executables and
 build a list of libraries in a right order (from more dependent to less
 dependent) using sub-project's dependencies. This list is necessary for
 linking the executables. So, it appears that the slowest part is the
 function that builds the list of libraries. Basically there is nothing
 wrong with that cmake function, it just intensively works with strings. :(

 And here is where I put my script:
 https://code.google.com/p/cmake-profile-stats/ Comments are welcome.

 Also it looks like there are few bugs in the trace functionality of cmake;
 especially how callstack changes when cmake process foreach and if/else
 calls. I just didn't investigate them and I cannot provide more details.
 Sorry.

 --
  Volo Zyko

 On Wed, Apr 24, 2013 at 10:14 PM, Bill Hoffman 
 bill.hoff...@kitware.comwrote:

 On 4/24/2013 3:07 PM, Volo Zyko wrote:

 Hi,

 We use Makefiles on Linux and MacOS. Windows is not our target platform.
 From what we see Linux is the fastest. We made few attempts of building
 our project on Windows in VS but it was very-very slow and definitely
 cmake generates too many project files for VS. For us it was 500+
 projects in a workspace which is too much for Visual Studio. :(

 Chances are you have too many high level targets in your project.  What
 types of targets do you have?  Are they all executables and libraries or
 are you using custom targets to do something?   That might be a source of
 your performance issues as well.

 -Bill


 --
 Bill Hoffman
 Kitware, Inc.
 28 Corporate Drive
 Clifton Park, NY 12065
 bill.hoff...@kitware.com
 http://www.kitware.com
 518 881-4905 (Direct)
 518 371-3971 x105
 Fax (518) 371-4573

 --

 Powered by www.kitware.com

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

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

 Follow this link to subscribe/unsubscribe:
 http://www.cmake.org/mailman/**listinfo/cmakehttp://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

--

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] Problem with CMAKE_AUTOMOC files not being regenerated or cleaned

2013-04-25 Thread Alexander Neundorf
On Thursday 25 April 2013, Glenn Coombs wrote:
 Hi,
 
 I have a Qt4 program that I'm working on and ran into an issue yesterday
 with the automoc cpp files.  I had added a new slot and connected a
 comboxbox currentIndexChanged signal to it but when I ran the program I
 could see messages on stdout complaining that my slot didn't exist.  I
 tracked the problem down to the fact that the moc_ctrlBasic.cpp file was
 not being regenerated.  If I look in my cmake build directory I currently
 have 8 moc cpp files:
 
 ./moc_ctrlBasic.cpp
 ./moc_ctrlmenu.cpp
 ./moc_infoWin.cpp
 ./moc_qglDisplay.cpp
 ./moc_qglMultiWindow.cpp
 ./moc_qglWindow.cpp
 ./moc_videoGeneric.cpp
 ./yuv_player_automoc.cpp
 
 I am using CMake 2.8.10.1 with Visual Studio 11 and when I do a clean
 solution these 8 moc cpp files are not deleted.  

That's ok so far.
automoc should create a file yuv_player_automoc.cpp, and this file should be 
removed when you clean.
Is that the case ?
This missing file should then trigger a rerun of automoc.

Alex
--

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] Date issue on www.cmake.org

2013-04-25 Thread Hendrik Sattler
Am Mittwoch, 24. April 2013, 17:53:28 schrieb David Cole:
 Sure, but this is in web page text only meant to be read by human beings,
 not in some parse-able data that’s actually important for anything.

The confusion probably comes from the fact, that U.S. date format is usually 
separated by '/' and not by '.', so 7/9/2012 instead of 7.9.2012. If it's 
meant for humans, writing July 9, 2012 usually also solves that problem.

HS
--

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 and MPIF90

2013-04-25 Thread Pettey . Lucas
Hello,

I am getting errors when I execute a simple hello World mpi program compiled 
using cmake.

I could not get the program to compile using various forms of FIND_PACKAGE(MPI 
REQUIRED), INCLUDE_DIRECTORIES(${MPI_INCLUDE_PATH}), 
TARGET_LINK_LIBRARIES(executable ${MPI_LIBRARIES}) and filling in flags 
manually for anything missing.

I then tried FC=mpif90 and the program compiled, but gave me upon execution a 
series of errors starting with:

[[INVALID],INVALID] ORTE_ERROR_LOG: Not found in file runtime/orte_init.c at 
line 121

The rest indicate that MPI is not being initialized properly.

As a sanity check, I compiled using mpif90 in the command line and everything 
worked fine.

Any ideas or links to documentation? I tried searching the wiki, but it is not 
very straightforward.

Thanks,
Lucas

This electronic message transmission and any attachments that accompany it 
contain information from DRC® (Dynamics Research Corporation) or its 
subsidiaries, or the intended recipient, which is privileged, proprietary, 
business confidential, or otherwise protected from disclosure and is the 
exclusive property of DRC and/or the intended recipient. The information in 
this email is solely intended for the use of the individual or entity that is 
the intended recipient. If you are not the intended recipient, any use, 
dissemination, distribution, retention, or copying of this communication, 
attachments, or substance is prohibited. If you have received this electronic 
transmission in error, please immediately reply to the author via email that 
you received the message by mistake and also promptly and permanently delete 
this message and all copies of this email and any attachments. We thank you for 
your assistance and apologize for any inconvenience.
--

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-commits] CMake branch, next, updated. v2.8.10.2-2827-g0492593

2013-04-25 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  0492593faa913c4aa36b6cce39c40d7c46104c0c (commit)
   via  f9eee7f1833856f690b4a8ef5f5aa44d9ccb8114 (commit)
   via  90bd16419343ada9f026ce8387fafff9c3546a10 (commit)
   via  2baf851c34357cbb752bb91b99b835d3847b23a1 (commit)
   via  e55b8ce4a4f5d6a935fe82d600637c79e64e8cbd (commit)
   via  d37fe5bc5b328fae6b03af033ba69651f045df80 (commit)
   via  50e96802d2ad81f69d72dc87de80eee74d7a8dc9 (commit)
   via  e6c3595fde100b62f021ddb253b81fe3ecc9328b (commit)
  from  4cf05ba7c48f69beff60ee682d0cd52008e65e32 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0492593faa913c4aa36b6cce39c40d7c46104c0c
commit 0492593faa913c4aa36b6cce39c40d7c46104c0c
Merge: 4cf05ba f9eee7f
Author: Brad King brad.k...@kitware.com
AuthorDate: Thu Apr 25 09:19:51 2013 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Apr 25 09:19:51 2013 -0400

Merge topic 'WindowsPaths-MinGW-cross-compile-only' into next

f9eee7f Windows: Search '/' prefix only when cross compiling (#10994)
90bd164 CMake Nightly Date Stamp
2baf851 CMake Nightly Date Stamp
e55b8ce CMake Nightly Date Stamp
d37fe5b CMake Nightly Date Stamp
50e9680 CMake Nightly Date Stamp
e6c3595 CMake Nightly Date Stamp


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f9eee7f1833856f690b4a8ef5f5aa44d9ccb8114
commit f9eee7f1833856f690b4a8ef5f5aa44d9ccb8114
Author: Brad King brad.k...@kitware.com
AuthorDate: Thu Apr 25 09:07:45 2013 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Thu Apr 25 09:07:45 2013 -0400

Windows: Search '/' prefix only when cross compiling (#10994)

Commit dac78148 (...makes the mingw cross compiler work out of the
box..., 2007-08-02) added to CMAKE_SYSTEM_PROGRAM_PATH and
CMAKE_SYSTEM_LIBRARY_PATH paths like /bin and /lib with no Windows
drive letter so that cross-compiling to Windows from Linux would search
these paths under CMAKE_FIND_ROOT_PATH.  Later commit 2a782880 (...use
CMAKE_SYSTEM_PREFIX_PATH when possible, 2008-01-16) generalized this
approach by instead adding / to CMAKE_SYSTEM_PREFIX_PATH.

Both commits assumed that the paths would never match anything on
Windows hosts without a drive letter.  However, Windows evaluates these
paths relative to the current working drive letter so find_* commands
may report paths like /lib/... when paths like c:/lib/... exist on
what happens to be current drive.  Such drive-less paths are not
reliable when the working drive changes, so we should not use them.

Fix WindowsPaths.cmake to add '/' to CMAKE_SYSTEM_PREFIX_PATH only when
cross-compiling to Windows from a non-Windows host.  This will avoid
searching and finding local paths without a drive letter on Windows.

diff --git a/Modules/Platform/WindowsPaths.cmake 
b/Modules/Platform/WindowsPaths.cmake
index bd31da0..fc921d7 100644
--- a/Modules/Platform/WindowsPaths.cmake
+++ b/Modules/Platform/WindowsPaths.cmake
@@ -77,10 +77,12 @@ list(APPEND CMAKE_SYSTEM_PREFIX_PATH 
${_CMAKE_INSTALL_DIR})
 list(APPEND CMAKE_SYSTEM_PREFIX_PATH
   # Project install destination.
   ${CMAKE_INSTALL_PREFIX}
+  )
 
+if(CMAKE_CROSSCOMPILING AND NOT CMAKE_HOST_SYSTEM_NAME MATCHES Windows)
   # MinGW (useful when cross compiling from linux with CMAKE_FIND_ROOT_PATH 
set)
-  /
-  )
+  list(APPEND CMAKE_SYSTEM_PREFIX_PATH /)
+endif()
 
 list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
   )

---

Summary of changes:
 Modules/Platform/WindowsPaths.cmake |6 --
 Source/CMakeVersion.cmake   |2 +-
 2 files changed, 5 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2830-g6ceeff2

2013-04-25 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  6ceeff297bd1b06a6b4141fdccdd76447de82a0f (commit)
   via  de9d4a63ca9af8f2a06c79e02d3e6ffb5320e01c (commit)
   via  78185f598c152b1dbce632e953874ce8132c5fe9 (commit)
  from  0492593faa913c4aa36b6cce39c40d7c46104c0c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6ceeff297bd1b06a6b4141fdccdd76447de82a0f
commit 6ceeff297bd1b06a6b4141fdccdd76447de82a0f
Merge: 0492593 de9d4a6
Author: Brad King brad.k...@kitware.com
AuthorDate: Thu Apr 25 10:33:21 2013 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Apr 25 10:33:21 2013 -0400

Merge topic 'fix-per-config-tll-include-dirs' into next

de9d4a6 Fix include dir propagation from conditionally linked targets
78185f5 CMake Nightly Date Stamp


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=de9d4a63ca9af8f2a06c79e02d3e6ffb5320e01c
commit de9d4a63ca9af8f2a06c79e02d3e6ffb5320e01c
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Thu Apr 25 09:43:42 2013 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Thu Apr 25 09:58:15 2013 -0400

Fix include dir propagation from conditionally linked targets

Code like

 target_link_libraries(B debug A)

generates usage requirement references such as $$CONFIG:DEBUG:A.
When cmTarget::GetIncludeDirectories uses such references it generates
expressions like:

 $TARGET_PROPERTY:$$CONFIG:DEBUG:A,INTERFACE_INCLUDE_DIRECTORIES

When the conditions are false such references evaluate as an empty
string and the expression fails with an error such as:

 $TARGET_PROPERTY:tgt,prop expression requires a non-empty target name.

Fix this by teaching cmTarget::GetIncludeDirectories to wrap the above
expression inside a conditional:

 $$BOOL:$$CONFIG:DEBUG:A:...

so that $TARGET_PROPERTY:... will not be evaluated with an empty
target.

diff --git a/Source/cmTarget.cxx b/Source/cmTarget.cxx
index 66c22b1..3d0d019 100644
--- a/Source/cmTarget.cxx
+++ b/Source/cmTarget.cxx
@@ -2947,8 +2947,8 @@ std::vectorstd::string 
cmTarget::GetIncludeDirectories(const char *config)
   }
   cmGeneratorExpression ge(it-Backtrace);
   cmsys::auto_ptrcmCompiledGeneratorExpression cge = ge.Parse(
-  $TARGET_PROPERTY: +
-  it-Value + ,INTERFACE_INCLUDE_DIRECTORIES);
+$$BOOL:+it-Value+:
+  $TARGET_PROPERTY:+it-Value+,INTERFACE_INCLUDE_DIRECTORIES);
 
   this-Internal-CachedLinkInterfaceIncludeDirectoriesEntries.push_back(
 new cmTargetInternals::IncludeDirectoriesEntry(cge,

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 Source/cmTarget.cxx   |4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits


[Cmake-commits] CMake branch, master, updated. v2.8.10.2-1006-gc8b3472

2013-04-25 Thread Kitware Robot
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  c8b34729d90366a7dfee7b0d4a3df1ebfd7cdeab (commit)
  from  78185f598c152b1dbce632e953874ce8132c5fe9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c8b34729d90366a7dfee7b0d4a3df1ebfd7cdeab
commit c8b34729d90366a7dfee7b0d4a3df1ebfd7cdeab
Author: Kitware Robot kwro...@kitware.com
AuthorDate: Fri Apr 26 00:01:09 2013 -0400
Commit: Kitware Robot kwro...@kitware.com
CommitDate: Fri Apr 26 00:01:09 2013 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 8ded30f..317cc73 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
 set(CMake_VERSION_MAJOR 2)
 set(CMake_VERSION_MINOR 8)
 set(CMake_VERSION_PATCH 10)
-set(CMake_VERSION_TWEAK 20130425)
+set(CMake_VERSION_TWEAK 20130426)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits