Re: [CMake] [cmake-developers] CLang error when building iOS bundle

[NoRulez]

I don't know why I get this error, but after I link against missing required 
frameworks (OpenGLES, AssetsLibrary and QuartzCore) the error is gone.

Regards
Roman

> Am 11.05.2016 um 22:48 schrieb Gregor Jasny via CMake :
> 
> Hello,
> 
>> On 11/05/16 21:22, Roman Wüger wrote:
>> I got the following error when linking the iOS bundle:
>> 
>> clang: error: cannot specify -o when generating multiple output files
>> 
>> I didn’t found anything about the error in the internet, so maybe someone
>> has already solved such error?
>> 
>> Does any one have a hint what could be wrong?
> 
> I cannot see any suspicious things, either (besides that -arch armv7 is
> listed twice). I would suggest you create a new user on the machine and
> try there. Or you could remove ~/Library/Developer/Xcode/DerivedData first.
> 
> Thanks,
> Gregor
> -- 
> 
> 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
-- 

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] CheckIncludeFiles doesn't find header files

[NoRulez]

Hello,

I hope someone could help me please.

I've the following situation that when I run CMake from the command line, all 
is working as expected and CheckIncludeFiles find the header files.

However, when I run the configure and build steps from within a CTestScript the 
CheckIncludeFiles doesn't find anything.

It doesn't matter if I set specified CMake variables of not. 

The strange thing is that when I use the 10.7 sdk than it works in both 
situations.
When I use the 10.5 sdk than it works only if I use CMake on the command line 
directly.

I use CMake 3.0.2 on Mac OS 10.10.1

Did someone have some tips or tricks to get it working.

Much thanks in advance

Best Regards

-- 

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] CMP0026 - Disallow use of the LOCATION target property

[NoRulez]

Hi,

We had that problem too.
Look at the great example from Stephen to my question.

His example was great and helped us a lot.

Best Regards


> Am 06.02.2015 um 19:18 schrieb Stephen Kelly :
> 
> Jifeng ZHANG wrote:
> 
>> Hi,
>> 
>> I have a question of policy CMP0026. Our project currently is on CMake
>> 2 and we are planning to move to CMake 3.
> 
> Lot's of questions on that lately. Someone opened the floodgates it seems 
> :).
> 
>> When we run CMake3.1.1, we get get a few warnings due to the policy
>> CMP0026, "Disallow use of the LOCATION target property". Even though
>> with those warnings, our cmake scripts still work fine and we are
>> getting the property correctly.
> 
>> So my question is, will the support of this kind of usage be dropped
>> in the future releases?
> 
> Yes. That is the purpose of the policy. Attempting to read the LOCATION will 
> eventually be an error. That is not going to happen before CMake 4.0 though.
> 
>> If we migrate away from get_target_property, "$ generator
>> expression" is suggested from CMake3.1.1's documentation. So to get
>> the LOCATION of ${TEST_PROJECT}, I can use:
>> set (TEST_PATH $)
> 
> This won't work. You need to use the generator expression instead of a cmake 
> variable. You use the generator expression in place of ${TEST_PATH} in 
> add_custom_command or wherever you use it.
> 
> Thanks,
> 
> Steve.
> 
> 
> -- 
> 
> 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
-- 

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] Workaround for CMP0026

[NoRulez]

Thank you for your help.

I think that for the replacement there is some missing documentation 
outstanding, because i didn't find the "TYPE" attribute in the "file" function 
for example.

Or examples for the CMP0026 policy like in the CMP0043 documentation.

Nevertheless, I also need to change the filename from "dirInstallScript.cmake" 
to "dirInstallScript$.cmake" in the "file(GENERATE" statement and use 
the hard coded filename "dirInstallScriptRelease.cmake" in the "install(SCRIPT" 
statement, because if i didn't so, I get several warnings/errors when 
generating with Visual Studio generator.

Is this really the right way?

Best Regards


> Am 04.02.2015 um 20:24 schrieb Stephen Kelly :
> 
> NoRulez wrote:
> 
>> Hello,
>> 
>> currently I'm updating my CMake scripts to use newer features and/or to
>> solve some old workarounds.
> 
> I think you're looking for 
> 
> 
>  file(GENERATE
>OUTPUT "${CMAKE_CURRENT_BINARY_DIR}/dirInstallScript.cmake"
>CONTENT   " 
>  if (CMAKE_INSTALL_CONFIG_NAME STREQUAL RELEASE)
>file(INSTALL DESTINATION
>  \"\${CMAKE_INSTALL_PREFIX}/share/myproj\" TYPE DIRECTORY
>  FILES \"$/MyDir\")
>  endif()")
> 
>  install(SCRIPT "${CMAKE_CURRENT_BINARY_DIR}/dirInstallScript.cmake")
> 
> 
> Thanks,
> 
> Steve.
> 
> 
> -- 
> 
> 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
-- 

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] Workaround for CMP0026

[NoRulez]

Hello,

currently I'm updating my CMake scripts to use newer features and/or to solve 
some old workarounds.

I have the following code:
  get_target_property(${PROJECT_NAME}OutputDirectory ${PROJECT_NAME} 
LOCATION_RELEASE)
get_filename_component(${PROJECT_NAME}OutputDirectory 
${${PROJECT_NAME}OutputDirectory} PATH)

install(DIRECTORY "${${PROJECT_NAME}OutputDirectory}/MyDir"
DESTINATION share/myproj)

In the description for porting such code is to use "file(GENERATE...)"

If I use this, how can I then read the value?

The following gives me the error that the file doesn't exist (in release build):

file(GENERATE OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/MyPath$.txt CONTENT 
"$")

file(READ ${CMAKE_CURRENT_BINARY_DIR}/MyPathRelease.txt MYCONTENT)

install(DIRECTORY ${MYCONTENT}/MyDir DESTINATION share/myproj)

Without the "file(read" and install, the files are created.

So, how can i use such information for the install stuff?

I already tried 
"set_source_file_properties(${CMAKE_CURRENT_BINARY_DIR}/MyPath$.txt 
PROPERTIES GENERATED TRUE)" but that doesn't work either.

Thanks in advance
Best Regards

-- 

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] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

Thank you for the information.


> Am 03.02.2015 um 20:34 schrieb Robert Maynard :
> 
> This is a regression and will be fixed in the next release.
> 
> install: Fix regression in default configuration selection
> http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dea42d92
> 
>> On Mon, Feb 2, 2015 at 9:54 AM, NoRulez  wrote:
>> Hi,
>> 
>> I think I found the problem:
>> In the file cmLocalGenerator.cxx the pointer is always true since 3.1.0, 
>> which was a const char* in 3.0.2. and now it could point to an empty const 
>> std::string, but the pointer is still valid
>> 
>> The if statement is:
>> if(!default_config)
>> 
>> And should be (line 411):
>> if(!default_config || (default_config && strlen(default_config) == 0))
>> 
>> Best Regards
>> 
>> 
>>> Am 23.01.2015 um 09:15 schrieb NoRulez :
>>> 
>>> Hi,
>>> 
>>> i've tested it also with 3.1.1 and the failure behaves the same.
>>> 
>>> Best Regards
>>> 
>>> 
>>>> Am 21.01.2015 um 10:00 schrieb NoRulez :
>>>> 
>>>> Hi,
>>>> 
>>>> it should also not work when you build a test project in release mode and 
>>>> then in the build directory type "cpack -G ZIP" for example. (Without the 
>>>> -C option)
>>>> 
>>>> In the CTestScript is also added the -C option to ensure it uses the 
>>>> release mode, but it doesn't work either.
>>>> 
>>>> When you then open the cmake_install.cmake files, you will see that the 
>>>> CMAKE_INSTALL_CONFIG_NAME variable is empty on line 15.
>>>> 
>>>> In CMake 3.0.2 the variable is set with the value "Release".
>>>> 
>>>> Best Regards
>>>> 
>>>> 
>>>>> Am 20.01.2015 um 18:40 schrieb Robert Maynard 
>>>>> :
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I haven't seen this issue but if you have a self-contained and reduced
>>>>> (preferably plain CMake ) test case, I would be happy to run it and
>>>>> verify if this is a regression.
>>>>> 
>>>>>> On Tue, Jan 20, 2015 at 2:37 AM, NoRulez  wrote:
>>>>>> No one?
>>>>>> 
>>>>>> Has something changed between 3.0.2 to 3.1.0 which prevents cpack to 
>>>>>> copy the generated *.exe file to the _CPack_Packages directory? Or did i 
>>>>>> need an additional variable to be set in 3.1.0?
>>>>>> 
>>>>>> Thanks in advance
>>>>>> 
>>>>>> Best Regards
>>>>>> 
>>>>>> 
>>>>>>> Am 16.01.2015 um 12:09 schrieb NoRulez :
>>>>>>> 
>>>>>>> If I switch back to 3.0.2 everything is working like a charm
>>>>>>> 
>>>>>>> Best Regards
>>>>>>> 
>>>>>>>> Am 15.01.2015 um 17:49 schrieb NoRulez :
>>>>>>>> 
>>>>>>>> Hello,
>>>>>>>> 
>>>>>>>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
>>>>>>>> following when cpack is executed in a CTestScript:
>>>>>>>> 
>>>>>>>> error: fixup_bundle: not a valid bundle
>>>>>>>> 
>>>>>>>> The files are ceated, but they are not copied to the _CPack_Packages 
>>>>>>>> folder
>>>>>>>> 
>>>>>>>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is 
>>>>>>>> empty in the cmake_install.cmake files
>>>>>>>> 
>>>>>>>> Any hints?
>>>>>>>> 
>>>>>>>> Best Regards
>>>>>>>> 
>>>>>>>> --
>>>>>>>> 
>>>>>>>> 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

Re: [CMake] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

Hi,

I think I found the problem:
In the file cmLocalGenerator.cxx the pointer is always true since 3.1.0, which 
was a const char* in 3.0.2. and now it could point to an empty const 
std::string, but the pointer is still valid

The if statement is:
if(!default_config)

And should be (line 411):
if(!default_config || (default_config && strlen(default_config) == 0))

Best Regards


> Am 23.01.2015 um 09:15 schrieb NoRulez :
> 
> Hi,
> 
> i've tested it also with 3.1.1 and the failure behaves the same.
> 
> Best Regards
> 
> 
>> Am 21.01.2015 um 10:00 schrieb NoRulez :
>> 
>> Hi,
>> 
>> it should also not work when you build a test project in release mode and 
>> then in the build directory type "cpack -G ZIP" for example. (Without the -C 
>> option)
>> 
>> In the CTestScript is also added the -C option to ensure it uses the release 
>> mode, but it doesn't work either.
>> 
>> When you then open the cmake_install.cmake files, you will see that the 
>> CMAKE_INSTALL_CONFIG_NAME variable is empty on line 15.
>> 
>> In CMake 3.0.2 the variable is set with the value "Release".
>> 
>> Best Regards
>> 
>> 
>>> Am 20.01.2015 um 18:40 schrieb Robert Maynard :
>>> 
>>> Hi,
>>> 
>>> I haven't seen this issue but if you have a self-contained and reduced
>>> (preferably plain CMake ) test case, I would be happy to run it and
>>> verify if this is a regression.
>>> 
>>>> On Tue, Jan 20, 2015 at 2:37 AM, NoRulez  wrote:
>>>> No one?
>>>> 
>>>> Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy 
>>>> the generated *.exe file to the _CPack_Packages directory? Or did i need 
>>>> an additional variable to be set in 3.1.0?
>>>> 
>>>> Thanks in advance
>>>> 
>>>> Best Regards
>>>> 
>>>> 
>>>>> Am 16.01.2015 um 12:09 schrieb NoRulez :
>>>>> 
>>>>> If I switch back to 3.0.2 everything is working like a charm
>>>>> 
>>>>> Best Regards
>>>>> 
>>>>>> Am 15.01.2015 um 17:49 schrieb NoRulez :
>>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
>>>>>> following when cpack is executed in a CTestScript:
>>>>>> 
>>>>>> error: fixup_bundle: not a valid bundle
>>>>>> 
>>>>>> The files are ceated, but they are not copied to the _CPack_Packages 
>>>>>> folder
>>>>>> 
>>>>>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty 
>>>>>> in the cmake_install.cmake files
>>>>>> 
>>>>>> Any hints?
>>>>>> 
>>>>>> Best Regards
>>>>>> 
>>>>>> --
>>>>>> 
>>>>>> 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
>>>>> --
>>>>> 
>>>>> 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
>>&g

Re: [CMake] CMake 3.0.2 check_include_files can't find include files in Mac OS X

[NoRulez]

Hi,

I've already set CMAKE_OSX_SYSROOT to /Developer/SDKs/MacOSX10.7.sdk
And CMAKE_OSX_DEPLOYMENT_TARGET to 10.7

Thanks in advance

Best regards


> Am 02.02.2015 um 06:58 schrieb Braden McDaniel :
> 
>> On Sun, 2015-02-01 at 22:56 +0100, NoRulez wrote:
>> I've my SDK under /Developer/SDKs/MacOSX10.7.sdk.
> 
> You need to set CMAKE_OSX_SYSROOT to that path.
> 
> It's surprising you were able to get very far at all without that;
> perhpas CMAKE_OSX_SYSROOT got set to something else (you definitely
> don't want that).
> 
> -- 
> Braden McDaniel 
> 
> -- 
> 
> 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
-- 

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.2 check_include_files can't find include files in Mac OS X

[NoRulez]

Hello,

I've my SDK under /Developer/SDKs/MacOSX10.7.sdk.

I've tried to set several CMake and environment variables, but 
check_include_files doesn't find anything. (e.g. sys/types.h, sys/stat.h, 
memory.h, ...)

What did I need to define, so that check_include_files find my include files?

The directory which i need to use:
/Developer/SDKs/MacOSX10.7.sdk/usr/include

Already tried CMake variables:
CMAKE_REQUIRED_INCLUDES
CNAKE_INCLUDE_PATH

Already tried environment variables:
USER_HEADER_SEARCH_PATH
HEADER_SEARCH_PATH
INCLUDEPATH
DYLD_LIBRARY_PATH
PATH
CPLUS_INCLUDE_PATH
C_INCLUDE_PATH

Could someone help?

Thanks in advance
-- 

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] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

Hi,

i've tested it also with 3.1.1 and the failure behaves the same.

Best Regards


> Am 21.01.2015 um 10:00 schrieb NoRulez :
> 
> Hi,
> 
> it should also not work when you build a test project in release mode and 
> then in the build directory type "cpack -G ZIP" for example. (Without the -C 
> option)
> 
> In the CTestScript is also added the -C option to ensure it uses the release 
> mode, but it doesn't work either.
> 
> When you then open the cmake_install.cmake files, you will see that the 
> CMAKE_INSTALL_CONFIG_NAME variable is empty on line 15.
> 
> In CMake 3.0.2 the variable is set with the value "Release".
> 
> Best Regards
> 
> 
>> Am 20.01.2015 um 18:40 schrieb Robert Maynard :
>> 
>> Hi,
>> 
>> I haven't seen this issue but if you have a self-contained and reduced
>> (preferably plain CMake ) test case, I would be happy to run it and
>> verify if this is a regression.
>> 
>>> On Tue, Jan 20, 2015 at 2:37 AM, NoRulez  wrote:
>>> No one?
>>> 
>>> Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy 
>>> the generated *.exe file to the _CPack_Packages directory? Or did i need an 
>>> additional variable to be set in 3.1.0?
>>> 
>>> Thanks in advance
>>> 
>>> Best Regards
>>> 
>>> 
>>>> Am 16.01.2015 um 12:09 schrieb NoRulez :
>>>> 
>>>> If I switch back to 3.0.2 everything is working like a charm
>>>> 
>>>> Best Regards
>>>> 
>>>>> Am 15.01.2015 um 17:49 schrieb NoRulez :
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
>>>>> following when cpack is executed in a CTestScript:
>>>>> 
>>>>> error: fixup_bundle: not a valid bundle
>>>>> 
>>>>> The files are ceated, but they are not copied to the _CPack_Packages 
>>>>> folder
>>>>> 
>>>>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty 
>>>>> in the cmake_install.cmake files
>>>>> 
>>>>> Any hints?
>>>>> 
>>>>> Best Regards
>>>>> 
>>>>> --
>>>>> 
>>>>> 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
>>>> --
>>>> 
>>>> 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
>>> --
>>> 
>>> 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/

Re: [CMake] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

Hi,

it should also not work when you build a test project in release mode and then 
in the build directory type "cpack -G ZIP" for example. (Without the -C option)

In the CTestScript is also added the -C option to ensure it uses the release 
mode, but it doesn't work either.

When you then open the cmake_install.cmake files, you will see that the 
CMAKE_INSTALL_CONFIG_NAME variable is empty on line 15.

In CMake 3.0.2 the variable is set with the value "Release".

Best Regards


> Am 20.01.2015 um 18:40 schrieb Robert Maynard :
> 
> Hi,
> 
> I haven't seen this issue but if you have a self-contained and reduced
> (preferably plain CMake ) test case, I would be happy to run it and
> verify if this is a regression.
> 
>> On Tue, Jan 20, 2015 at 2:37 AM, NoRulez  wrote:
>> No one?
>> 
>> Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy 
>> the generated *.exe file to the _CPack_Packages directory? Or did i need an 
>> additional variable to be set in 3.1.0?
>> 
>> Thanks in advance
>> 
>> Best Regards
>> 
>> 
>>> Am 16.01.2015 um 12:09 schrieb NoRulez :
>>> 
>>> If I switch back to 3.0.2 everything is working like a charm
>>> 
>>> Best Regards
>>> 
>>>> Am 15.01.2015 um 17:49 schrieb NoRulez :
>>>> 
>>>> Hello,
>>>> 
>>>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
>>>> following when cpack is executed in a CTestScript:
>>>> 
>>>> error: fixup_bundle: not a valid bundle
>>>> 
>>>> The files are ceated, but they are not copied to the _CPack_Packages folder
>>>> 
>>>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty in 
>>>> the cmake_install.cmake files
>>>> 
>>>> Any hints?
>>>> 
>>>> Best Regards
>>>> 
>>>> --
>>>> 
>>>> 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
>>> --
>>> 
>>> 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
>> --
>> 
>> 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
-- 

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] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

No one?

Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy the 
generated *.exe file to the _CPack_Packages directory? Or did i need an 
additional variable to be set in 3.1.0?

Thanks in advance 

Best Regards


> Am 16.01.2015 um 12:09 schrieb NoRulez :
> 
> If I switch back to 3.0.2 everything is working like a charm
> 
> Best Regards
> 
>> Am 15.01.2015 um 17:49 schrieb NoRulez :
>> 
>> Hello,
>> 
>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
>> following when cpack is executed in a CTestScript:
>> 
>> error: fixup_bundle: not a valid bundle
>> 
>> The files are ceated, but they are not copied to the _CPack_Packages folder
>> 
>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty in 
>> the cmake_install.cmake files
>> 
>> Any hints?
>> 
>> Best Regards
>> 
>> -- 
>> 
>> 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
> -- 
> 
> 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
-- 

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] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

If I switch back to 3.0.2 everything is working like a charm

Best Regards

> Am 15.01.2015 um 17:49 schrieb NoRulez :
> 
> Hello,
> 
> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
> following when cpack is executed in a CTestScript:
> 
> error: fixup_bundle: not a valid bundle
> 
> The files are ceated, but they are not copied to the _CPack_Packages folder
> 
> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty in 
> the cmake_install.cmake files
> 
> Any hints?
> 
> Best Regards
> 
> -- 
> 
> 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
-- 

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] CPack in CMake 3.1.0 doesn't install files

[NoRulez]

Hello,

we have only upgraded to the last release 3.1.0 from 3.0.2 and get the 
following when cpack is executed in a CTestScript:

error: fixup_bundle: not a valid bundle

The files are ceated, but they are not copied to the _CPack_Packages folder

Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty in the 
cmake_install.cmake files

Any hints?

Best Regards

-- 

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] Problems with CMake 3.1.0-rc3 write_compiler_detection_header

[NoRulez]

Not supported in general or only in the rc/final 3.1.0?

Because it would be very helpful for Features which are supported for e.g. in 
VS2010 to VS2014 and more.

Best Regards


> Am 15.12.2014 um 18:49 schrieb Brad King :
> 
>> On 12/15/2014 08:40 AM, NoRulez wrote:
>> I see that only GNU and Clang is currently supported
>> ("set(compilers GNU Clang);")
>> 
>> Is that right and would MSVC be added to the final 3.1.0 version?
> 
> This was a mistake in the documentation that was updated here:
> 
> WCDH: Don't imply that MSVC is supported by the module.
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0db3db41
> 
> MSVC is not supported.  The contributor of the feature does not
> work extensively with MS tools.  Someone else will have to work
> on populating the feature table.
> 
> -Brad
> 
-- 

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] Problems with CMake 3.1.0-rc3 write_compiler_detection_header

[NoRulez]

I see that only GNU and Clang is currently supported ("set(compilers GNU 
Clang);")

Is that right and would MSVC be added to the final 3.1.0 version?

Thanks in advance

Best Regards


> Am 15.12.2014 um 12:34 schrieb NoRulez :
> 
> Hello,
> 
> I tried write_compiler_detection_header as in the example provided with 
> VS2013 but i only get the following message: "Unsupported compiler MSVC"
> 
> Any suggestions?
> 
> Best Regards
> -- 
> 
> 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
-- 

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] Problems with CMake 3.1.0-rc3 write_compiler_detection_header

[NoRulez]

Hello,

I tried write_compiler_detection_header as in the example provided with VS2013 
but i only get the following message: "Unsupported compiler MSVC"

Any suggestions?

Best Regards
-- 

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] Green Hills Generator #0014992

[NoRulez]

No one?

The patch is already working.


> Am 12.11.2014 um 09:45 schrieb NoRulez :
> 
> Hi,
> 
> is it possible to get the patch for the green hills generator into CMake 3.1
> 
> Thanks in advance 
> 
> Best Regards
> 
> -- 
> 
> 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
-- 

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] Green Hills Generator #0014992

[NoRulez]

Hi,

is it possible to get the patch for the green hills generator into CMake 3.1

Thanks in advance 

Best Regards

-- 

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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

When i start "ctest -V -V -S CTestScript.cmake" manually on the command line, I 
see the following messages:

Performing coverage
RegularExpression::compile(): ?+* follows nothing.
RegularExpression::compile(): Error in compile.

Best regards


> Am 17.09.2014 um 13:07 schrieb Rolf Eike Beer :
> 
> Am 17.09.2014 12:02, schrieb David Cole via CMake:
>>> No, the submit seems fine, but the value in the Coverage.xml looks
>>> like
>>> 0.00
>>> 0.00
>>> Which can't be.
>>> However, the *-covbr.* and *-covsrc.* are generated with valid values.
>> Sounds like a bug in ctest then. There must be something going wrong in
>> the code that reads the coverage files and generates Coverage.xml.
>> Can you reproduce the problem with a minimal test case? Or debug it
>> yourself to analyze what's going wrong with ctest on the machine
>> demonstrating the problem?
> 
> Excellent would be if you could provide an output file of Bullseye that shows 
> that problem that could later be used in an automated test, the code parsing 
> Bullseye data is currently not tested at all. Ideally you would use Bullseye 
> to analyze either a dummy file or something from CMake itself so you do not 
> need to show anything of your code (and CMake doesn't need to ship that).
> 
> Greetings,
> 
> Eike
> -- 
> 
> 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
-- 

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] Code Coverage & Bullseye

[NoRulez]

Hello,

since code coverage doesn't work very well with gcov and so on on Mac, our 
company decided to use bullseye for Mac OS too.

I hope it helps

Am 17.09.2014 um 14:22 schrieb David Cole via CMake :

>> I am trying to configure the code coverage using the ctest script. I
>> took help from : http://www.cmake.org/Wiki/CTest/Coverage
> 
> That wiki page was mostly written in 2007 and 2009. You may want to
> refer to something more recent than that, and something that's proven
> to work, like an existing dashboard script that does coverage, as a
> reference.
> 
> One thing to note: there may not be a working example of somebody doing
> code coverage using the Xcode generator on a Mac. If there is,
> hopefully he will speak up here, and give you some additional hints.
> 
> You might have better luck doing a coverage dashboard on Linux using
> gcc and gcov.
> 
> See the scripts used for coverage dashboards on the CMake dashboard...
> for example, this one:
> 
> http://open.cdash.org/viewNotes.php?buildid=3493343
> 
> Especially note the use of the -fprofile-arcs -ftest-coverage flags in
> the script. (Mentioned on that wiki page, I might add.)
> 
> 
>> Is Bullseye is mandatory for code coverage using ctest ???
>> Is there any way to perform code coverage through ctest without using
>> bullseye ??
> 
> Bullseye is absolutely NOT mandatory for code coverage testing using
> ctest, it's simply one of the available options.
> 
> If you do not have Bullseye, there is no need to set the COVFILE env
> variable.
> 
> 
> 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
-- 

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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

Sorry for the long response time but we are currently in a release stage.

No, the submit seems fine, but the value in the Coverage.xml looks like

0.00
0.00

Which can't be.

However, the *-covbr.* and *-covsrc.* are generated with valid values.

Currently CMake 3.0.1 and CDash 2.2.2 are used

Best Regards

> Am 05.09.2014 um 12:45 schrieb David Cole :
> 
> When the coverage shows "0%" is there  any indication that the ctest_submit 
> for the coverage step failed? (i.e. do you log the output of ctest, and does 
> it show anything about failing to submit?)
> 
> That's another type of intermittent network blip that I see, where there's a 
> successful local build, but the submit of a piece of the dashboard fails 
> occasionally.
> 
> 
> D
> 
-- 

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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

We do not use a license manager.

The following files are created in the Testing/Temporary folder:
[DATE]-[TIME]-covbr.stderr
[DATE]-[TIME]-covbr.stdout
[DATE]-[TIME]-covsrc.stderr
[DATE]-[TIME]-covsrc.stdout
LastCoverage_[DATE]-[TIME].log

Which shows the symbols which are normally shown in CDash when a file is 
selected (e.g.: --> and so on)

Best Regards

> Am 04.09.2014 um 12:17 schrieb David Cole :
> 
> Sometimes an unfortunate network interruption (even a very brief one,
> at just the wrong time...) can cause my bullseye dashboards to report
> "0%" coverage. I use the license manager for Bullseye, so the build
> machine needs network access to the license manager machine when
> turning coverage on and off with the "cov01" Bullseye tool. If there is
> no network access at "call cov01 -1" time, then trying to turn on
> coverage measurement cannot succeed, and the result is a coverage build
> without any coverage data: 0%.
> 
> You can probably tell if this is happening to you or not by paying
> attention to the return value of cov01. I suspect it returns an error
> code in this condition, but my scripts just ignore it and continue with
> the build anyhow.
> 
> 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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

Ok then what could be the problem?
It also shows 0% coverage sometimes.

With bullshtml on the other hand the output seems to be ok. 

Best Regards

Am 15.07.2014 um 12:11 schrieb David Cole :

>>> There is an option (which should be on by default) in the
>>> "Miscellaneous" section of the project settings, which is
>>> called: "Show coverage code".
> 
>> Thanks, this solves the problem. The option wasn't checked.
> 
> The option should be *OFF* by default.
> 
> If the intent is not to show your code (because it's private, for
> example), then having it OFF is the safe default. Having it OFF by
> default and making a mistake results in emails like this... along with
> a quick and easy solution to the problem. Having it ON by default and
> making a mistake would result in the loss of privacy, which is by far a
> worse consequence, with no solution whatsoever. Please keep the default
> value *OFF*.
> 
> 
> Thanks,
> 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] [Cdash] Show results from the bullseye coverage in CDash

[NoRulez]

Thanks, this solves the problem. The option wasn't checked.

Best Regards

> Am 15.07.2014 um 08:32 schrieb Julien Jomier :
> 
> There is an option (which should be on by default) in the "Miscellaneous" 
> section of the project settings, which is called: "Show coverage code". Can 
> you make sure it's checked?
> 
> Julien
> 
>> On 15/07/2014 00:01, noru...@me.com wrote:
>> Hello,
>> 
>> I use bullseye coverage to perform coverage analysis on windows.
>> 
>> We have 2 dashboard (CDash) machines (productive, testing)
>> 
>> On the testing machine I could click on a file in CDash to display the 
>> coverage analyze for the selected file.
>> On the productive machine I doesn't have those links.
>> 
>> Does anybody know why the file links aren't shown, or where the problem 
>> could be that they aren't shown?
>> 
>> I also tried to update to CDash 2.2.2 with no luck.
>> 
>> Thanks in advance
>> 
>> Best Regards
>> ___
>> Cdash mailing list
>> cd...@public.kitware.com
>> http://public.kitware.com/mailman/listinfo/cdash
>> 
-- 

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] Show results from the bullseye coverage in CDash

[NoRulez]

Hello,

I use bullseye coverage to perform coverage analysis on windows.

We have 2 dashboard (CDash) machines (productive, testing)

On the testing machine I could click on a file in CDash to display the coverage 
analyze for the selected file.
On the productive machine I doesn't have those links.

Does anybody know why the file links aren't shown, or where the problem could 
be that they aren't shown?

I also tried to update to CDash 2.2.2 with no luck.

Thanks in advance

Best Regards

-- 

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] ExternalProject_Add show sources in Visual Studio

[NoRulez]

Ok, thank you very much.

I will try your examples.

Best Regards

> Am 19.03.2014 um 15:40 schrieb David Cole :
> 
> That's one "workaround". Two more come to mind:
> 
> (1) Another would be to force the configure/build steps of an external 
> project to run *always* rather than when the stamp file indicates they are 
> out of date. You could take a look at the open chemistry super build to see 
> an example.
> 
> Specifically, check out the code here:
> 
>
> https://github.com/OpenChemistry/openchemistry/blob/master/CMakeLists.txt#L32
> 
> And here:
> 
>
> https://github.com/OpenChemistry/openchemistry/blob/master/cmake/External_avogadrolibs.cmake#L20
> 
> Then, when forced, a build of the outer project will always trigger the build 
> of the external project and make sure it's up to date with respect to its own 
> source tree.
> 
> But, if you have a lot of these, it just slows your build down in the normal 
> case of not changing anything in the external projects. So use it sparingly, 
> not globally.
> 
> (2) One more workaround worth mentioning: the manual one. ExternalProject_Add 
> will generate VS projects for the sub-projects if they are CMake-based and 
> your containing project is using a VS generator, and then open the generated 
> sub-projects directly to see the "normal" view of things. Make mods in there, 
> and build/install in there, then go back to your containing project, and it's 
> already up to date.
> 
> To each his own... Good luck.
> 
> 
> HTH,
> David C.
> 
> 
> 
> -Original Message-
> From: NoRulez 
> To: David Cole 
> Cc: cmake 
> Sent: Wed, Mar 19, 2014 9:48 am
> Subject: Re: [CMake] ExternalProject_Add show sources in Visual Studio
> 
> 
> Ok, so the only "workaround" to archive this is to use "file(GLOB_RECURS...)"
> and rebuild the changed external project. Right?
> 
> Best Regards
> 
>> Am 19.03.2014 um 12:44 schrieb David Cole :
>> 
>> Well, that sounds like the perfect way to use ExternalProject.
>> 
>> But why do you want to show the sources in Visual Studio? Just for
> ease of
> looking at them?
>> 
>> As I said in my earlier reply... even if we showed the sources,
> editing them
> would not trigger a rebuild of the external project. The dependencies are
> tracked via custom commands and stamp files that indicate last successful run
> time of those custom commands. They are not tracked by Visual Studio on a
> per-source-file/per-obj-file basis as they are in a normal VS project.
>> 
>> The main goal of ExternalProject is to provide an easy-to-use way of
> *building*, *installing* and depending on an external project... It is most
> definitely NOT to provide an easy way to do active development on a project.
>> 
>> If you need to see the sources for something that you're building
> within
> Visual Studio, then to me, that's a big red flag that it should not be an
> external project.
>> 
>> 
>> 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://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] ExternalProject_Add show sources in Visual Studio

[NoRulez]

Ok, so the only "workaround" to archive this is to use "file(GLOB_RECURS...)" 
and rebuild the changed external project. Right?

Best Regards

> Am 19.03.2014 um 12:44 schrieb David Cole :
> 
> Well, that sounds like the perfect way to use ExternalProject.
> 
> But why do you want to show the sources in Visual Studio? Just for ease of 
> looking at them?
> 
> As I said in my earlier reply... even if we showed the sources, editing them 
> would not trigger a rebuild of the external project. The dependencies are 
> tracked via custom commands and stamp files that indicate last successful run 
> time of those custom commands. They are not tracked by Visual Studio on a 
> per-source-file/per-obj-file basis as they are in a normal VS project.
> 
> The main goal of ExternalProject is to provide an easy-to-use way of 
> *building*, *installing* and depending on an external project... It is most 
> definitely NOT to provide an easy way to do active development on a project.
> 
> If you need to see the sources for something that you're building within 
> Visual Studio, then to me, that's a big red flag that it should not be an 
> external project.
> 
> 
> 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://www.cmake.org/mailman/listinfo/cmake

[CMake] CPack and PackageMaker hide pages

[NoRulez]

Is it possible to hide some of the pages used in PackageMaker? For example if I 
don't want to show the license dialog.

Best Regards
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] ExternalProject_Add show sources in Visual Studio

[NoRulez]

Because the external projects depends on different library versions than the 
"SuperProject". Maybe I misconfigured something, but i don't know an 
alternative.

E.g.: super project (AA) builds with version 9 of library X.

The external project B requires version 5 of library X and had some source 
files.

The external project C requires version 3 of library X and had some different 
sources.

The external projects are only shared libraries (which are also standalone 
projects with there own source tree) which are then used by the super project.

If I understand it correctly then ExternalProject_Add should be the solution 
for this, right?

Best Regards

> Am 17.03.2014 um 15:24 schrieb David Cole :
> 
> Why do you want to do that?
> 
> The ExternalProject will not rebuild correctly when you modify these source 
> files... Unless you are forcing the build step to run every single time.
> 
> You are using ExternalProject as if it were NOT external. Why not just use 
> add_subdirectory instead and have an "internal" project?
> 
> 
> D
> 
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] ExternalProject_Add show sources in Visual Studio

[NoRulez]

I've added the source files with "file(GLOB_RECURSE..." and set source file 
property for each of these files with HEADER_FILE_OLY to TRUE.

It seems to work, but I'm not sure if this is the right way.


> Am 17.03.2014 um 08:49 schrieb NoRulez :
> 
> Hello,
> 
> if I add an external project with ExternalProject_Add, is it possible to show 
> the sources of that project in Visual Studio too?
> 
> I don't know if this is the reason, but currently the projects type is set to 
> utility.
> 
> Best Regards
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] ExternalProject_Add show sources in Visual Studio

[NoRulez]

Hello,

if I add an external project with ExternalProject_Add, is it possible to show 
the sources of that project in Visual Studio too?

I don't know if this is the reason, but currently the projects type is set to 
utility.

Best Regards
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] CMake and Framework/CFBundle Support

[NoRulez]

If i want to make some contributions for this, what is the best way?

Is the contribution site from CMake up to date, because I also found 
repositories on github and gitorious too, but i don't know if these are 
official repositories.

Thanks in advance

> Am 11.02.2014 um 16:01 schrieb :
> 
> 
> 
> 
> Hello,
> 
> I don't know if I overlook something or the framework/CFBundle support on Mac 
> OS is rarely.
> 
> Most of the things I have already implemented as post-build commands but are 
> there also CMake ways of doing such things?
> 
> .) Adding resources to CFBundles? (Resources for frameworks are supported)
> .) Creating PkgInfo files in CFBundles
> .) Copying custom Info.plist files to CFBundles
> With an exception of the 3rd one, I don't think there is a CMake way of doing 
> those except with post-build commands.
> For the custom Info.plist, have you tried setting the 
> MACOSX_BUNDLE_INFO_PLIST property on the target?
> 
> Clint
-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] PackageMaker with script for InstallationCheck

[NoRulez]

Hello list,

I found variables to launch custom preflight/postflight scripts with 
CPACK_PREFLIGHT_SCRIPT and CPACK_POSTFLIGHT_SCRIPT.

Is there also a way to call a custom install check script? For example, I need 
to know if a specified application is already installed or not. If the 
application wasn't found then the installer could exit.

Thanks in advance

-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Mac bundled application with multiple executables.

[NoRulez]

You can use add_custom_command as POST_BUILD step and TargetGenerators for the 
main GUI bundle to do what you want.

Best Regards

> Am 09.02.2014 um 23:56 schrieb Andreas Pakulat :
> 
> Hi Bill,
> 
>> On Sun, Feb 9, 2014 at 8:45 PM, Bill Somerville  wrote:
>> Hi,
>> 
>> noob here so firstly thanks for the great build tools!
>> 
>> I'm struggling with shoehorning a Win32/Linux Qt GUI application into CMake 
>> for those targets and for OS-X.
>> 
>> At the moment the Mac build is manually transformed into an OS-X app bundle. 
>> I am making some progress getting it to install (and package, for 
>> deployment) directly into a bundle format. Using MACOSX_BUNDLE on the main 
>> GUI executable target plus the required CMake variable declarations.
>> 
>> What I am stuck with is how to include another executable in the app bundle. 
>> It is a console type program that is spawned from the GUI to do some 
>> background work. Although it can be run standalone from the console, its 
>> purpose is to be run by the GUI program. Therefore it belongs in the bundle.
>> 
>> What incantation do I need to give CMake to get this executable into the 
>> bundle installation. It is built as a target by the same CMake script as the 
>> GUI executable.
> 
> This is how CMake itself is shipped on MacOSX (the bundle starts the qt gui 
> and contains the console gui as well as the various cli tools like cmake, 
> ctest etc. So you may want to look into CMake's own buildsystem files for 
> that, IIRC the cmake buildsystem wasn't that hard to understand and follow.
> 
> Andreas 
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] CMake and Framework/CFBundle Support

[NoRulez]

Hello,

I don't know if I overlook something or the framework/CFBundle support on Mac 
OS is rarely.

Most of the things I have already implemented as post-build commands but are 
there also CMake ways of doing such things?

.) Adding resources to CFBundles? (Resources for frameworks are supported)
.) Creating PkgInfo files in CFBundles
.) Copying custom Info.plist files to CFBundles

Thanks in advance

Best Regards-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] Libraries as bundles on Mac OS

[NoRulez]

Hello,

I know how to create bundles for applications, but how can I create bundles for 
libraries. For example when I want to create a plugin for an adobe product 
(Illustrator => plugin.aip)?

The add_library command does not except MACOSX_BUNDLE, only MODULE, SHARED and 
STATIC are allowed. The target property MACOSX_BUNDLE does also not work.

Thanks in advance 

Best Regards
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Problems with renamed CMake Generators

[NoRulez]

I know I can use CMAKE_CL_64 to detect 32/64 bit and MSVC12 if the Visual 
Studio 2013 generator is used. 

But what about other compilers/IDEs?

> Am 23.01.2014 um 08:19 schrieb NoRulez :
> 
> Hello,
> 
> at the moment I test with if("${CMAKE_GENERATOR}" STREQUAL "Visual Studio 12")
> 
> in the upcoming release of CMake this string has changed. So, is there an 
> other way to test for generators and if a generator is called for 32/64bit?
> 
> Thanks in advance
> Best Regardsn
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

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

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

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

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

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

[CMake] Problems with renamed CMake Generators

[NoRulez]

Hello,

at the moment I test with if("${CMAKE_GENERATOR}" STREQUAL "Visual Studio 12")

in the upcoming release of CMake this string has changed. So, is there an other 
way to test for generators and if a generator is called for 32/64bit?

Thanks in advance
Best Regardsn
-- 

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Backslash instead of slashes in *.vcxproj files

[NoRulez]

No, it's not as simple as it looks like, because the project name and 
repository name itself starts with MP*

So, to rename a directory or two it's ok, but not if we must change the 
complete infrastructure. ;-)

Is there no way to execute some commands after the creation is finished? E.g. 
Some post command/script execution?


> Am 07.01.2014 um 18:43 schrieb David Cole :
> 
> It may be ugly, it may be painful, you might not like it  
> 
>  but isn't the simple workaround to rename the directory (or copy its 
> contents to an alternate location) such that it does not have a "/MP" in 
> it?
> 
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Backslash instead of slashes in *.vcxproj files

[NoRulez]

Sure, but in the meanwhile I need a workaround too.

> Am 07.01.2014 um 18:20 schrieb Bill Hoffman :
> 
>> On 1/7/2014 11:12 AM, NoRulez wrote:
>> Hello,
>> 
>> is there a simple way to replace the slashes (directory delimiter) with 
>> backslashes for include paths after or during the generation of *.vcxproj 
>> files?
>> 
>> The problem which is described here exists in VS2012 and 
>> VS2013:http://connect.microsoft.com/VisualStudio/feedback/details/778367/vc-2012-mistakes-include-path-for-compiler-switch-and-runs-a-full-rebuild
> Can you create a bug for this?
> 
> 
> -- 
> 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
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

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

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

[CMake] Backslash instead of slashes in *.vcxproj files

[NoRulez]

Hello,

is there a simple way to replace the slashes (directory delimiter) with 
backslashes for include paths after or during the generation of *.vcxproj files?

The problem which is described here exists in VS2012 and VS2013: 
http://connect.microsoft.com/VisualStudio/feedback/details/778367/vc-2012-mistakes-include-path-for-compiler-switch-and-runs-a-full-rebuild

I already tried to override the add_library and add_executable functions, but 
it seems that the generation process is called after the functions.

Thanks in advance

Best regards 
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] CMake doesn't list 64-bit generator

[NoRulez]

Previous versions of CMake should list those platforms too.
Would this intentionally be removed in the newer versions?

Best Regards

> Am 29.11.2013 um 03:10 schrieb William Woodbury :
> 
>> On 28/11/2013 21:37, NoRulez wrote:
>> Hi,
>> 
>> I've installed VS 2010 professional with x64 tools on a fresh installed 
>> windows 7 ultimate 64-bit system and I also want to use CMake 2.8.12.
>> 
>> After the installation stuff, when I run CMake on the command line, then no 
>> 64 bit generator are listed.
>> 
>> I tried this in the normal command prompt, in the Visual Studio x64 Cross 
>> Tools (2010) command prompt and in the Visual Studio x64 Win64 (2010) 
>> command prompt.
>> 
>> All I get is the following:
>> The following generators are available on this platform:
>>   Visual Studio 6 = Generates Visual Studio 6 project files.
>>   Visual Studio 7 = Generates Visual Studio .NET 2002 project
>> files.
>>   Visual Studio 10= Generates Visual Studio 10 (2010) project
>> files.
>>   Visual Studio 11= Generates Visual Studio 11 (2012) project
>> files.
>>   Visual Studio 12= Generates Visual Studio 12 (2013) project
>> files.
>>   Visual Studio 7 .NET 2003   = Generates Visual Studio .NET 2003 project
>> files.
>>   Visual Studio 8 2005= Generates Visual Studio 8 2005 project files.
>>   Visual Studio 9 2008= Generates Visual Studio 9 2008 project files.
>>   Borland Makefiles   = Generates Borland makefiles.
>>   NMake Makefiles = Generates NMake makefiles.
>>   NMake Makefiles JOM = Generates JOM makefiles.
>>   Watcom WMake= Generates Watcom WMake makefiles.
>>   MSYS Makefiles  = Generates MSYS makefiles.
>>   MinGW Makefiles = Generates a make file for use with
>> mingw32-make.
>>   Unix Makefiles  = Generates standard UNIX makefiles.
>>   Ninja   = Generates build.ninja files (experimental).
>>   CodeBlocks - MinGW Makefiles= Generates CodeBlocks project files.
>>   CodeBlocks - NMake Makefiles= Generates CodeBlocks project files.
>>   CodeBlocks - Ninja  = Generates CodeBlocks project files.
>>   CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
>>   Eclipse CDT4 - MinGW Makefiles
>>   = Generates Eclipse CDT 4.0 project files.
>>   Eclipse CDT4 - NMake Makefiles
>>   = Generates Eclipse CDT 4.0 project files.
>>   Eclipse CDT4 - Ninja= Generates Eclipse CDT 4.0 project files.
>>   Eclipse CDT4 - Unix Makefiles
>>   = Generates Eclipse CDT 4.0 project files.
>>   Sublime Text 2 - MinGW Makefiles
>>   = Generates Sublime Text 2 project files.
>>   Sublime Text 2 - NMake Makefiles
>>   = Generates Sublime Text 2 project files.
>>   Sublime Text 2 - Ninja  = Generates Sublime Text 2 project files.
>>   Sublime Text 2 - Unix Makefiles
>>   = Generates Sublime Text 2 project files.
>> 
>> Did I need to set up some additional environment variables?
>> 
>> Thanks in advance
>> 
>> Best Regards
>> --
>> 
>> Powered by www.kitware.com
>> 
>> Please keep messages on-topic and check the CMake FAQ at: 
>> http://www.cmake.org/Wiki/CMake_FAQ
>> 
>> Kitware offers various services to support the CMake community. For more 
>> information on each offering, please visit:
>> 
>> CMake Support: http://cmake.org/cmake/help/support.html
>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>> 
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
> I mean "Visual Studio 10 Win64", not "Visual Studio 2010 Win64"
> --
> 
> 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] CMake doesn't list 64-bit generator

[NoRulez]

Hi,

I've installed VS 2010 professional with x64 tools on a fresh installed windows 
7 ultimate 64-bit system and I also want to use CMake 2.8.12.

After the installation stuff, when I run CMake on the command line, then no 64 
bit generator are listed.

I tried this in the normal command prompt, in the Visual Studio x64 Cross Tools 
(2010) command prompt and in the Visual Studio x64 Win64 (2010) command prompt.

All I get is the following:
The following generators are available on this platform:
  Visual Studio 6 = Generates Visual Studio 6 project files.
  Visual Studio 7 = Generates Visual Studio .NET 2002 project
files.
  Visual Studio 10= Generates Visual Studio 10 (2010) project
files.
  Visual Studio 11= Generates Visual Studio 11 (2012) project
files.
  Visual Studio 12= Generates Visual Studio 12 (2013) project
files.
  Visual Studio 7 .NET 2003   = Generates Visual Studio .NET 2003 project
files.
  Visual Studio 8 2005= Generates Visual Studio 8 2005 project files.
  Visual Studio 9 2008= Generates Visual Studio 9 2008 project files.
  Borland Makefiles   = Generates Borland makefiles.
  NMake Makefiles = Generates NMake makefiles.
  NMake Makefiles JOM = Generates JOM makefiles.
  Watcom WMake= Generates Watcom WMake makefiles.
  MSYS Makefiles  = Generates MSYS makefiles.
  MinGW Makefiles = Generates a make file for use with
mingw32-make.
  Unix Makefiles  = Generates standard UNIX makefiles.
  Ninja   = Generates build.ninja files (experimental).
  CodeBlocks - MinGW Makefiles= Generates CodeBlocks project files.
  CodeBlocks - NMake Makefiles= Generates CodeBlocks project files.
  CodeBlocks - Ninja  = Generates CodeBlocks project files.
  CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
  Eclipse CDT4 - MinGW Makefiles
  = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - NMake Makefiles
  = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Ninja= Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Unix Makefiles
  = Generates Eclipse CDT 4.0 project files.
  Sublime Text 2 - MinGW Makefiles
  = Generates Sublime Text 2 project files.
  Sublime Text 2 - NMake Makefiles
  = Generates Sublime Text 2 project files.
  Sublime Text 2 - Ninja  = Generates Sublime Text 2 project files.
  Sublime Text 2 - Unix Makefiles
  = Generates Sublime Text 2 project files.

Did I need to set up some additional environment variables?

Thanks in advance

Best Regards 
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Difference between CMake and CVS CMake when using Bullseye

[NoRulez]

Ok, I think it is working now.

The nightly build shows coverage informations.

I extend the IF statement:

if (WITH_COVERAGE AND (CTEST_COVERAGE_COMMAND OR COV01))

Best Regards

> Am 21.11.2013 um 22:19 schrieb Bill Hoffman :
> 
>> On 11/21/2013 3:16 PM, NoRulez wrote:
>> I followed the following article in the Wiki to extend my CTestScript:
>> 
>> http://www.cmake.org/Wiki/CTest/Coverage#C.2FC.2B.2B_Coverage_with_Bullseye
>> 
>> And i read about CVS CMake in the mailing list:
> http://www.cmake.org/pipermail/cmake/2007-December/018610.html
> 
> 
> OK, that was in 2007, bullseye support has been in CMake releases for a long 
> time now.
> 
>> 
>> In the logs i see that bullseye is running with the message:
> "BullseyeCoverage Compile C++ 8.8.6 Windows License"
>> 
>> But I doesn't have the output in the coverage category under CDash.
> With gcov I get the expected result.
> 
> Can you post the script you are using?
> 
> Also the output of the ctest run to go along with the script.
> 
> -Bill
> 
> 
> 
> --
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Difference between CMake and CVS CMake when using Bullseye

[NoRulez]

I followed the following article in the Wiki to extend my CTestScript:

http://www.cmake.org/Wiki/CTest/Coverage#C.2FC.2B.2B_Coverage_with_Bullseye

And i read about CVS CMake in the mailing list: 
http://www.cmake.org/pipermail/cmake/2007-December/018610.html


In the logs i see that bullseye is running with the message: "BullseyeCoverage 
Compile C++ 8.8.6 Windows License"

But I doesn't have the output in the coverage category under CDash. With gcov I 
get the expected result.

Best Regards



> Am 21.11.2013 um 18:19 schrieb Bill Hoffman :
> 
>> On 11/21/2013 11:44 AM, NoRulez wrote:
>> Hi,
>> 
>> i want to try Bullseye on Windows and have CMake 2.8.12 installed.
> 
>> Bullseye get called, creates the CMake.cov file in the binary folder
> but doesn't produce output in CDash.
>> I then read that this does only work when CVS CMake is used. What is
> the difference between these CMake versions.
>> 
>> Thanks in advance
>> --
> Should work.  Can you give more details?  I assume when you say CVS CMake you 
> mean git next?
> 
> What commands did you run, and what was the output?
> 
> -Bill
> --
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

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

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

[CMake] Difference between CMake and CVS CMake when using Bullseye

[NoRulez]

Hi,

i want to try Bullseye on Windows and have CMake 2.8.12 installed.

Bullseye get called, creates the CMake.cov file in the binary folder but 
doesn't produce output in CDash.
I then read that this does only work when CVS CMake is used. What is the 
difference between these CMake versions.

Thanks in advance 
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Experimental builds not always shown in CDash

[NoRulez]

I checked the logs from the web server which looks fine.

I also have a look on the generated xml files (Update, Submit, ...), these 
looks also good.

The LastSubmit file shows "successfully sent".

The CDash remains empty, no experimental build


> Am 20.11.2013 um 18:30 schrieb Micha Hergarden :
> 
> 
> 
>> On 11/20/2013 06:08 PM, NoRulez wrote:
>> When I run "ctest -V -S CTestScript.cmake" then everything is done 
>> successfully, except that I doesn't see the build under CDash.
>> 
>>>> Am 20.11.2013 um 17:30 schrieb Nils Gladitz :
>>>> 
>>>> On 20.11.2013 17:23, NoRulez wrote:
>>>> Now the problem is, that sometimes the experimental entry are shown in 
>>>> CDash, but not every time when I call the CTest script.
>>>> 
>>>> I don't know when it was shown or not.
>>>> Did I need to configure some additional settings to get it to work?
>>>> 
>>>> I use CMake 2.8.12 on Windows 7.
>>> Maybe the script itself intermittently fails before or during submission 
>>> (ctest_submit())?
>>> 
>>> Nils
>> --
>> 
>> Powered by www.kitware.com
>> 
>> Please keep messages on-topic and check the CMake FAQ at: 
>> http://www.cmake.org/Wiki/CMake_FAQ
>> 
>> Kitware offers various services to support the CMake community. For more 
>> information on each offering, please visit:
>> 
>> CMake Support: http://cmake.org/cmake/help/support.html
>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>> 
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
> Have you checked the logs from the webserver running CDash? I once had
> failing submissions because the xml file reached the post limit of the
> nginx server. You can also check the logs
> /Testing/Temporary/LastSubmit* to see what errors
> emerged during submit.
> 
> hth,
> Micha
> 
> 
> 
> 
> 
> --
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] Experimental builds not always shown in CDash

[NoRulez]

When I run "ctest -V -S CTestScript.cmake" then everything is done 
successfully, except that I doesn't see the build under CDash.

> Am 20.11.2013 um 17:30 schrieb Nils Gladitz :
> 
>> On 20.11.2013 17:23, NoRulez wrote:
>> Now the problem is, that sometimes the experimental entry are shown in 
>> CDash, but not every time when I call the CTest script.
>> 
>> I don't know when it was shown or not.
>> Did I need to configure some additional settings to get it to work?
>> 
>> I use CMake 2.8.12 on Windows 7.
> Maybe the script itself intermittently fails before or during submission 
> (ctest_submit())?
> 
> Nils
--

Powered by www.kitware.com

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

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

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

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

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

[CMake] Experimental builds not always shown in CDash

[NoRulez]

Hello,

in my CTestScript I have the following:

set(MODEL "Experimental")
ctest_start(${MODEL} TRACK ${MODEL})
.
.
.

The script is called from a scheduler every 30 minutes:
ctest -S CTestScript.cmake

Now the problem is, that sometimes the experimental entry are shown in CDash, 
but not every time when I call the CTest script.

I don't know when it was shown or not.
Did I need to configure some additional settings to get it to work?

I use CMake 2.8.12 on Windows 7.

Thanks in advance 
--

Powered by www.kitware.com

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

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

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

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

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

[CMake] Weird problems after updating to 2.8.12

[norulez]

Hello,

I updated cmake from 2.8.10-2 to 2.8.12.
Since the update I get the following error on Mac OS (10.6.8) when I run the 
command 'cmake -G "Unix Makefiles" ../source':

"add_subdirectory not given a binary directory but the given source directory 
is not a subdirectory of...
When specifying an out-of-tree source a binary directory must be explicitly 
specified."

The main CMakeLists.txt file looks like:

.
.
.
add_subdirectory(prjA)
add_subdirectory(prjB)
.
.
.

Has something changed for the add_directory() command?

The second problem after the upgrade is that I get the messages "sh: ps: 
command not found" when I use Qt4 in my projects.

Thanks in advance

--

Powered by www.kitware.com

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

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

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

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

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

[CMake] Weird problems after updating to 2.8.12

[NoRulez]

Hello,

I updated cmake from 2.8.10-2 to 2.8.12.
Since the update I get the following error on Mac OS (10.6.8) when I run the 
command 'cmake -G "Unix Makefiles" ../source':

"add_subdirectory not given a binary directory but the given source directory 
is not a subdirectory of...
When specifying an out-of-tree source a binary directory must be explicitly 
specified."

The main CMakeLists.txt file looks like:

.
.
.
add_subdirectory(prjA)
add_subdirectory(prjB)
.
.
.

Has something changed for the add_directory() command?

The second problem after the upgrade is that I get the messages "sh: ps: 
command not found" when I use Qt4 in my projects.

Thanks in advance

--

Powered by www.kitware.com

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

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

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

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

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

Re: [CMake] ctest_update with git fetch --tags (was: ctest & git submodules)

[NoRulez]

Thank you very much.

The goal is to have a nightly/continuous build with the tagged version number.

Without the "--tags" option it is only working if we push the changes after 
tagging.

With the "--tags" option it is now also possible to move/overwrite tags which 
gets then updated.

In the projects CMakeLists.txt file we get the current tag/version with "git 
describe --tags"

Maybe there would be alternatives but currently this is working fine. But we 
are open for suggestions.

Best Regards

Am 28.02.2013 um 17:38 schrieb Brad King :

> On 02/28/2013 11:11 AM, NoRulez wrote:
>> I've attached the two log files, can you take a look on it?
> 
> After running "git fetch" CMake reads .git/FETCH_HEAD to determine
> what branch is intended for merge (just as pull does).  This is the
> same as "git pull --tags" failing.  You need to specify the remote
> and branch explicitly to use pull with --tags:
> 
> set(CTEST_GIT_UPDATE_OPTIONS "--tags origin master")
> 
> CMake cannot add this automatically because the entire point of
> reading FETCH_HEAD is that CMake does not try to parse the git
> config to learn this information.
> 
> What is your goal of using --tags?  The ctest_update command's job
> is to follow a tracking branch.  What do tags have to do with that?
> 
> -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

[CMake] ctest & git submodules

[NoRulez]

Hello Brad,I've attached the two log files, can you take a look on it?Thanks in advanceBest Regards

Am 28.02.2013 um 16:41 schrieb Brad King <brad.k...@kitware.com>:

> On 02/28/2013 10:34 AM, NoRulez wrote:
>> Yes, it is the command which I want.
>> 
>> On the command line the same command works in the source tree.
>> 
>> The command only fails during the CTest run if I set the option.
> 
> Read
> 
> Testing/Temporary/LastUpdate*.log
> 
> in the test build tree for verbose details.
> 
> -Brad
--- Begin Cleanup ---
--- End Cleanup ---
"/usr/bin/git" "rev-list" "-n" "1" "HEAD"
rl-err> fatal: ambiguous argument 'HEAD': both revision and filename
rl-err> Use '--' to separate filenames from revisions
--- Begin Update ---
"/usr/bin/git" "fetch" "--tags"
"/usr/bin/git" "rev-parse" "--git-dir"
rev-parse-out> .git
FETCH_HEAD has no upstream branch candidate!
--- End Update ---
"/usr/bin/git" "rev-list" "-n" "1" "HEAD"
rl-err> fatal: ambiguous argument 'HEAD': both revision and filename
rl-err> Use '--' to separate filenames from revisions
--- Begin Revisions ---
"/usr/bin/git" "rev-list" "--reverse" ".." "--" | "/usr/bin/git" "diff-tree" 
"--stdin" "--always" "-z" "-r" "--pretty=raw" "--encoding=utf-8"
dt-out> 
"/usr/bin/git" "update-index" "--refresh"
"/usr/bin/git" "diff-index" "-z" "HEAD"
di-err> fatal: ambiguous argument 'HEAD': both revision and filename
di-err> Use '--' to separate filenames from revisions
--- End Revisions ---
--- Begin Cleanup ---
--- End Cleanup ---
"/usr/bin/git" "rev-list" "-n" "1" "HEAD"
rl-err> fatal: ambiguous argument 'HEAD': both revision and filename
rl-err> Use '--' to separate filenames from revisions
--- Begin Update ---
"/usr/bin/git" "fetch"
"/usr/bin/git" "rev-parse" "--git-dir"
rev-parse-out> .git
FETCH_HEAD> b2209bbe079ff44ba7df190b55e75efcdba9ed0bnot-for-merge   branch 
'1.0' of SERVER:PROJECT
FETCH_HEAD> f7b45494636cacace32d334d86307c161ed1aa69not-for-merge   branch 
'1.1' of SERVER:PROJECT
FETCH_HEAD> f9eb31076046ef23bee15f395dd6904d98800afdnot-for-merge   branch 
'1.1.1' of SERVER:PROJECT
FETCH_HEAD> 8faab638d94b3ad5d70269d07e0cea1f3ad225fbnot-for-merge   branch 
'1.2' of SERVER:PROJECT
FETCH_HEAD> 057f5e4f4a09728526d433e67d0f87c2e8df18fenot-for-merge   branch 
'1.3' of SERVER:PROJECT
FETCH_HEAD> d34837a189fb9412424eee7da3f49f41430a02d0not-for-merge   branch 
'1.4' of SERVER:PROJECT
FETCH_HEAD> 0f16cb2c6725babbef4da42aebf74cab3fecaad2branch 'master' 
of SERVER:PROJECT
"/usr/bin/git" "reset" "--hard" "0f16cb2c6725babbef4da42aebf74cab3fecaad2"
reset-out> HEAD is now at 0f16cb2 Implemented the unified tool bar on Mac OS X
"/usr/bin/git" "rev-parse" "--show-cdup"
rev-parse-out> 
"/usr/bin/git" "--version"
version-out> git version 1.7.5.4
"/usr/bin/git" "submodule" "update" "--recursive"
--- End Update ---
"/usr/bin/git" "rev-list" "-n" "1" "HEAD"
rl-err> fatal: ambiguous argument 'HEAD': both revision and filename
rl-err> Use '--' to separate filenames from revisions
--- Begin Revisions ---
"/usr/bin/git" "rev-list" "--reverse" ".." "--" | "/usr/bin/git" "diff-tree" 
"--stdin" "--always" "-z" "-r" "--pretty=raw" "--encoding=utf-8"
dt-out> 
"/usr/bin/git" "update-index" "--refresh"
"/usr/bin/git" "diff-index" "-z" "HEAD"
di-err> fatal: ambiguous argument 'HEAD': both revision and filename
di-err> Use '--' to separate filenames from revisions
--- End Revisions ---
--

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] ctest & git submodules

[NoRulez]

Yes, it is the command which I want.

On the command line the same command works in the source tree.

The command only fails during the CTest run if I set the option.


Am 28.02.2013 um 13:07 schrieb Brad King :

> On 02/28/2013 02:38 AM, NoRulez wrote:
>> But if I set the option:
>> set(CTEST_GIT_UPDATE_OPTIONS "--tags")
>> 
>> Then I get the following error message:
>> Update command failed: "C:/Program Files/Git/cmd/git.cmd" "fetch" "--tags"
> 
> Isn't that the command you want?  Perhaps it really fails.
> Try running it by hand from a command line.
> 
> -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] ctest & git submodules

[NoRulez]

But if I set the option:
set(CTEST_GIT_UPDATE_OPTIONS "--tags")

Then I get the following error message:
Update command failed: "C:/Program Files/Git/cmd/git.cmd" "fetch" "--tags"

Did I miss something?

Thanks in advance
Best Regards

Am 27.02.2013 um 14:01 schrieb Brad King :

> On 02/27/2013 12:36 AM, NoRulez wrote:
>> I think for the --tags option it is the same, isn't it?
>> 
>> How can I set such option for the checkout/update command?
> 
> The --tags option belongs to "git fetch" and extra flags can
> be added for that by setting CTEST_GIT_UPDATE_OPTIONS before
> calling ctest_update.  Try:
> 
> set(CTEST_GIT_UPDATE_OPTIONS "--tags")
> ...
> ctest_update()
> 
> Alternatively one may configure the Git repo with
> 
> git config remote.origin.tagopt "--tags"
> 
> so that "git fetch" does it automatically.
> 
> -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] ctest & git submodules

[NoRulez]

I think for the --tags option it is the same, isn't it?

How can I set such option for the checkout/update command?

Best Regards

Am 26.02.2013 um 22:50 schrieb Brad King :

> On 2/26/2013 2:52 PM, Jean-Christophe Fillion-Robin wrote:
>> +1 to add these into CTest :) What would be the argument against it ?
> 
> Not every project wants every submodule checked out all the time.
> A major use case for them is to have an umbrella project with many
> submodules and the developer may only checkout and work on some.
> Some may even be proprietary and inaccessible to some machines.
> 
>>> However, it seems to me that ctest already does a
>>> git submodule update --recurse
> 
> This is the proper command to update everything that is already
> to configured to checkout in the source tree.
> 
>>> but its missing the --init flag to deal with changes to the
>>> .gitmodules file.
>>It also misses git submodule sync to deal with changes in git
>>submodule URL,
> 
> These are all intentionally missing for the above reason.  We
> should honor the user's configuration.  Maybe they intentionally
> use a custom url for a submodule for the branch they test.  We
> should not blow away their configuration by default.
> 
>> and reset --hard etc.
> 
> We do a reset --hard at the top level but I do not think we
> do it in the submodules.  That may be worth adding, perhaps
> with git submodule foreach.
> 
>>We have just been dealing with a
>>few of these issues and currently call git directly to sync, init, and
>>then use submodule foreach to reset and clean all submodules before
>>updating.
> 
> That is the expected way to deal with it.  The local dashboard
> script knows if it needs to preserve the user config or not.
> 
> We could also consider adding options for ctest_update to
> tell it to init, sync, etc., but it should not be the default.
> 
> -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
--

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] ctest & git submodules

[NoRulez]

Here is a working example:

## -- Update git submodules
if (EXISTS "${CTEST_SOURCE_DIRECTORY}/.gitmodules")
message (" -- Update git submodules ${MODEL} - ${CTEST_BUILD_NAME} --")
execute_process (COMMAND ${GIT_EXECUTABLE} submodule update --init --recursive
WORKING_DIRECTORY ${CTEST_SOURCE_DIRECTORY})
endif ()

Best Regards

Am 26.02.2013 um 20:16 schrieb NoRulez :

> Hi,
> 
> I don't think so, you could check for a .git directory and then call
> 
> git submodule update --init --recursive
> 
> Best Regards
> 
> Am 26.02.2013 um 18:34 schrieb Clinton Stimpson :
> 
>> 
>> Is there anything special I need to do with ctest so that the ctest_update() 
>> will recognize git submodules and do any init/update of those for me?  I 
>> assumed it would be automatic, but that doesn't seem to be the case.
>> 
>> -- 
>> Clinton Stimpson
>> Elemental Technologies, Inc
>> Computational Simulation Software, LLC
>> www.csimsoft.com
>> --
>> 
>> 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
--

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] ctest & git submodules

[NoRulez]

Hi,

I don't think so, you could check for a .git directory and then call

git submodule update --init --recursive

Best Regards

Am 26.02.2013 um 18:34 schrieb Clinton Stimpson :

> 
> Is there anything special I need to do with ctest so that the ctest_update() 
> will recognize git submodules and do any init/update of those for me?  I 
> assumed it would be automatic, but that doesn't seem to be the case.
> 
> -- 
> Clinton Stimpson
> Elemental Technologies, Inc
> Computational Simulation Software, LLC
> www.csimsoft.com
> --
> 
> 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] How to set CTest Update Options correctly

[NoRulez]

Hello again, 

CTEST_UPDATE_COMMAND is set to ${GIT_EXECUTABLE}.

I also tried to extend the CTEST_CHECKOUT_COMMAND variable, but here I get also 
an error.

Please, could someone help?

Thanks in advance

Am 25.02.2013 um 18:15 schrieb NoRulez :

> Hello,
> i've set CTEST_UPDATE_OPTIONS as followed:
> 
> set(CTEST_UPDATE_OPTIONS "--tags")
> 
> I set this, because I need newely created and/or modified tags.
> 
> When I set this option then I get the error: 
> "git.cmd" "fetch" "--tags" Update command failed
> 
> Is there an other way of doing so?
> 
> Thanks in advance
> 
> Best Regards
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

[CMake] How to set CTest Update Options correctly

[NoRulez]

Hello,
i've set CTEST_UPDATE_OPTIONS as followed:

set(CTEST_UPDATE_OPTIONS "--tags")

I set this, because I need newely created and/or modified tags.

When I set this option then I get the error: 
"git.cmd" "fetch" "--tags" Update command failed

Is there an other way of doing so?

Thanks in advance

Best Regards
--

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] Running CPack and ignore exit codes

[NoRulez]

Thank you I will try it.

In the future I/we will handle it better and do not ignore errors. ;-)

Best Regards

Am 06.02.2013 um 20:57 schrieb Eric Noulard :

> 2013/2/6 NoRulez :
>> You're right. Normally I do not ignore errors, but in some situations if
>> unit tests and/or parts of new libraries are under development, on some
>> platforms they won't compile/link, but the main application is still stable
>> and could be packaged. I think you know what I mean. It is not my decision.
>> 
>> How could I overwrite it?
> 
> If you know that some project or component of a project
> shall not be packaged then you can
> set CPACK_INSTALL_CMAKE_PROJECTS.
> The expected content is a list of quadruplet
> see cpack --help-variable CPACK_INSTALL_CMAKE_PROJECTS
> 
> Its defaul value is "; ; ALL; /"
> 
> You can overwrite it with your own value.
> (In CMakeLists.txt or on CPack command line, command line value
> should has higher priority than value found in CPackConfig.cmake)
> 
> the "ALL" is a component name so that you can chose to install
> only some component of the concerned project.
> 
> You should be able to put as many quadruplet as you want in there.
> 
>> Am 06.02.2013 um 20:23 schrieb David Cole :
>> 
>> My advice to you would be not to ignore the errors.
> 
> I would say that as well.
> 
> -- 
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

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

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

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

Re: [CMake] Running CPack and ignore exit codes

[NoRulez]

You're right. Normally I do not ignore errors, but in some situations if unit 
tests and/or parts of new libraries are under development, on some platforms 
they won't compile/link, but the main application is still stable and could be 
packaged. I think you know what I mean. It is not my decision.

How could I overwrite it?


Am 06.02.2013 um 20:23 schrieb David Cole :

> My advice to you would be not to ignore the errors.
> 
> If you want to ignore them anyway, you're on your own. Or maybe somebody else 
> who is also ignoring errors like these will step up with some alternate 
> advice. ;-)
> 
> You can override what CPack calls for "make install" -- you can tell it to 
> run something else that won't do a "make all" first. But it would probably be 
> easier to just fix the errors.
> 
> 
> D
> 
> 
> -Original Message-
> From: NoRulez 
> To: David Cole 
> Cc: eric.noulard ; cmake 
> Sent: Wed, Feb 6, 2013 2:19 pm
> Subject: Re: [CMake] Running CPack and ignore exit codes
> 
> Ok, when I have the following situation:
> 
> prj1 (install target)
> prj2 (not install target but produce compile error, so this could be ignored)
> prj3 (install target)
> prj4 (install target)
> 
> At the moment I call "cpack -G ZIP" (normally I call cpack from within a 
> CTestScript) and it stops by prj2 without building the zip archive.
> If the prj2 doesn't have errors it runs smoothly.
> 
> Did this mean that I must know (at CTestScript time) which projects should be 
> build?
> e.g.: cpack -G ZIP prj1 prj2 prj3?
> 
> Best Regards
> 
> Am 06.02.2013 um 19:58 schrieb David Cole :
> 
>> CPack does call "make install" -- and make install first does a make all to 
>> get everything up to date.
>> 
>> So even calling just cpack by itself in this situation is no good.
>> 
>> 
>> 
>> -Original Message-
>> From: Eric Noulard 
>> To: NoRulez 
>> Cc: CMake ML 
>> Sent: Wed, Feb 6, 2013 1:57 pm
>> Subject: Re: [CMake] Running CPack and ignore exit codes
>> 
>> 2013/2/6 NoRulez :
>> > Because CPack runs the default (all) target.
>> 
>> Ok now I think I get it.
>> 
>> AIFAIK, CPack does NOT run "all" target.
>> 
>> "make package" does.
>> 
>> You should be able to call CPack explicitely without problem, try:
>> 
>> cpack
>> 
>> in your build dir. However this won't try to build anything.
>> 
>> > It could be that a target doesn't build because of compile or link errors 
>> > and 
>> are not an install target (unit tests for example or other sub projects 
>> which 
>> are not required).
>> 
>> You'll build a package with a failing unit test !! :-]
>> 
>> > CPack should build as much as possible and only break if an install target 
>> > has 
>> errors.
>> 
>> Like I said, CPack does not build anything per se, the "package"
>> target depends on "all"
>> so that the build tool (make,  Visual Studio, XCode etc...) does build all.
>> 
>> > Currently it is not possible to run cpack and create packages for such 
>> situation.
>> 
>> True but I'm not sure I would personnally want to build a package out
>> of a partially buildable project.
>> Other may have other opinion though.
>> 
>> From my point of view, if you really want to accept the building of a
>> package even if
>> some target may fail then you could simply make the building of those
>> targets optional
>> using
>> 
>> option(BUILD_OPTIONAL_TARGET "Build Optional Target" OFF)
>> 
>> then
>> if(BUILD_OPTIONAL_TARGET)
>>   add_executable(...)
>> endif()
>> 
>> Then set BUILD_OPTIONAL_TARGET to OFF if you don't care of those when
>> building a package.
>> 
>> Currently CMake (and not CPack) is not  tracking down target that
>> "are built but not installed"
>> it may be doable but this would be a new feature.
>> I don't really know the portion of CMake code handling manifest files
>> but AFAIRemember this was handled **at install time** so that the
>> list of "to be installed files/target" is unknown at CMake time.
>> 
>> What "may be possible" is to add a new "package/fast" target
>> which would depend on "preinstall/fast and install/fast" instead of
>> "preinstall" so that
>> you will avoid the build of "all"
>> 
>> The trouble is, the fast t

Re: [CMake] Running CPack and ignore exit codes

[NoRulez]

Ok, when I have the following situation:

prj1 (install target)
prj2 (not install target but produce compile error, so this could be ignored)
prj3 (install target)
prj4 (install target)

At the moment I call "cpack -G ZIP" (normally I call cpack from within a 
CTestScript) and it stops by prj2 without building the zip archive.
If the prj2 doesn't have errors it runs smoothly.

Did this mean that I must know (at CTestScript time) which projects should be 
build?
e.g.: cpack -G ZIP prj1 prj2 prj3?

Best Regards

Am 06.02.2013 um 19:58 schrieb David Cole :

> CPack does call "make install" -- and make install first does a make all to 
> get everything up to date.
> 
> So even calling just cpack by itself in this situation is no good.
> 
> 
> 
> -Original Message-
> From: Eric Noulard 
> To: NoRulez 
> Cc: CMake ML 
> Sent: Wed, Feb 6, 2013 1:57 pm
> Subject: Re: [CMake] Running CPack and ignore exit codes
> 
> 2013/2/6 NoRulez :
> > Because CPack runs the default (all) target.
> 
> Ok now I think I get it.
> 
> AIFAIK, CPack does NOT run "all" target.
> 
> "make package" does.
> 
> You should be able to call CPack explicitely without problem, try:
> 
> cpack
> 
> in your build dir. However this won't try to build anything.
> 
> > It could be that a target doesn't build because of compile or link errors 
> > and 
> are not an install target (unit tests for example or other sub projects which 
> are not required).
> 
> You'll build a package with a failing unit test !! :-]
> 
> > CPack should build as much as possible and only break if an install target 
> > has 
> errors.
> 
> Like I said, CPack does not build anything per se, the "package"
> target depends on "all"
> so that the build tool (make,  Visual Studio, XCode etc...) does build all.
> 
> > Currently it is not possible to run cpack and create packages for such 
> situation.
> 
> True but I'm not sure I would personnally want to build a package out
> of a partially buildable project.
> Other may have other opinion though.
> 
> From my point of view, if you really want to accept the building of a
> package even if
> some target may fail then you could simply make the building of those
> targets optional
> using
> 
> option(BUILD_OPTIONAL_TARGET "Build Optional Target" OFF)
> 
> then
> if(BUILD_OPTIONAL_TARGET)
>   add_executable(...)
> endif()
> 
> Then set BUILD_OPTIONAL_TARGET to OFF if you don't care of those when
> building a package.
> 
> Currently CMake (and not CPack) is not  tracking down target that
> "are built but not installed"
> it may be doable but this would be a new feature.
> I don't really know the portion of CMake code handling manifest files
> but AFAIRemember this was handled **at install time** so that the
> list of "to be installed files/target" is unknown at CMake time.
> 
> What "may be possible" is to add a new "package/fast" target
> which would depend on "preinstall/fast and install/fast" instead of
> "preinstall" so that
> you will avoid the build of "all"
> 
> The trouble is, the fast target does not build **anything** so you'll
> have to do:
> 
> make -k all
> make package/fast
> 
> to achieve what you want.
> 
> -- 
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

Re: [CMake] Running CPack and ignore exit codes

[NoRulez]

Because CPack runs the default (all) target.

It could be that a target doesn't build because of compile or link errors and 
are not an install target (unit tests for example or other sub projects which 
are not required).

CPack should build as much as possible and only break if an install target has 
errors.

Currently it is not possible to run cpack and create packages for such 
situation.

Best Regards

Am 06.02.2013 um 16:10 schrieb Eric Noulard :

> 2013/2/6 NoRulez :
>> Sorry, i forgot to say that I'm using CMake 2.8.7?
>> 
>> Is there a chance to do so?
> 
> There is currently no way to do that.
> Why would it be useful for CPack to partially build the packages?
> 
> Do you have an example?
> -- 
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

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

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

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

Re: [CMake] Running CPack and ignore exit codes

[NoRulez]

Sorry, i forgot to say that I'm using CMake 2.8.7?

Is there a chance to do so?

Thanks in advance

Am 05.02.2013 um 14:17 schrieb NoRulez :

> Hi,
> 
> when i run cpack, then it breaks after the first error.
> 
> Is there a way (For NMake for example) to run "nmake /I" to ignore exit codes 
> and build as much as possible?
> 
> Thanks in advance
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

[CMake] Release date for CMake 2.8.11?

[NoRulez]

Hi,

does anybody know the new release date for CMake 2.8.11?
In Mantis the date was scheduled for 2013-01-30.

Thanks in advance
--

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] Running CPack and ignore exit codes

[NoRulez]

Hi,

when i run cpack, then it breaks after the first error.

Is there a way (For NMake for example) to run "nmake /I" to ignore exit codes 
and build as much as possible?

Thanks in advance
--

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 2.8.10 available for download

[norulez]

Hello David,

I had also a question for the new release.
How can I create a valid VS2012 solution under windows 8?

I need to call "cmake -G "Visual Studio 11" ..\source" twice to get a solution 
file.
The first time I get messages which tells that there is an unknown CXX compiler 
and:

-- Looking for Q_WS_WIN
CMake Error at C:/Program Files (x86)/CMake 
2.8/share/cmake-2.8/Modules/CMakeCXXInformation.cmake:37 
(get_filename_component):
get_filename_component called with incorrect number of arguments

However, after the solution is created an opened, then some sub projects are 
valid, but the others are incompatible sub projects. (e.g. "ALL_BUILD 
(incompatible)"). The same works great under Windows 7 with and older cmake 
version such as 2.8.7.

Did I miss something?

Thanks in advance

Best Regards

P.S.: I use CMake 2.8.10, Windows 8 Pro and VS 2012 Express for Windows 8



Am 02.11.2012 um 10:38 schrieb David Cole :

> The scripts that buld the CMake release binaries are in 
> CMake/Utilities/Release.
> 
> If you have a system-installed OpenSSL, then setting the cache
> variable CMAKE_USE_OPENSSL should be sufficient.
> 
> If not, and you have a custom built openssl, you need to set the
> following variables as well:
> 
> CMAKE_USE_OPENSSL:BOOL=ON
> OPENSSL_CRYPTO_LIBRARY:FILEPATH=/path/to/openssl-1.0.1c-install/lib/libcrypto.a
> OPENSSL_INCLUDE_DIR:PATH=/path/to/openssl-1.0.1c-install/include
> OPENSSL_SSL_LIBRARY:FILEPATH=/path/to/openssl-1.0.1c-install/lib/libssl.a
> 
> If you still have problems after this, send along whatever error
> message you're getting...
> 
> 
> HTH,
> David
> 
> 
> On Fri, Nov 2, 2012 at 12:24 AM, Orion Poplawski  wrote:
>> On 10/31/2012 07:45 PM, David Cole wrote:
>>> 
>>> On behalf of myself, Ken, Bill, Brad, Alex, Eike, Steve, Eric, Zach,
>>> Ben and the rest of the CMake team from all around the world, we are
>>> pleased to announce that CMake 2.8.10 is now available for download
>>> at:
>>> 
>>>   http://www.cmake.org/files/v2.8/?C=M;O=D
>>> 
>>> It is also available from the usual download links found on the CMake web
>>> site:
>>> 
>>>   http://www.cmake.org/cmake/resources/software.html
>>> 
>>> Some of the notable changes in this release are:
>>> 
>>>  - file(DOWNLOAD now handles "https" URLs -- the pre-built binaries
>>> available from Kitware link to OpenSSL
>> 
>> 
>> What is required to enable this when building cmake?  It does not appear
>> that:
>> 
>> ../bootstrap --prefix=/usr --datadir=/share/cmake
>> --docdir=/share/doc/cmake-2.8.10 --mandir=/share/man --system-libs
>> --parallel=2 --qt-gui -- -DCMAKE_USE_OPENSSL=TRUE
>> 
>> is sufficient.
>> 
>> TIA,
>> 
>>  Orion
>> 
>> --
>> Orion Poplawski
>> Technical Manager 303-415-9701 x222
>> NWRA/CoRA DivisionFAX: 303-415-9702
>> 3380 Mitchell Lane  or...@cora.nwra.com
>> Boulder, CO 80301  http://www.cora.nwra.com
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

[CMake] Different library versions for sub projects?

[norulez]

Hello,

is it possible to use different libraries for sub projects?
For example if a sub project needs dynamic linked boost 1.48 library and a 
other sub project needs static linked boost 1.51 library.

The same could be for Qt projects too.

Thanks in advance
Best Regards
--

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 can't find the correct Qt installation paths

[NoRulez]

Hello,when I install Qt to the location C:\Qt\QtSDK and then I run cmake, everything is working fine.But if I rename the directory to C:\Qt\QtSDL then cmake have problems to find Qt because qmake.exe isn't patched.In qmake.exe the path to the libraries are set to "C:\Qt\QtSDK\..." which is also used for the query command.So, if i patch qmake.exe (Rename the directory in the qmake.exe file => works only if the length of the directory name is the same),cmake works fine but the problem is, that cmake tries to find out the location of libraries and so on from the query, which is wrong in my oppinion,because if I want to move the custom build Qt library to another location then cmake doesn't find Qt.For example when I rename the directory to C:\Qt\QtSDL and run qmake -query:QT_INSTALL_PREFIX:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingwQT_INSTALL_DATA:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\QT_INSTALL_DOCS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\docQT_INSTALL_HEADERS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\includeQT_INSTALL_LIBS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\libQT_INSTALL_BINS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\binQT_INSTALL_PLUGINS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\pluginsQT_INSTALL_IMPORTS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\importsQT_INSTALL_TRANSLATIONS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\translationsQT_INSTALL_CONFIGURATION:C:/Qt/QtSDK/Desktop/Qt/4.8.1/mingwQT_INSTALL_EXAMPLES:C:\Qt\QtSDK\Examples\4.7QT_INSTALL_DEMOS:C:\Qt\QtSDK\Demos\4.7QMAKE_MKSPECS:C:\Qt\QtSDK\Desktop\Qt\4.8.1\mingw\\mkspecsQMAKE_VERSION:2.01aQT_VERSION:4.8.1When I run it from the drive letter D:, E:, F:, ..., then the result is the same.Best RegardsNoRulez--

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 creates incompatible VS 2012 (VS 11) solution

[NoRulez]

Hello Bill,i think the problem is solved. CMake generates valid VS 2012 / VS 11 solution files.The problem is that VS 2012 Express doesn't support desktop applications, only metro style apps.I've tested the same solution file with VS 2012 Ultimate (http://www.microsoft.com/visualstudio/11/de-de/downloads#vs),with this version the solution is working as expected.Double clicking on the *.sln file in the explorer opens visual studio and loads the projects. Best RegardsAm 03. August 2012 um 23:58 schrieb Bill Hoffman :On 8/3/2012 5:46 PM, noru...@me.com wrote: > I read other posts and i think it has to do with that, that i would like to double click on the *.sln file to open it. > > I don't know if this should already be fixed in 2.8.8 >  Can you create a project via the VS IDE and send me the project files.  Also, send me the project files for one generated by CMake.  Thanks.   > Best Regards > > Am 03.08.2012 um 22:47 schrieb Klaim - Joël Lamotte : > >> I'm using CMake 2.8.8 to generate VS2012 RC projects in Win 7 (with last updates), >> I have no such problem. The only problems I have seems to have been fixed in the trunk for CMake 2.8.9 but I didn't try. >> >> I never seen the problem you present, but if you use the same version of CMake than me, then it's related to the OS or the version of VS that you use... >> >> Joel Lamotte >> > -- > > 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 >   --  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.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] CMake creates incompatible VS 2012 (VS 11) solution

[norulez]

I read other posts and i think it has to do with that, that i would like to 
double click on the *.sln file to open it.

I don't know if this should already be fixed in 2.8.8

Best Regards

Am 03.08.2012 um 22:47 schrieb Klaim - Joël Lamotte :

> I'm using CMake 2.8.8 to generate VS2012 RC projects in Win 7 (with last 
> updates), 
> I have no such problem. The only problems I have seems to have been fixed in 
> the trunk for CMake 2.8.9 but I didn't try.
> 
> I never seen the problem you present, but if you use the same version of 
> CMake than me, then it's related to the OS or the version of VS that you 
> use...
> 
> Joel Lamotte
> 
--

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 creates incompatible VS 2012 (VS 11) solution

[NoRulez]

Hello,

I tried to create a visual studio 2012 solution under Windows 8 Release Preview.
This solution contains for demo purpose only a main.cpp file

I tried the 32 bit variant and the
cmake -G "Visual Studio 11" ..\source

64 bit variant:
cmake -G "Visual Studio 11 Win64" ..\source

After I load the *.sln file with Visual Studio I get the following result:

ALL_BUILD (incompatible)
DemoPrj (load failed)
ZERO_CHECK (incompatible)

Here is the CMakeLists.txt file:

project(DemoPrj)

add_executable(DemoPrj main.cpp)
target_link_libraries(DemoPrj)


And here is the main.cpp:

int main(int argc, char* argv[]) {
    return 0;
}I use the following:cmake 2.8.8Visual Studio 2012 RCWindows 8 Release PreviewIs Visual Studio 2012 not supported yet?Thanks in advanceBest Regards

--

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] Strange behavior with Nightly builds

[norulez]

Hello Richard,
hello David,

sorry for the long response time, I tried to get it working but it doesn't work.
I'm trying to describe it in a more detail:

1.) CTestScript.cmake is now configured with set(CTEST_NIGHTLY_START_TIME 
"3:00:00 UTC")
2.) the windows slave is configured as GMT+2 in the scheduler at every minute 
(continuous) between 6am and 10pm and nightly at 1 am (UTC-2 for europe, which 
is described at http://www.kitware.com/blog/home/post/77)
3.) the last revision at 4pm (2012-07-01) is for e.g. 80.
4.) the nightly build at 1am (2012-07-02) removes all files in the build 
directory and update/configure the project.
At this point the revision should be 80 because it is the last commit of the 
previous day (at 4 pm, but could also be 6pm or 7pm on 2012-07-01) => HEAD (for 
2012-07-01)
! And here is the problem, the revision which is checked out isn't 80, it 
is a revision before 80 (e.g. 79, 75, ...)
5.) Continuous build for a developer commit on 2012-07-02 at 6 am with revision 
81

step 5 is the expected result, but the real thing is, that the Continous build 
at 6am is done without a developer commit (for revision 80) because of the 
failed nightly build (commit was < 80). 


Much thanks in advance

Best Regards


Am 22.06.2012 um 14:14 schrieb Richard Wackerbarth :

> I made a minor error in my previous posting. I forgot the first run as 
> continuous starts up on the second day.
> I have make the correction inline below.
> 
> On Jun 22, 2012, at 2:09 AM, NoRulez wrote:
> 
>> Hello Richard,
>> 
>> >> What is the configured cutoff time for Nightly runs?
>> Did you mean the nightly build time?
> 
> I mean this value (for example in CTestConfig.cmake)
> such as:
> 
> set(CTEST_NIGHTLY_START_TIME "21:00:00 EDT")
> or
> set(CTEST_NIGHTLY_START_TIME "1:00:00 UTC")
> 
> But let's be certain that we both are talking about the consistent times, 
> namely UTC.
> 
>> >> During which hours does the "continuous" builder run?
>> Between 6 am and 10 pm
>  (UTC ?)
> 
> (Note A) See below
> 
>> >> When does the "nightly" builder run?
>> Nightly build time is configured for 23:00 UTC (11 pm)
>> 
>> >> Which builds do you expect to be posted to "continuous"?
>> At 10 pm and at 6 pm in the morning (next day) the commit should be e.g. 48
> 
> I interpret (Note A) to indicate that you should expect the following runs:
> 5, 6, 7, ... , 21, 29 - 45, 53 - 69, etc.
> Commit 5 is processed when the builder restarts at 6 AM.
> Commit 6 is processed shortly after 6:15 AM
> The builder shuts down for the night before Commit 22 is posted at 10:15 PM
> 
>> >> Which builds do you expect to be posted to "nightly"?
>> At 11 pm the commit should be e.g. 48 (HEAD revision) which means the last 
>> commit from the current day
> 
> At 11 PM, the last commit was the one made at 10:15 PM, namely 22, 46, 70, ...
> 
>> e.g.: If the last commit from the 21.06.2012 is at 12:30 am
> 
> I don't know how you expect 12:30 AM to be the last commit of the day. The 
> day started only 30 minutes earlier.
> 
>> and has the commit 32, then the nightly build from the 21.06.2012 at 23:00 
>> (11 pm) has (should have) the commit 32 too.
> 
> This doesn't make sense. (And please follow my assumptions -- all of the 
> commits in my scenario occur at 15 minutes past the hour. There are no 
> commits made at 12:30 am)
> 
> Please draw your timeline, mark all of the actions and revise your 
> expectations.
> 
>> The only difference is that the nightly builds starts from an empty build 
>> directory (the directory content are removed).
> 
> A typical distinction.
> 
>> Thanks in advance
>> 
>> Best Regards
>> 
>> 
>> Am 21. Jun 2012 um 20:20 schrieb Richard Wackerbarth :
>> 
>>> From reading this, I get the distinct impression that your are not 
>>> interpreting the meaning of "nightly" in the same way that the rest of us 
>>> are doing so.
>>> 
>>> Let's assume the following:
>>> 
>>> At 15 minutes past each hour, a new commit is added to the repository.
>>> 
>>> For the sake of description, the "zeroth" commit happens at 12:15 AM on 
>>> June 21
>>> Commit #1 is at 1:15 AM,
>>> ...
>>> Commit #18 is at 6:15 PM,
>>> ...
>>> Commit #22 is at 10:15 PM,
>>> Commit #23 is at 11:15 PM,
>>> Commit #24 is at 12:15 AM on June 22
>>> ...
>>> Commit #47 is at 11:15 PM,
>>> Commit #48 is at 12:15 AM on June 23
>>> ...
&g

[CMake] Bug 12630 possible for CMake 2.8.9?

[norulez]

Hello,

is there a chance to get http://public.kitware.com/Bug/view.php?id=12630 into 
2.8.9?

Best Regards
--

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] Problems with CPack 2.8.8

[NoRulez]

Because of the long time... this was because first I thought it was my fault.It would be great if the old behavior could be restored.Best RegardsAm 03. Juli 2012 um 13:35 schrieb David Cole :Looks like we let the default command line behavior get trounced when we added the new cpack --help* stuff... Guess we don't have a test for that.  To loop over all configure CPack generators, you can still use the command line:  cpack -C CPackConfig.cmake  But:  cpack  just by itself simply spits out the help text now.  Should we put it back to the way it was in 2.8.7, or should we leave it the way it is now in 2.8.8?  Seems like 3 months is a pretty long time before anybody noticed a change in behavior like this one.   Thanks for the report. And further comments will be appreciated.  David   On Tue, Jul 3, 2012 at 4:28 AM, NoRulez <noru...@me.com> wrote: > Hello, > > i've upgraded my cmake installation from 2.8.7 to 2.8.8. After the upgrade > the cpack has an unwanted behavior. > > When i run cpack from the build directory (in cpack 2.8.7) then cpack > iterates over all configured CPACK_GENERATORs and creates the > installer/archives. > But with cpack 2.8.8 I get only the options from cpack. > Is this a bug or did I need to configure something else in 2.8.8? > > cpack version 2.8.8 > Usage > >   cpack -G  [options] > > Options >   -G   = Use the specified generator to generate >     package. >   -C   = Specify the project configuration >   -D =    = Set a CPack variable. >   --config   = Specify the config file. >   --verbose,-V    = enable verbose output >   --debug = enable debug output (for CPack developers) >   -P    = override/define CPACK_PACKAGE_NAME >   -R     = override/define CPACK_PACKAGE_VERSION >   -B   = override/define CPACK_PACKAGE_DIRECTORY >   --vendor   = override/define CPACK_PACKAGE_VENDOR >   --help-command cmd [file]   = Print help for a single command and exit. >   --help-command-list [file]  = List available commands and exit. >   --help-commands [file]  = Print help for all commands and exit. >   --help-variable var [file]  = Print help for a single variable and exit. >   --help-variable-list [file] = List documented variables and exit. >   --help-variables [file] = Print help for all variables and exit. >   --copyright [file]  = Print the CMake copyright and exit. >   --help,-help,-usage,-h,-H,/?= Print usage information and exit. >   --help-full [file]  = Print full help and exit. >   --help-html [file]  = Print full help in HTML format. >   --help-man [file]   = Print full help as a UNIX man page and exit. >   --version,-version,/V [file]= Show program name/version banner and exit. > > Generators >   NSIS    = Null Soft Installer >   STGZ    = Self extracting Tar GZip compression >   TBZ2    = Tar BZip2 compression >   TGZ     = Tar GZip compression >   TZ  = Tar Compress compression >   ZIP = ZIP file format > > Best Regards > NoRulez > > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake--

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] Problems with CPack 2.8.8

[NoRulez]

Hello,i've upgraded my cmake installation from 2.8.7 to 2.8.8. After the upgrade the cpack has an unwanted behavior.When i run cpack from the build directory (in cpack 2.8.7) then cpack iterates over all configured CPACK_GENERATORs and creates the installer/archives.But with cpack 2.8.8 I get only the options from cpack.Is this a bug or did I need to configure something else in 2.8.8?cpack version 2.8.8Usage  cpack -G  [options]Options  -G   = Use the specified generator to generate    package.  -C   = Specify the project configuration  -D =    = Set a CPack variable.  --config   = Specify the config file.  --verbose,-V    = enable verbose output  --debug = enable debug output (for CPack developers)  -P    = override/define CPACK_PACKAGE_NAME  -R     = override/define CPACK_PACKAGE_VERSION  -B   = override/define CPACK_PACKAGE_DIRECTORY  --vendor   = override/define CPACK_PACKAGE_VENDOR  --help-command cmd [file]   = Print help for a single command and exit.  --help-command-list [file]  = List available commands and exit.  --help-commands [file]  = Print help for all commands and exit.  --help-variable var [file]  = Print help for a single variable and exit.  --help-variable-list [file] = List documented variables and exit.  --help-variables [file] = Print help for all variables and exit.  --copyright [file]  = Print the CMake copyright and exit.  --help,-help,-usage,-h,-H,/?= Print usage information and exit.  --help-full [file]  = Print full help and exit.  --help-html [file]  = Print full help in HTML format.  --help-man [file]   = Print full help as a UNIX man page and exit.  --version,-version,/V [file]= Show program name/version banner and exit.Generators  NSIS    = Null Soft Installer  STGZ    = Self extracting Tar GZip compression  TBZ2    = Tar BZip2 compression  TGZ = Tar GZip compression  TZ  = Tar Compress compression  ZIP = ZIP file formatBest RegardsNoRulez--

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] Strange behavior with Nightly builds

[NoRulez]

Hello Richard,>> What is the configured cutoff time for Nightly runs?Did you mean the nightly build time?>> During which hours does the "continuous" builder run?Between 6 am and 10 pm>> When does the "nightly" builder run?Nightly build time is configured for 23:00 UTC (11 pm)>> Which builds do you expect to be posted to "continuous"?At 10 pm and at 6 pm in the morning (next day) the commit should be e.g. 48>> Which builds do you expect to be posted to "nightly"?At 11 pm the commit should be e.g. 48 (HEAD revision) which means the last commit from the current daye.g.: If the last commit from the 21.06.2012 is at 12:30 am and has the commit 32, then the nightly build from the 21.06.2012 at 23:00 (11 pm) has (should have) the commit 32 too.The only difference is that the nightly builds starts from an empty build directory (the directory content are removed).Thanks in advanceBest RegardsAm 21. Jun 2012 um 20:20 schrieb Richard Wackerbarth :From reading this, I get the distinct impression that your are not interpreting the meaning of "nightly" in the same way that the rest of us are doing so.  Let's assume the following:  At 15 minutes past each hour, a new commit is added to the repository.  For the sake of description, the "zeroth" commit happens at 12:15 AM on June 21 Commit #1 is at 1:15 AM, ... Commit #18 is at 6:15 PM, ... Commit #22 is at 10:15 PM, Commit #23 is at 11:15 PM, Commit #24 is at 12:15 AM on June 22 ... Commit #47 is at 11:15 PM, Commit #48 is at 12:15 AM on June 23 ...  etc.  Further, assume that a build requires 5 minutes to run.  ===  Now it terms of those assumptions, please tell me:  What is the configured cutoff time for Nightly runs? During which hours does the "continuous" builder run? When does the "nightly" builder run?  Which builds do you expect to be posted to "continuous"? Which builds do you expect to be posted to "nightly"?  ===  With those answers, perhaps I will be able to understand what you expect and help explain how you might achieve it.  Richard  On Jun 21, 2012, at 1:29 AM, NoRulez wrote:  > Has no one an idea on how to do so or is such functionality missing? >  > Thanks in advance >  > Best Regards >  >  > Am 15. Jun 2012 um 08:38 schrieb NoRulez <noru...@me.com>: >  >> Hello David, >>  >> but the problem is, that the timestamp is one day behind, so this doesn't work and I get previous revisions. (Our nightly build starts at 23:00 and not at 1 am) >> However is there a way to update to the HEAD revision? >>  >> Best Regards --

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] Strange behavior with Nightly builds

[NoRulez]

Has no one an idea on how to do so or is such functionality missing?Thanks in advanceBest RegardsAm 15. Jun 2012 um 08:38 schrieb NoRulez :Hello David,but the problem is, that the timestamp is one day behind, so this doesn't work and I get previous revisions. (Our nightly build starts at 23:00 and not at 1 am)However is there a way to update to the HEAD revision?Best RegardsAm 14. Jun 2012 um 15:05 schrieb David Cole :On Thu, Jun 14, 2012 at 3:07 AM, NoRulez <noru...@me.com> wrote:I think i fond the problem, but I don't know how to solve it.I have the following defined in the CTestScript.cmake:if(${NEED_REPOSITORY_CHECKOUT})     set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} co ${REPOSITORY_URL} \"${CTEST_SOURCE_DIRECTORY}\" -r HEAD") else()    set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} update") endif()The CTEST_CHECKOUT_COMMAND should only be used for checkout. It should not be used for update. which seems to be correct, but in CDash the update command looks like: Update Command: "C:/Program Files/Subversion/bin/svn.exe" "update" "--non-interactive" "-r{2012-06-12 23:00:00 +}"This comes from the ctest_update command, and it intentionally uses the nightly date stamp to guarantee a consistent snapshot across clients. Otherwise, you could get different source trees on different machines depending on the timing of running the ctest_update command. From the svn documentation: If no revision is given, bring working copy up-to-date with HEAD rev.  Else synchronize working copy to revision given by -r.So, how could I remove the last command line argument ("-r{2012-06-12 23:00:00 +0000}")?Thanks in advanceBest RegardsAm 06. Jun 2012 um 23:31 schrieb Richard Wackerbarth :> NoRulez,  A better question is "Why was revision 8 not included in the nightly run?" Using one source tree for both continuous and nightly assumes that there will be no continuous runs between the last update incorporated in the nightly run and the time at which the nightly run is performed. It appears that you are not suspending continuous runs between the nightly epoch and the time that you perform the nightly run.  By following Stefan's scheme of two complete trees, each tree meets the above criteria because the nightly version never does continuous runs and the continuous version never does nightly runs.  On Jun 6, 2012, at 3:49 PM, Stefan Reuschl wrote:  > Am 06.06.2012, 08:57 Uhr, schrieb NoRulez <noru...@me.com>: >  >> Hello, >>  >> here is the build process of the build server: >>  >> 1.) e.g.: last commit at 03:00 pm (svn revision 8) => build is ok >> 2.) The nightly build starts at 10:00 pm (svn revision 7) => build is ok >> Why is the svn revision before the last commit, it should be 8? >> 3.) In the morning (~ 06:00 am) a continuous build is triggered (SVN revision 8) => build is ok >> Why is this continuous build triggered? >>  >> The folder structure for the project on the build server is the following: >>  >> MyProject >> | >> +build >> | >> +source >>  >> In the CTestScript.cmake if have the following: >>  >> if(MODEL STREQUAL "Nightly") >> file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}") >> set(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE) >> endif() >>  >> According to my understanding the build directory should be removed and newly created. >> But I don't know why the revisions are changed during the nightly build. >  > That's because the svn update for both Nightly and Continuous are done on > the common source tree. > The solution is to have independent source trees: >  > MyProject > | > +Continuous > | | > | +build > | | > | +source > | > +Nightly > | | > | +build > | | > | +source >  > Regards, > Stefan > -- >  > 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 --  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 

Re: [CMake] Strange behavior with Nightly builds

[NoRulez]

Hello David,but the problem is, that the timestamp is one day behind, so this doesn't work and I get previous revisions. (Our nightly build starts at 23:00 and not at 1 am)However is there a way to update to the HEAD revision?Best RegardsAm 14. Jun 2012 um 15:05 schrieb David Cole :On Thu, Jun 14, 2012 at 3:07 AM, NoRulez <noru...@me.com> wrote:I think i fond the problem, but I don't know how to solve it.I have the following defined in the CTestScript.cmake:if(${NEED_REPOSITORY_CHECKOUT})     set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} co ${REPOSITORY_URL} \"${CTEST_SOURCE_DIRECTORY}\" -r HEAD") else()    set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} update") endif()The CTEST_CHECKOUT_COMMAND should only be used for checkout. It should not be used for update. which seems to be correct, but in CDash the update command looks like: Update Command: "C:/Program Files/Subversion/bin/svn.exe" "update" "--non-interactive" "-r{2012-06-12 23:00:00 +}"This comes from the ctest_update command, and it intentionally uses the nightly date stamp to guarantee a consistent snapshot across clients. Otherwise, you could get different source trees on different machines depending on the timing of running the ctest_update command. From the svn documentation: If no revision is given, bring working copy up-to-date with HEAD rev.  Else synchronize working copy to revision given by -r.So, how could I remove the last command line argument ("-r{2012-06-12 23:00:00 +0000}")?Thanks in advanceBest RegardsAm 06. Jun 2012 um 23:31 schrieb Richard Wackerbarth :> NoRulez,  A better question is "Why was revision 8 not included in the nightly run?" Using one source tree for both continuous and nightly assumes that there will be no continuous runs between the last update incorporated in the nightly run and the time at which the nightly run is performed. It appears that you are not suspending continuous runs between the nightly epoch and the time that you perform the nightly run.  By following Stefan's scheme of two complete trees, each tree meets the above criteria because the nightly version never does continuous runs and the continuous version never does nightly runs.  On Jun 6, 2012, at 3:49 PM, Stefan Reuschl wrote:  > Am 06.06.2012, 08:57 Uhr, schrieb NoRulez <noru...@me.com>: >  >> Hello, >>  >> here is the build process of the build server: >>  >> 1.) e.g.: last commit at 03:00 pm (svn revision 8) => build is ok >> 2.) The nightly build starts at 10:00 pm (svn revision 7) => build is ok >> Why is the svn revision before the last commit, it should be 8? >> 3.) In the morning (~ 06:00 am) a continuous build is triggered (SVN revision 8) => build is ok >> Why is this continuous build triggered? >>  >> The folder structure for the project on the build server is the following: >>  >> MyProject >> | >> +build >> | >> +source >>  >> In the CTestScript.cmake if have the following: >>  >> if(MODEL STREQUAL "Nightly") >> file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}") >> set(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE) >> endif() >>  >> According to my understanding the build directory should be removed and newly created. >> But I don't know why the revisions are changed during the nightly build. >  > That's because the svn update for both Nightly and Continuous are done on > the common source tree. > The solution is to have independent source trees: >  > MyProject > | > +Continuous > | | > | +build > | | > | +source > | > +Nightly > | | > | +build > | | > | +source >  > Regards, > Stefan > -- >  > 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 --  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] Strange behavior with Nightly builds

[NoRulez]

I think i fond the problem, but I don't know how to solve it.I have the following defined in the CTestScript.cmake:if(${NEED_REPOSITORY_CHECKOUT})    set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} co ${REPOSITORY_URL} \"${CTEST_SOURCE_DIRECTORY}\" -r HEAD")else()    set(CTEST_CHECKOUT_COMMAND "${CTEST_UPDATE_COMMAND} update")endif()which seems to be correct, but in CDash the update command looks like:Update Command: "C:/Program Files/Subversion/bin/svn.exe" "update" "--non-interactive" "-r{2012-06-12 23:00:00 +}"From the svn documentation: If no revision is given, bring working copy up-to-date with HEAD rev. Else synchronize working copy to revision given by -r.So, how could I remove the last command line argument ("-r{2012-06-12 23:00:00 +}")?Thanks in advanceBest RegardsAm 06. Jun 2012 um 23:31 schrieb Richard Wackerbarth :> NoRulez,  A better question is "Why was revision 8 not included in the nightly run?" Using one source tree for both continuous and nightly assumes that there will be no continuous runs between the last update incorporated in the nightly run and the time at which the nightly run is performed. It appears that you are not suspending continuous runs between the nightly epoch and the time that you perform the nightly run.  By following Stefan's scheme of two complete trees, each tree meets the above criteria because the nightly version never does continuous runs and the continuous version never does nightly runs.  On Jun 6, 2012, at 3:49 PM, Stefan Reuschl wrote:  > Am 06.06.2012, 08:57 Uhr, schrieb NoRulez <noru...@me.com>: >  >> Hello, >>  >> here is the build process of the build server: >>  >> 1.) e.g.: last commit at 03:00 pm (svn revision 8) => build is ok >> 2.) The nightly build starts at 10:00 pm (svn revision 7) => build is ok >> Why is the svn revision before the last commit, it should be 8? >> 3.) In the morning (~ 06:00 am) a continuous build is triggered (SVN revision 8) => build is ok >> Why is this continuous build triggered? >>  >> The folder structure for the project on the build server is the following: >>  >> MyProject >> | >> +build >> | >> +source >>  >> In the CTestScript.cmake if have the following: >>  >> if(MODEL STREQUAL "Nightly") >> file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}") >> set(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE) >> endif() >>  >> According to my understanding the build directory should be removed and newly created. >> But I don't know why the revisions are changed during the nightly build. >  > That's because the svn update for both Nightly and Continuous are done on > the common source tree. > The solution is to have independent source trees: >  > MyProject > | > +Continuous > | | > | +build > | | > | +source > | > +Nightly > | | > | +build > | | > | +source >  > Regards, > Stefan > -- >  > 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 --

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] Strange behavior with Nightly builds

[NoRulez]

Hello,here is the build process of the build server: 1.) e.g.: last commit at 03:00 pm (svn revision 8) => build is ok2.) The nightly build starts at 10:00 pm (svn revision 7) => build is ok    Why is the svn revision before the last commit, it should be 8?3.) In the morning (~ 06:00 am) a continuous build is triggered (SVN revision 8) => build is ok    Why is this continuous build triggered?The folder structure for the project on the build server is the following:MyProject    |    +build    |    +sourceIn the CTestScript.cmake if have the following:if(MODEL STREQUAL "Nightly")    file(REMOVE_RECURSE "${CTEST_BINARY_DIRECTORY}")    set(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)endif()According to my understanding the build directory should be removed and newly created.But I don't know why the revisions are changed during the nightly build.Can anyone please helpThanks in advanceBest RegardsNoRulez--

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] Meaning of CTEST_ENVIRONMENT

[NoRulez]

Hello,in an example i saw that CTEST_ENVIRONMENT is used to set specific paths.I tried the same in my CTestScript, but this doesn't work. Can anybody explain me why variant 1 is working and variant 2 is not?1.Variant:set(ENV{QTDIR} "C:\\Qt")set(ENV{PATH} "$ENV{QTDIR};$ENV{QTDIR}\\bin;$ENV{PATH}")2.Variant:set(CTEST_ENVIRONMENT "QTDIR=C:\\Qt"  "PATH=%QTDIR%\;%QTDIR%\\bin\;%PATH%")Thanks in advanceBest RegardsNoRulez--

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] Problems with nightly builds

[NoRulez]

Hello,i've a build server running based on http://www.cmake.org/Wiki/CTest:Buildserver.The build slave is a Windows Server 2003 R2.So, what I try to archive is the following:Each time a developer check in files/changes, then the continuous build (every minute) starts to with the last changes found. => OKBut in the nightly build I want to run a clean build (As building the project for the first time). It seems that the nightly build is based on the last continuous build.How can I avoid this behavior and/or change them?Thanks in advanceBest RegardsNoRulez
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack: Installing applications in separate folders (NSIS)

[norulez]

I got it to work.

Under windows/NSIS I set the destination to "../CustomDir" instead of 
$CustomDir.
With this and a custom nsis script which knows the location it is possible to 
run CPack.

In the NSIS script I've the following
Var $CustomDir="@CPACK_TEMPORARY_DIRECTORY@\..\CustomDir"

After this I can install files from this directory too.

The directory content after the preinstall:
.../_CPack_Packages/win32/NSIS/myproject.1.0.0.1/
.../_CPack_Packages/win32/NSIS/CustomDir/
.../_CPack_Packages/win32/NSIS/project.nsi
.
.
.

@Eric, @David: Thank you very much

Best Regards


Am 22.05.2012 um 00:38 schrieb Eric Noulard :

> 2012/5/21 David Cole :
>> On Mon, May 21, 2012 at 2:05 PM,  wrote:
>>> 
>>> But what about other systems like linux. If I have an executable and
>>> shared libraries for example.
>>> Then it is possible to install it under /opt/myproject, but it is not
>>> possible to install the executable under /usr/bin and the shared libraries
>>> under /usr/lib? Or did I misunderstood something?
>> 
>> 
>> But you don't build an NSIS installer based on those.
> 
> And installing lib in /usr/lib and exe in /usr/bin IS possible
> because the 2 path shares the /usr prefix.
> 
> On Linux if you build an RPM or DEB package which contains various
> prefix (/usr /opt etc..) you either get a non relocatable package
> or decide that some files are "special" like config files.
> 
> but David is right this does not work with NSIS.
> 
>>> Sorry, for simple installers the default NSIS template is great, but for
>>> customized ones it seems to be very difficult, isn't it?
> 
> As difficult as it is with NSIS alone :-]
> 
>> Yes, you're correct. It takes some effort if you are not installing
>> everything underneath the directory that the end user chooses for your final
>> location.
>> 
>> It's quite good for "simple installers" and "component-based installers" --
>> beyond that, and especially putting things outside the location chosen by
>> the end user ... you're on your own.
> 
> If you do have 2 separate unrelated installation prefixes
> may be you can just build 2 NSIS installers
> (which contains only one prefix)
> using CPack twice out of 2 differents configurations of the same project
> 
> Or craft your own project.nsi file.
> 
> -- 
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack: Installing applications in separate folders (NSIS)

[norulez]

I think one solution could be that the files must be copied with 
add_custom_command's, then run configure_file with the NSIS template to be able 
to use @ variables and then another add_custom_command to run NSIS.

Is there maybe a simpler solution or is this the correct way?


Am 21.05.2012 um 20:05 schrieb noru...@me.com:

> But what about other systems like linux. If I have an executable and shared 
> libraries for example.
> Then it is possible to install it under /opt/myproject, but it is not 
> possible to install the executable under /usr/bin and the shared libraries 
> under /usr/lib? Or did I misunderstood something?
> 
> Sorry, for simple installers the default NSIS template is great, but for 
> customized ones it seems to be very difficult, isn't it?
> 
> 
> Best Regards
> 
> Am 21.05.2012 um 19:27 schrieb David Cole :
> 
>> The install rule:
>> 
>>   install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION 
>> $CustomDir)
>> 
>> doesn't make sense because $CustomDir is not known at CMake-time or even at 
>> build-time or install-time. It's not known except to NSIS at packaging time.
>> 
>> make install runs before NSIS runs.
>> 
>> Sounds like you need a completely custom installer -- if you have installed 
>> files that are not contained within the make install tree prefix, then you 
>> cannot use the recursive "install all files from one root" technique in the 
>> NSIS script that CPack uses by default.
>> 
>> 
>> We generally encourage and expect a "re-locatable" install tree to be used 
>> with the CPack built NSIS installers. (i.e. -- no matter where the end-user 
>> finally installs your package, they will be able to run the installed 
>> programs just fine.) That's why the entire install tree is copied using the 
>> following:
>> 
>>   this->SetOptionIfNotSet("CPACK_NSIS_FULL_INSTALL", 
>> "File /r \"${INST_DIR}\\*.*\"");
>> 
>> That results in the following generated in project.nsi:
>> 
>>   File /r "${INST_DIR}\*.*"
>> 
>> which installs all files and directories recursively (from your make install 
>> tree) to the installation directory chosen by the end user of your 
>> installation program.
>> 
>> 
>> This stuff is not easy, especially when we can't see your code.
>> 
>> Cheers, (& good luck),
>> David
>> 
>> 
>> On Mon, May 21, 2012 at 12:39 PM, NoRulez  wrote:
>> Hi,
>> 
>> I know that the install commands collect files and copy them into the 
>> temporary cpack directory for the specified generator.
>> How is it possible to install an application for example into those folders:
>> C:\myapp
>> C:\somefolder
>> 
>> I defined 'Var CustomDir="C:\somefolder"' in the NSIS template.
>> 
>> When I then use the following in the CMakeLists.txt:
>> install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION 
>> $CustomDir)
>> 
>> Then the files are installed in 
>> _CPACK_PACKAGES/NSIS/myproject_1.0.0.1/$CustomDir.
>> The generated project.nsi has the content: $INSTDIR\$CustomDir\...
>> 
>> How can I avoid that $INSTDIR\ is added, or did I need to use the install 
>> command in a different way?
>> 
>> Thanks in advance
>> 
>> Best Regards
>> NoRulez
>> 
>> --
>> 
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the CMake FAQ at: 
>> http://www.cmake.org/Wiki/CMake_FAQ
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>> 
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack: Installing applications in separate folders (NSIS)

[norulez]

But what about other systems like linux. If I have an executable and shared 
libraries for example.
Then it is possible to install it under /opt/myproject, but it is not possible 
to install the executable under /usr/bin and the shared libraries under 
/usr/lib? Or did I misunderstood something?

Sorry, for simple installers the default NSIS template is great, but for 
customized ones it seems to be very difficult, isn't it?


Best Regards

Am 21.05.2012 um 19:27 schrieb David Cole :

> The install rule:
> 
>   install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION 
> $CustomDir)
> 
> doesn't make sense because $CustomDir is not known at CMake-time or even at 
> build-time or install-time. It's not known except to NSIS at packaging time.
> 
> make install runs before NSIS runs.
> 
> Sounds like you need a completely custom installer -- if you have installed 
> files that are not contained within the make install tree prefix, then you 
> cannot use the recursive "install all files from one root" technique in the 
> NSIS script that CPack uses by default.
> 
> 
> We generally encourage and expect a "re-locatable" install tree to be used 
> with the CPack built NSIS installers. (i.e. -- no matter where the end-user 
> finally installs your package, they will be able to run the installed 
> programs just fine.) That's why the entire install tree is copied using the 
> following:
> 
>   this->SetOptionIfNotSet("CPACK_NSIS_FULL_INSTALL", 
> "File /r \"${INST_DIR}\\*.*\"");
> 
> That results in the following generated in project.nsi:
> 
>   File /r "${INST_DIR}\*.*"
> 
> which installs all files and directories recursively (from your make install 
> tree) to the installation directory chosen by the end user of your 
> installation program.
> 
> 
> This stuff is not easy, especially when we can't see your code.
> 
> Cheers, (& good luck),
> David
> 
> 
> On Mon, May 21, 2012 at 12:39 PM, NoRulez  wrote:
> Hi,
> 
> I know that the install commands collect files and copy them into the 
> temporary cpack directory for the specified generator.
> How is it possible to install an application for example into those folders:
> C:\myapp
> C:\somefolder
> 
> I defined 'Var CustomDir="C:\somefolder"' in the NSIS template.
> 
> When I then use the following in the CMakeLists.txt:
> install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION 
> $CustomDir)
> 
> Then the files are installed in 
> _CPACK_PACKAGES/NSIS/myproject_1.0.0.1/$CustomDir.
> The generated project.nsi has the content: $INSTDIR\$CustomDir\...
> 
> How can I avoid that $INSTDIR\ is added, or did I need to use the install 
> command in a different way?
> 
> Thanks in advance
> 
> Best Regards
> NoRulez
> 
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
> 
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

I don't know how, but the problem is solved. If I find out the problem I'll 
post it on the list.

What i've done was to begin from scratch with the installers CMakeLists.txt and 
the custom NSIS template.

Much thanks to Eric and David for the hint with the "--verbose --debug" command 
line arguments

Best Regards

Am 19.05.2012 um 20:51 schrieb :

> Sorry, but the project is a commercial application.
> 
> Did you mean this site? http://www.cmake.org/cmake/help/cmake_tutorial.html#s7
> 
> But there must something in the original *.nsi file, because if I use the 
> original file then the files get copied (Without changing the CMakeLists.txt 
> file)
> 
> On the workstations we use VS instead of nmake. Is there a way do call CPack 
> with the "--verbose --debug" options under VS without using nmake from the 
> command line?
> 
> 
> Am 19.05.2012 um 20:26 schrieb David Cole :
> 
>> CPack does a "make install" and puts your install tree underneath 
>> _CPack_Packages.
>> 
>> THEN, it calls NSIS with the *.nsi script, and packages that up into an 
>> installer.
>> 
>> There is nothing in the *.nsi file that copies anything into 
>> _CPack_Packages. That happens before makensis is ever called.
>> 
>> Please post some code, so we can help you figure out what is going on here.
>> 
>> Is this in an open source project where we can inspect the code? Or can you 
>> replicate your problem with the CMake/Tests/Tutorial/Step7 project?
>> 
>> 
>> 
>> On Sat, May 19, 2012 at 2:02 PM,  wrote:
>> Hello Eric,
>> hello David,
>> 
>> sorry for the long response time.
>> 
>> I noticed that the custom CPackConfig is not necessary if I use variable 
>> names beginning with CPACK_. So first I removed the custom file.
>> 
>> Then the main problem...
>> I don't use a changed NSIS.template.in file from the CMake installation. I 
>> use a NSIS script from a college and tried to use it under CPack. This means 
>> than I used CPACK variable names instead of hard coded values. However I'm a 
>> NSIS novice, so it seems that in a CPACK variable and/or in the original 
>> NSIS.template.in file are some commands which I didn't find. The only one I 
>> need is the command which copies the necessary files into the temporary 
>> CPack directory (_CPack_Packges).
>> 
>> Which CPack variable and/or NSIS commands from the original template file 
>> are required to solve this?
>> 
>> Thanks in advance
>> 
>> Best Regards
>> 
>> Am 09.05.2012 um 20:45 schrieb "NoRulez" :
>>> >> By the way could you try 2.8.8 instead of 2.8.7 ?
>>> Yes, I will try it tomorrow (I read the changelog 
>>> http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.8 but I can't find any 
>>> details where this behavior may be fixed)
>>> Because on our Buildserver CMake 2.8.7 is installed and if no relevant 
>>> changes are made in 2.8.8, then I would be happy if I could retain the 
>>> CMake 2.8.7 installation (Never change a running system ;-))
>>> 
>>> But I will try 2.8.8 on the workstation and send you the output from 2.8.7 
>>> ("--verbose --debug").
>>> 
>>> Best Regards
>>> 
>>> Am 09. Mai 2012 um 11:31 schrieb Eric Noulard :
>>> 
>>>> 2012/5/9 :
>>>> >>> Is it the case? Is there any file in 
>>>> >>> _CPack_Packages\win32\NSIS\MyProject
>>>> >>> ?
>>>> > No, there aren't any files
>>>> >
>>>> >
>>>> >>> Could you copy/paste the exact message you get and may be running cpack
>>>> >>> on the command line with ---verbose and --debug.
>>>> > Sure, but I can only do so tomorrow
>>>> >
>>>> >
>>>> >>> Nope normally you don't but what are you doing in your
>>>> >>> "CPackConfig.cmake.in" ?
>>>> > I only set the CPACK variables and additional variables which are used in
>>>> > the NSIS.template.in file.
>>>> > Because if I don't use the custom CPackConfig.cmake.in file then the
>>>> > variables in the NSIS.template.in files aren't resolved.
>>>> 
>>>> Please send us those files.
>>>> As usual the devil may be in the details.
>>>> 
>>>> >>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project?
>>>> > Yes, i use this for the BundleU

[CMake] CPack: Installing applications in separate folders (NSIS)

[NoRulez]

Hi,I know that the install commands collect files and copy them into the temporary cpack directory for the specified generator.How is it possible to install an application for example into those folders:C:\myappC:\somefolderI defined 'Var CustomDir="C:\somefolder"' in the NSIS template.When I then use the following in the CMakeLists.txt:install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION $CustomDir)Then the files are installed in _CPACK_PACKAGES/NSIS/myproject_1.0.0.1/$CustomDir.The generated project.nsi has the content: $INSTDIR\$CustomDir\...How can I avoid that $INSTDIR\ is added, or did I need to use the install command in a different way?Thanks in advanceBest RegardsNoRulez--

Powered by www.kitware.com

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

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

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

Re: [CMake] How to use verbose and debug output for CPack under VS

[norulez]

Thanks, the custom command works

Am 21.05.2012 um 17:41 schrieb David Cole :

> On Mon, May 21, 2012 at 3:30 AM, Eric Noulard  wrote:
> 2012/5/21  :
> > Is there an environment variable or a CMake/CPack variable which is must 
> > set?
> 
> Currently AFAIK there aren't any.
> But it would be easy to add, you may propose a patch.
> 
> > how can I configure a project for Visual Studio to use the "--verbose" and 
> > the "--debug"
> > options/command line parameters?
> 
> As a workaround I would suggest to craft a custom target that will do the job:
> 
> add_custom_target(PACKAGE_DEBUG
>  COMMAND ${CMAKE_CPACK_COMMAND} --debug --verbose
> --config CPackConfig.cmake
>  COMMENTS "Build package with debug and verbose output")
> --
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
> 
> 
> I don't think this needs to be done very often, and is not worth making a 
> change in CMake for... (So I don't want a patch for it... thanks, anyway)  
> You can easily edit the custom command that CMake already generates for 
> running CPack directly in the Visual Studio gui if you need to add command 
> line arguments for debugging purposes.
> 
> Simply right click the "PACKAGE" project, and choose "Properties" -- when the 
> property pages come up, look for "Build Events" and "Post-Build Event" and 
> edit the command line for the post build event.
> 
> You can see there's one line in there that calls cpack with something like:
> 
>   "C:\Program Files (x86)\CMake 2.8\bin\cpack.exe" -C $(Configuration) 
> --config ./CPackConfig.cmake
> 
> Just add your --verbose and --debug there, and then right click the "PACKAGE" 
> project again, and choose "Project Only > Build Only PACKAGE" to execute the 
> post build command that you just edited...
> 
> 
> Alternatively, besides some environment differences (which may but don't 
> typically cause final package differences), there should be no reason you 
> can't just run cpack directly from a command prompt in your build tree and 
> get the exact same package.
> 
> 
> HTH,
> David
> 
> 
--

Powered by www.kitware.com

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

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

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

Re: [CMake] How to use verbose and debug output for CPack under VS

[norulez]

Is there an environment variable or a CMake/CPack variable which is must set?

Thanks in advance

Am 20.05.2012 um 20:10 schrieb noru...@me.com:

> Hello,
> 
> how can I configure a project for Visual Studio to use the "--verbose" and 
> the "--debug" options/command line parameters?
> 
> Thanks in advance
> 
> Best Regards
> NoRulez
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

[CMake] How to use verbose and debug output for CPack under VS

[norulez]

Hello,

how can I configure a project for Visual Studio to use the "--verbose" and the 
"--debug" options/command line parameters?

Thanks in advance

Best Regards
NoRulez
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

Sorry, but the project is a commercial application.

Did you mean this site? http://www.cmake.org/cmake/help/cmake_tutorial.html#s7

But there must something in the original *.nsi file, because if I use the 
original file then the files get copied (Without changing the CMakeLists.txt 
file)

On the workstations we use VS instead of nmake. Is there a way do call CPack 
with the "--verbose --debug" options under VS without using nmake from the 
command line?


Am 19.05.2012 um 20:26 schrieb David Cole :

> CPack does a "make install" and puts your install tree underneath 
> _CPack_Packages.
> 
> THEN, it calls NSIS with the *.nsi script, and packages that up into an 
> installer.
> 
> There is nothing in the *.nsi file that copies anything into _CPack_Packages. 
> That happens before makensis is ever called.
> 
> Please post some code, so we can help you figure out what is going on here.
> 
> Is this in an open source project where we can inspect the code? Or can you 
> replicate your problem with the CMake/Tests/Tutorial/Step7 project?
> 
> 
> 
> On Sat, May 19, 2012 at 2:02 PM,  wrote:
> Hello Eric,
> hello David,
> 
> sorry for the long response time.
> 
> I noticed that the custom CPackConfig is not necessary if I use variable 
> names beginning with CPACK_. So first I removed the custom file.
> 
> Then the main problem...
> I don't use a changed NSIS.template.in file from the CMake installation. I 
> use a NSIS script from a college and tried to use it under CPack. This means 
> than I used CPACK variable names instead of hard coded values. However I'm a 
> NSIS novice, so it seems that in a CPACK variable and/or in the original 
> NSIS.template.in file are some commands which I didn't find. The only one I 
> need is the command which copies the necessary files into the temporary CPack 
> directory (_CPack_Packges).
> 
> Which CPack variable and/or NSIS commands from the original template file are 
> required to solve this?
> 
> Thanks in advance
> 
> Best Regards
> 
> Am 09.05.2012 um 20:45 schrieb "NoRulez" :
>> >> By the way could you try 2.8.8 instead of 2.8.7 ?
>> Yes, I will try it tomorrow (I read the changelog 
>> http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.8 but I can't find any 
>> details where this behavior may be fixed)
>> Because on our Buildserver CMake 2.8.7 is installed and if no relevant 
>> changes are made in 2.8.8, then I would be happy if I could retain the CMake 
>> 2.8.7 installation (Never change a running system ;-))
>> 
>> But I will try 2.8.8 on the workstation and send you the output from 2.8.7 
>> ("--verbose --debug").
>> 
>> Best Regards
>> 
>> Am 09. Mai 2012 um 11:31 schrieb Eric Noulard :
>> 
>>> 2012/5/9 :
>>> >>> Is it the case? Is there any file in 
>>> >>> _CPack_Packages\win32\NSIS\MyProject
>>> >>> ?
>>> > No, there aren't any files
>>> >
>>> >
>>> >>> Could you copy/paste the exact message you get and may be running cpack
>>> >>> on the command line with ---verbose and --debug.
>>> > Sure, but I can only do so tomorrow
>>> >
>>> >
>>> >>> Nope normally you don't but what are you doing in your
>>> >>> "CPackConfig.cmake.in" ?
>>> > I only set the CPACK variables and additional variables which are used in
>>> > the NSIS.template.in file.
>>> > Because if I don't use the custom CPackConfig.cmake.in file then the
>>> > variables in the NSIS.template.in files aren't resolved.
>>> 
>>> Please send us those files.
>>> As usual the devil may be in the details.
>>> 
>>> >>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project?
>>> > Yes, i use this for the BundleUtilities like in the BundleUtilities 
>>> > example
>>> >
>>> > INSTALL(CODE "
>>> > file(GLOB_RECURSE SHARED_LIBS
>>> > \"\${CMAKE_INSTALL_PREFIX}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\")
>>> > include(BundleUtilities)
>>> > fixup_bundle(\"${APPS}\" \"\${SHARED_LIBS}\" \"${DIRS}\")
>>> > " COMPONENT Runtime)
>>> 
>>> I'm not a BundleUtilities user but code like that may break with CPack 
>>> because
>>> CPack may internally use DESTDIR to do its local installation so that
>>> one should usually write:
>>> 
>>> $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}
>>> ra

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

Hello Eric,
hello David,

sorry for the long response time.

I noticed that the custom CPackConfig is not necessary if I use variable names 
beginning with CPACK_. So first I removed the custom file.

Then the main problem...
I don't use a changed NSIS.template.in file from the CMake installation. I use 
a NSIS script from a college and tried to use it under CPack. This means than I 
used CPACK variable names instead of hard coded values. However I'm a NSIS 
novice, so it seems that in a CPACK variable and/or in the original 
NSIS.template.in file are some commands which I didn't find. The only one I 
need is the command which copies the necessary files into the temporary CPack 
directory (_CPack_Packges).

Which CPack variable and/or NSIS commands from the original template file are 
required to solve this?

Thanks in advance

Best Regards

Am 09.05.2012 um 20:45 schrieb "NoRulez" :
> >> By the way could you try 2.8.8 instead of 2.8.7 ?
> Yes, I will try it tomorrow (I read the changelog 
> http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.8 but I can't find any 
> details where this behavior may be fixed)
> Because on our Buildserver CMake 2.8.7 is installed and if no relevant 
> changes are made in 2.8.8, then I would be happy if I could retain the CMake 
> 2.8.7 installation (Never change a running system ;-))
> 
> But I will try 2.8.8 on the workstation and send you the output from 2.8.7 
> ("--verbose --debug").
> 
> Best Regards
> 
> Am 09. Mai 2012 um 11:31 schrieb Eric Noulard :
> 
>> 2012/5/9 :
>> >>> Is it the case? Is there any file in _CPack_Packages\win32\NSIS\MyProject
>> >>> ?
>> > No, there aren't any files
>> >
>> >
>> >>> Could you copy/paste the exact message you get and may be running cpack
>> >>> on the command line with ---verbose and --debug.
>> > Sure, but I can only do so tomorrow
>> >
>> >
>> >>> Nope normally you don't but what are you doing in your
>> >>> "CPackConfig.cmake.in" ?
>> > I only set the CPACK variables and additional variables which are used in
>> > the NSIS.template.in file.
>> > Because if I don't use the custom CPackConfig.cmake.in file then the
>> > variables in the NSIS.template.in files aren't resolved.
>> 
>> Please send us those files.
>> As usual the devil may be in the details.
>> 
>> >>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project?
>> > Yes, i use this for the BundleUtilities like in the BundleUtilities example
>> >
>> > INSTALL(CODE "
>> > file(GLOB_RECURSE SHARED_LIBS
>> > \"\${CMAKE_INSTALL_PREFIX}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\")
>> > include(BundleUtilities)
>> > fixup_bundle(\"${APPS}\" \"\${SHARED_LIBS}\" \"${DIRS}\")
>> > " COMPONENT Runtime)
>> 
>> I'm not a BundleUtilities user but code like that may break with CPack 
>> because
>> CPack may internally use DESTDIR to do its local installation so that
>> one should usually write:
>> 
>> $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}
>> rather than
>> ${CMAKE_INSTALL_PREFIX}
>> 
>> however since you have NO file at all in the local CPack install dir,
>> the problem is elsewhere.
>> 
>> By the way could you try 2.8.8 instead of 2.8.7 ?
>> 
>> -- 
>> Erk
>> Le gouvernement représentatif n'est pas la démocratie --
>> http://www.le-message.org
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[NoRulez]

>> By the way could you try 2.8.8 instead of 2.8.7 ?Yes, I will try it tomorrow (I read the changelog http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.8 but I can't find any details where this behavior may be fixed)Because on our Buildserver CMake 2.8.7 is installed and if no relevant changes are made in 2.8.8, then I would be happy if I could retain the CMake 2.8.7 installation (Never change a running system ;-))But I will try 2.8.8 on the workstation and send you the output from 2.8.7 ("--verbose --debug").Best RegardsAm 09. Mai 2012 um 11:31 schrieb Eric Noulard :2012/5/9 : >>> Is it the case? Is there any file in _CPack_Packages\win32\NSIS\MyProject >>> ? > No, there aren't any files > > >>> Could you copy/paste the exact message you get and may be running cpack >>> on the command line with ---verbose and --debug. > Sure, but I can only do so tomorrow > > >>> Nope normally you don't but what are you doing in your >>> "CPackConfig.cmake.in" ? > I only set the CPACK variables and additional variables which are used in > the NSIS.template.in file. > Because if I don't use the custom CPackConfig.cmake.in file then the > variables in the NSIS.template.in files aren't resolved.  Please send us those files. As usual the devil may be in the details.  >>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project? > Yes, i use this for the BundleUtilities like in the BundleUtilities example > > INSTALL(CODE " > file(GLOB_RECURSE SHARED_LIBS > \"\${CMAKE_INSTALL_PREFIX}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\") > include(BundleUtilities) > fixup_bundle(\"${APPS}\" \"\${SHARED_LIBS}\" \"${DIRS}\") > " COMPONENT Runtime)  I'm not a BundleUtilities user but code like that may break with CPack because CPack may internally use DESTDIR to do its local installation so that one should usually write:  $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX} rather than ${CMAKE_INSTALL_PREFIX}  however since you have NO file at all in the local CPack install dir, the problem is elsewhere.  By the way could you try 2.8.8 instead of 2.8.7 ?  --  Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

>> Is it the case? Is there any file in _CPack_Packages\win32\NSIS\MyProject ?No, there aren't any files>> Could you copy/paste the exact message you get and may be running cpack on the command line with ---verbose and --debug.Sure, but I can only do so tomorrow>> Nope normally you don't but what are you doing in your "CPackConfig.cmake.in" ?I only set the CPACK variables and additional variables which are used in the NSIS.template.in file.Because if I don't use the custom CPackConfig.cmake.in file then the variables in the NSIS.template.in files aren't resolved.>> And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project?Yes, i use this for the BundleUtilities like in the BundleUtilities exampleINSTALL(CODE "file(GLOB_RECURSE SHARED_LIBS  \"\${CMAKE_INSTALL_PREFIX}/*${CMAKE_SHARED_LIBRARY_SUFFIX}\")include(BundleUtilities)fixup_bundle(\"${APPS}\" \"\${SHARED_LIBS}\" \"${DIRS}\")" COMPONENT Runtime)Best RegardsAm 09. Mai 2012 um 10:55 schrieb Eric Noulard :2012/5/9 : [...]  > > If I run the INSTALL target under VS then the files are correctly copied to > C:\Program Files\MyProject > But only the PACKAGE target under VS doesn't work, and I get the message > from the last email I sent.  >> So, my custom CPackConfig.cmake.in and my NSIS.template.in seems to work, >> but CPack reports that there are not files (*.* under >> _CPack_Packages\win32\NSIS\MyProject)  Is it the case? Is there any file in _CPack_Packages\win32\NSIS\MyProject ?  Could you copy/paste the exact message you get and may be running cpack on the command line with ---verbose and --debug.   >> I have install statements for the executable and also for the shared >> libraries. What could be the problem? >> Do I need a special setting in CPackConfig.cmake.in or in NSIS.tempalte.in >> to copy the files into the _CPack_Packages subfolder?  Nope normally you don't but what are you doing in your "CPackConfig.cmake.in" ?  And do you have any INSTALL(CODE or INSTALL(SCRIPTS in your project?   --  Erk Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

The install command looks something likemacro(InstallTarget TARGET)    INSTALL(TARGETS ${TARGET}
BUNDLE DESTINATION .
RUNTIME DESTINATION .ARCHIVE DESTINATION .LIBRARY DESTINATION .
)endmacro(InstallTarget)...InstallTarget(MyApp)..InstallTarget(MyLib)Other files will be installed like the following:install(FILES "${CMAKE_SOURCE_DIR}/setup/vcredist_x86.exe  DESTINATION .)If I run the INSTALL target under VS then the files are correctly copied to C:\Program Files\MyProjectBut only the PACKAGE target under VS doesn't work, and I get the message from the last email I sent.Best RegardsAm 09. Mai 2012 um 19:39 schrieb David Cole :What do your install commands look like?  You're not trying to install files into absolute paths on Windows, are you? (i.e. -- all things should be installed underneath CMAKE_INSTALL_PREFIX in a normal 'make install' tree in order to work well on Windows with the NSIS generator.)On Wed, May 9, 2012 at 1:34 PM, NoRulez <noru...@me.com> wrote: > Hello Eric, > > I've found the problem, it was my mistake. A few lines later i overwrote the > CPACK_MODULE_PATH setting. [RESOLVED] > > But what I didn't understand was the fact that it would work on Windows 7 > with the same settings. > > So, my custom CPackConfig.cmake.in and my NSIS.template.in seems to work, > but CPack reports that there are not files (*.* under > _CPack_Packages\win32\NSIS\MyProject) > I have install statements for the executable and also for the shared > libraries. What could be the problem? > Do I need a special setting in CPackConfig.cmake.in or in NSIS.tempalte.in > to copy the files into the _CPack_Packages subfolder? > > Thank you for your help > > Best Regards > > Am 08.05.2012 um 15:19 schrieb noru...@me.com: > > >> It is only a copy from the original. It doesn't work in windows xp in >> general. >> >> Best Regards >> >> Am 08.05.2012 um 13:51 schrieb Eric Noulard <eric.noul...@gmail.com>: >> >>> 2012/5/8 <noru...@me.com>: >>>> There is no difference with your command. It still uses the >>>> NSIS.template.in file from the CMake installation. >>> >>> Are there any difference between the 2 CPackConfig.cmake files ? >>> WinXP failing case vs Win7 working case? >>> >>> Does the ${CMAKE_SOURCE_DIR}/cmake/NSIS.template.in file has any weird >>> attribute? >>> Is it readable by "normal user"? (you said it works if you are admin >>> right?) >>> >>>> Yes I tried the configurations in new build directories such as build1 >>>> ... buildn. >>> >>> I got that but I suspected something in the source tree (where your >>> NSIS.template.in is) >>> so starting from another source tree (taken from your VCS) may exhibit >>> different behavior. >>> >>> If all that fail I'm afraid I cannot help more unless you can build a >>> minimalistic example >>> which shows the wrong behavior. >>> >>> (I have no WinXP at hand but then I may look into the source more >>> thoroughly). >>> >>> -- >>> Erk >>> Le gouvernement représentatif n'est pas la démocratie -- >>> http://www.le-message.org >> -- >> >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Follow this link to subscribe/unsubscribe: >> http://www.cmake.org/mailman/listinfo/cmake > > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[NoRulez]

Hello Eric,I've found the problem, it was my mistake. A few lines later i overwrote the CPACK_MODULE_PATH setting. [RESOLVED]

But what I didn't understand was the fact that it would work on Windows 7 with the same settings.So, my custom CPackConfig.cmake.in and my NSIS.template.in seems to work, but CPack reports that there are not files (*.* under _CPack_Packages\win32\NSIS\MyProject)I have install statements for the executable and also for the shared libraries. What could be the problem?Do I need a special setting in CPackConfig.cmake.in or in NSIS.tempalte.in to copy the files into the _CPack_Packages subfolder?

Thank you for your help

Best Regards

Am 08.05.2012 um 15:19 schrieb noru...@me.com:

> It is only a copy from the original. It doesn't work in windows xp in general.
> 
> Best Regards
> 
> Am 08.05.2012 um 13:51 schrieb Eric Noulard :
> 
>> 2012/5/8  :
>>> There is no difference with your command. It still uses the NSIS.template.in file from the CMake installation.
>> 
>> Are there any difference between the 2 CPackConfig.cmake files ?
>> WinXP failing case vs Win7 working case?
>> 
>> Does the ${CMAKE_SOURCE_DIR}/cmake/NSIS.template.in file has any weird
>> attribute?
>> Is it readable by "normal user"? (you said it works if you are admin right?)
>> 
>>> Yes I tried the configurations in new build directories such as build1 ... buildn.
>> 
>> I got that but I suspected something in the source tree (where your
>> NSIS.template.in is)
>> so starting from another source tree (taken from your VCS) may exhibit
>> different behavior.
>> 
>> If all that fail I'm afraid I cannot help more unless you can build a
>> minimalistic example
>> which shows the wrong behavior.
>> 
>> (I have no WinXP at hand but then I may look into the source more thoroughly).
>> 
>> -- 
>> Erk
>> Le gouvernement représentatif n'est pas la démocratie --
>> http://www.le-message.org
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

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

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

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

Re: [CMake] CPack doesn't recognize custom templates

[norulez]

It is only a copy from the original. It doesn't work in windows xp in general.

Best Regards

Am 08.05.2012 um 13:51 schrieb Eric Noulard :

> 2012/5/8  :
>> There is no difference with your command. It still uses the NSIS.template.in 
>> file from the CMake installation.
> 
> Are there any difference between the 2 CPackConfig.cmake files ?
> WinXP failing case vs Win7 working case?
> 
> Does the ${CMAKE_SOURCE_DIR}/cmake/NSIS.template.in file has any weird
> attribute?
> Is it readable by "normal user"? (you said it works if you are admin right?)
> 
>> Yes I tried the configurations in new build directories such as build1 ... 
>> buildn.
> 
> I got that but I suspected something in the source tree (where your
> NSIS.template.in is)
> so starting from another source tree (taken from your VCS) may exhibit
> different behavior.
> 
> If all that fail I'm afraid I cannot help more unless you can build a
> minimalistic example
> which shows the wrong behavior.
> 
> (I have no WinXP at hand but then I may look into the source more thoroughly).
> 
> -- 
> Erk
> Le gouvernement représentatif n'est pas la démocratie --
> http://www.le-message.org
--

Powered by www.kitware.com

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

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

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