[cmake-developers] [CMake 0012940]: FindBoost.cmake cannot find libraries built with clang on Darwin.

2012-02-07 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=12940 
== 
Reported By:David Rogers
Assigned To:
== 
Project:CMake
Issue ID:   12940
Category:   Modules
Reproducibility:always
Severity:   tweak
Priority:   normal
Status: new
== 
Date Submitted: 2012-02-07 14:25 EST
Last Modified:  2012-02-07 14:25 EST
== 
Summary:FindBoost.cmake cannot find libraries built with
clang on Darwin.
Description: 
If boost libraries are built with clang, their compiler name ends up being
clang-darwin instead of xgcc. Because of this, the script fails to locate them.

Steps to Reproduce: 
Build boost with clang. Attempt to locate them in a script.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2012-02-07 14:25 David Rogers   New Issue
==

--

Powered by www.kitware.com

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

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

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[CMake] Again multiple subdirs

2012-02-07 Thread justin
Hi,

and just in the beginning, I am sorry if this was asked thousands of
times before, but I wasn't able to find it.

The situation is following

src -- common -- common.c
 |
   a -- a.c
 |
   b -- b.c


add_library (a
 ${project_SOURCE_DIR}/common/common
 ${project_SOURCE_DIR}/a/a}

add_library (b
 ${project_SOURCE_DIR}/common/common
 ${project_SOURCE_DIR}/b/b}


This results in a double compilation of common.c. One time for liba and
the other one for libb.

What is the best way to force common.c to be compiled just ones?


Thanks justin



signature.asc
Description: OpenPGP digital signature
--

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] Default Generator to use

2012-02-07 Thread Eric Noulard
2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 Hello Friends,

 How do I specify the default generator that CMAKE should use when invoked
 without the “-G” option?

 I am on Windows.

 I saw an old thread on this. But I am not sure if any support was added
 later on.


 Is there a REGISTRY entry in Windows that we can set to make so that CMAKE
 can check it?

When starting with an empty build tree (or more precisely with empty cache)
the logic of the default generator is implement in:

Source/cmake.cxx::int cmake::ActualConfigure()

There is some system dependent macro logic and in
the Windows case the code comment says
(if not in Borland or Cygwin or Mingw case):
// Try to find the newest VS installed on the computer and
// use that as a default if -G is not specified

So no, as far as I understand the code,
there is no registry entry that could possibly be set to force a
particular default.

I guess it shouldn't be that hard to implement but it is not there.
(I'm not willing to try myself because I'm not a Windows user/developer)

Nevertheless, may be you can explain us why you would like to setup a default?
Is it too painful to add the extra -G argument?

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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] How to submit patches?

2012-02-07 Thread Eric Noulard
2012/2/7 Rolf Eike Beer e...@sf-mail.de:
 Am Montag, 6. Februar 2012, 19:12:27 schrieb Michael Pechner:
 Is this the correct forum?

 cmake-develop...@cmake.org would be the right place. Or open a bug report at
 http://cmake.org/Bug and attach it there.

May be browse/search the bug tracker before filing a new bug
just in case there is a similar/identical bug already reported.

 What format do you want the patch in?

 git format-patch

How to get CMake git tree is explained here:
http://www.cmake.org/Wiki/CMake/Git/Download

More infos on using git for CMake here:
http://www.cmake.org/Wiki/CMake/Git

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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] How to submit patches?

2012-02-07 Thread Sarnath K - ERS, HCLTech
I have found Visual Studio (generated via CMAKE)  smart enough to handle these 
double-compilation cases.
That's my vague memory. You may check it out. Are you on windows?

::DISCLAIMER::
---

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and
attachments please check them for viruses and defect.

---
--

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] Again multiple subdirs

2012-02-07 Thread Rolf Eike Beer
 add_library (a
  ${project_SOURCE_DIR}/common/common
  ${project_SOURCE_DIR}/a/a}

 add_library (b
  ${project_SOURCE_DIR}/common/common
  ${project_SOURCE_DIR}/b/b}


 This results in a double compilation of common.c. One time for liba and
 the other one for libb.

 What is the best way to force common.c to be compiled just ones?

Create a static library from it.

Eike
--

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] Again multiple subdirs

2012-02-07 Thread Andreas Pakulat
On 07.02.12 08:55:47, justin wrote:
 Hi,
 
 and just in the beginning, I am sorry if this was asked thousands of
 times before, but I wasn't able to find it.
 
 The situation is following
 
 src -- common -- common.c
  |
    a -- a.c
  |
    b -- b.c
 
 
 add_library (a
  ${project_SOURCE_DIR}/common/common
  ${project_SOURCE_DIR}/a/a}
 
 add_library (b
  ${project_SOURCE_DIR}/common/common
  ${project_SOURCE_DIR}/b/b}
 
 
 This results in a double compilation of common.c. One time for liba and
 the other one for libb.
 
 What is the best way to force common.c to be compiled just ones?

If a and b are static libs, create a static lib for the common code and
link both against it. If a and b are shared libs, make the common code a
shared lib too and link a/b against the shared lib.

Andreas

--

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] Default Generator to use

2012-02-07 Thread Sarnath K - ERS, HCLTech
Hello Eric,

We have a case where 2 teams are working on a common source tree.
One team is using Visual Studio 9 2008 and the other Visual Studio 10
Our platform is Windows7 64-bit.

We have a tool in our project that gets added as an External Project to the 
main CMAKE project.
This tool needs to be compiled _only_ as a 32-bit windows executable.
I use a configure.bat to configure this external project and build.

This batch-file has to invoke CMAKE with either Visual Studio 9 2008 or 
Visual Studio 10.
But I would like this batch file to use the latest Visual Studio installed in 
the system in 32-bit mode.
I am on Win64 Command Prompt.
The main project is generated using NMake Makefiles.
How do I do this?

Thanks,
Best Regards,
Sarnath

-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Tuesday, February 07, 2012 1:36 PM
To: Sarnath K - ERS, HCLTech
Cc: cmake@cmake.org
Subject: Re: [CMake] Default Generator to use

2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 Hello Friends,

 How do I specify the default generator that CMAKE should use when invoked
 without the -G option?

 I am on Windows.

 I saw an old thread on this. But I am not sure if any support was added
 later on.


 Is there a REGISTRY entry in Windows that we can set to make so that CMAKE
 can check it?

When starting with an empty build tree (or more precisely with empty cache)
the logic of the default generator is implement in:

Source/cmake.cxx::int cmake::ActualConfigure()

There is some system dependent macro logic and in
the Windows case the code comment says
(if not in Borland or Cygwin or Mingw case):
// Try to find the newest VS installed on the computer and
// use that as a default if -G is not specified

So no, as far as I understand the code,
there is no registry entry that could possibly be set to force a
particular default.

I guess it shouldn't be that hard to implement but it is not there.
(I'm not willing to try myself because I'm not a Windows user/developer)

Nevertheless, may be you can explain us why you would like to setup a default?
Is it too painful to add the extra -G argument?

--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

::DISCLAIMER::
---

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and
attachments please check them for viruses and defect.

---
--

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] Default Generator to use

2012-02-07 Thread Sarnath K - ERS, HCLTech
http://stackoverflow.com/questions/6430251/what-is-the-default-generator-for-cmake-in-windows

In the stack overflow list, one guy mentions about 
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\
Is this the same thing as the AutoConfigure thing that you were mentioning?
What should I set here? Pardon my ignorance.

Thanks,
Best Regards,
Sarnath

::DISCLAIMER::
---

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and
attachments please check them for viruses and defect.

---
--

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] Default Generator to use

2012-02-07 Thread Eric Noulard
2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 Hello Eric,

 We have a case where 2 teams are working on a common source tree.
 One team is using Visual Studio 9 2008 and the other Visual Studio 10
 Our platform is Windows7 64-bit.

 We have a tool in our project that gets added as an External Project to 
 the main CMAKE project.
 This tool needs to be compiled _only_ as a 32-bit windows executable.
 I use a configure.bat to configure this external project and build.

You should have a look to ExternalProject cmake module and
its ExternalProject_Add macro.


 This batch-file has to invoke CMAKE with either Visual Studio 9 2008 or 
 Visual Studio 10.
 But I would like this batch file to use the latest Visual Studio installed in 
 the system in 32-bit mode.
 I am on Win64 Command Prompt.
 The main project is generated using NMake Makefiles.
 How do I do this?

My guess is that you should write some script or executable which does just that
get the name of the latest Visual Studio installed in the system
If you go for a script, may be a CMake script can do that.

May be you could parse the output of cmake --help in order to get
the list of supported generators and/or inspect registry yourself in
order to build
the appropriate name.


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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] Default Generator to use

2012-02-07 Thread Sarnath K - ERS, HCLTech
I just looked at ActualConfigure() function. This is the same as the one 
mentioned in Stackoverflow URL.

I think I will just create the correct entries in the registry and allow 
CMAKE to take the decision.
I won't pass any -G at all.

That's the most portable way as I look at it.

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\9.0;InstallDir] -- 
seems to be the place.
But I really don't understand what is the ; doing there.
Should I first create a 9.0 entry and then create an InstallDir inside it 
pointing to the directory where Visual Studio is installed?
Thanks for any help,

Best Regards,
Sarnath

::DISCLAIMER::
---

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and
attachments please check them for viruses and defect.

---
--

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] Default Generator to use

2012-02-07 Thread Eric Noulard
2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 http://stackoverflow.com/questions/6430251/what-is-the-default-generator-for-cmake-in-windows

 In the stack overflow list, one guy mentions about 
 [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\
 Is this the same thing as the AutoConfigure thing that you were mentioning?

Yes it is.

 What should I set here? Pardon my ignorance.

You shouldn't set anything here because it is set by the Visual Studio
installer.
CMake is only **reading** it in order to guess the latest VS installed.

The comment on Stack Overflow is right:

For posterity: there is an entry in the CMake mailing list that
addresses this issue. To change the default generator, it seems you
need to either modify the CMake source and recompile or write a small
batch file that adds the -G option to substitute the generator when
none is specified. – André Caron

the refered ML message is:
http://www.mail-archive.com/cmake@cmake.org/msg18033.html
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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] Default Generator to use

2012-02-07 Thread Eric Noulard
2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 I just looked at ActualConfigure() function. This is the same as the one 
 mentioned in Stackoverflow URL.

 I think I will just create the correct entries in the registry and allow 
 CMAKE to take the decision.
 I won't pass any -G at all.

 That's the most portable way as I look at it.

Not my opinion but that's your choice.

 [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\9.0;InstallDir] -- 
 seems to be the place.
 But I really don't understand what is the ; doing there.
 Should I first create a 9.0 entry and then create an InstallDir inside it 
 pointing to the directory where Visual Studio is installed?

You should read  more about what is the registry, before trying to modify it:
http://en.wikipedia.org/wiki/Windows_Registry
http://support.microsoft.com/kb/136393


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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] Default Generator to use

2012-02-07 Thread Sarnath K - ERS, HCLTech
Thank you Eric

The entry for 9.0 is already there and CMAKE is detecting it in our setup 
without passing any -G option.
And, the default is 32-bit build even on 64-bit machines. This is great news 
for us!

If this behavior is seen with the VC 10 installation then we are good to go on 
this without any changes.

Thanks,
Best Regards,
Sarnath

-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Tuesday, February 07, 2012 3:08 PM
To: Sarnath K - ERS, HCLTech
Cc: cmake@cmake.org
Subject: Re: [CMake] Default Generator to use

2012/2/7 Sarnath K - ERS, HCLTech k_sarn...@hcl.com:
 I just looked at ActualConfigure() function. This is the same as the one 
 mentioned in Stackoverflow URL.

 I think I will just create the correct entries in the registry and allow 
 CMAKE to take the decision.
 I won't pass any -G at all.

 That's the most portable way as I look at it.

Not my opinion but that's your choice.

 [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\9.0;InstallDir] -- 
 seems to be the place.
 But I really don't understand what is the ; doing there.
 Should I first create a 9.0 entry and then create an InstallDir inside it 
 pointing to the directory where Visual Studio is installed?

You should read  more about what is the registry, before trying to modify it:
http://en.wikipedia.org/wiki/Windows_Registry
http://support.microsoft.com/kb/136393


--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

::DISCLAIMER::
---

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and
attachments please check them for viruses and defect.

---
--

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] Making a variable a dependency...

2012-02-07 Thread Nicolas Desprès
On Sat, Feb 4, 2012 at 11:35 PM, Oliver Smith osm...@playnet.com wrote:
 My CMakeLists uses the Subversion repository information in a couple of
 places (it configures a file revision.h and it uses it for the CPack package
 name).

 The problem is that this variable is cached and retained until the cache is
 rebuilt, instead of being calculated or evaluated per make. So if I do a
 build, then do an svn update and pull some changes, it will build a new
 executable but it will stamp it with the revision number from when CMake
 last regenerated the make files...

 Is there a way to mark a variable as volatile or something so that CMake
 will always recalculate it and check if it has changed?


I had the same problem and I decided it does not worth to tackle it
perfectly. Actually, you only need the right revision.h at release
time. So in my project I had a 'release' target with this behavior:
1/ tag the repository
2/ make rebuild_cache
3/ make all
4/ make package
Also, this could be simplify since I think it is safer to make a
release from a clean build directory so you can just skip the first
two step and just tell your release script to checkout the right
revision before to do a cmake, make, make package.

During development phase if you really want to have the proper
revision.h, I would suggest to add a 'force-revision' target which
recompute the revision number and regenerate the revision.h header.

I know I did not really answer your question but this solution is good
enough and does not require any tricks. Also I don't think it worth
running cmake each time make is called.

Regards,

-- 
Nicolas Desprès
--

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 CMake with icc via configuration options when needing interprocedural optimization?

2012-02-07 Thread janitor 048
Hello,

this is a question I recently asked on stackoverflow (
http://stackoverflow.com/questions/9129233/recommended-ways-to-use-cmake-with-icc-via-configuration-options)
but that has not received any response since then. Maybe this mailing list
is a better place to ask... Here goes

I would like to use the Intel compiler icc (or icpc) with a CMake-based
project (on Linux for what it's worth). I can of course export the CXX
variable when calling cmake, e.g. like

CXX=icpc cmake ../

and this works fine. I would however like to make this choice available via
a custom option. For this I parse custom option, e.g.

cmake -DMY_COMPILER_OPTION=Intel ..

as

IF (MY_COMPILER_OPTION STREQUAL Intel)
  MESSAGE(STATUS ** Compiling with Intel settings **)
  SET(CMAKE_CXX_COMPILER icpc)
  SET(CMAKE_CXX_FLAGS_RELEASE -O3 -w)
  SET(CMAKE_CXX_FLAGS_DEBUG -g)
ENDIF ()

and set CMAKE_CXX_COMPILER together with some compiler flags. This also
works, however there is an important but.

I would also like to use the option -ipo (interprocedural optimization) for
my code when compiling with icc plus I need to compile a static library
within the build process. For this to work, I need to use Intel's xiar (and
also xilink I guess).

cmake actually offers a special property for this

set_property(TARGET mytarget PROPERTY INTERPROCEDURAL_OPTIMIZATION 1)

however this only seems to works properly when the compiler has been set
via the environment variable (then xiar is used). When setting the compiler
via CMAKE_CXX_COMPILER this property is ignored.

Is there another way to do this?. Some recommended way? Or at least a
work-around?


Cheers, Oliver
--

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] [Java] - Adding manifest information to a jar file

2012-02-07 Thread Nicolas Desprès
On Sat, Dec 10, 2011 at 3:46 PM, Andreas Schneider a...@cryptomilk.org wrote:
 On Saturday 29 October 2011 23:34:50 Frank Glinka wrote:
 Hi,

 Hi,

Hi,


 I am happy about the recently improved Java support within cmake.
 Thanks! Anyhow, I have a small point which should be easy to improve and
 which would deliver quite some usability, in my opinion.

 The current syntax for building and packaging Java files is:
  add_jar(${TARGETNAME} ${SOURCE_FILES} ${RESOURCE_FILES})

 This has some drawbacks:

 1) No executable jar can be created with that method. It seems there is
 already some effort on that issue as:
 https://github.com/viandfraich/CMake/commit/36b223e34f5d48339da39e833a2f5e7d
 f2866e87

 I don't like the way how it has been added here. I think it should be an
 optional vairable you set before like the others. Please open a feature
 request in the bug tracker. Patches are welcome.


Here is a proposal: https://github.com/polrop/CMake/commits/java-executable-jar

 2) A jar file can be annotated with a lot of more important information,
 e.g., version information, scope, main-class (would also catch the first
 issue), etc. This information is normally passed as a property/manifest
 file when calling the jar packager. Currently, the UseJava.cmake

 module creates the following command within 'add_jar':
  jar cf ${TARGETNAME} ${CLASS_FILES} ${RESOURCE_FILES}

 The following would solve my (and I guess many others') use cases:
  jar cmf ${TARGETNAME} MyManifest.mf ${CLASS_FILES} ${RESOURCE_FILES}

 Should be an optional option and should be done like the other options.

 set(CMAKE_JAVA_MANIFEST mymanifest.mf)
 add_jar(foo foo.java)


I don't have any patch for this issue yet. Maybe in the future.

 An optional command to add_jar would be desirable which allows to
 provide an optional manifest file. If provided, the later syntax should
 be used for calling the 'jar' tool.

 Will there be progress towards supporting manifest information anytime
 soon within cmake?

 Open a feature request in the bugtracker.


Please tell me what you think about the proposal.

Regards,

-- 
Nicolas Desprès
--

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 CMake with icc via configuration options when needing interprocedural optimization?

2012-02-07 Thread Michael Jackson
Not sure that is really going to work because by the time CMake has parsed your 
option code the compiler (and who knows how many other internal variables) 
has already been set. 
--
Mike Jackson www.bluequartz.net

On Feb 7, 2012, at 8:43 AM, janitor 048 wrote:

 Hello,
 
 this is a question I recently asked on stackoverflow 
 (http://stackoverflow.com/questions/9129233/recommended-ways-to-use-cmake-with-icc-via-configuration-options)
  but that has not received any response since then. Maybe this mailing list 
 is a better place to ask... Here goes
 I would like to use the Intel compiler icc (or icpc) with a CMake-based 
 project (on Linux for what it's worth). I can of course export the CXX 
 variable when calling cmake, e.g. like
 
 CXX=icpc cmake ../
 
 and this works fine. I would however like to make this choice available via a 
 custom option. For this I parse custom option, e.g.
 
 cmake -DMY_COMPILER_OPTION=Intel ..
 
 as
 
 IF (MY_COMPILER_OPTION STREQUAL Intel)
   MESSAGE(STATUS ** Compiling with Intel settings **)
   SET(CMAKE_CXX_COMPILER icpc)
   SET(CMAKE_CXX_FLAGS_RELEASE -O3 -w)
   SET(CMAKE_CXX_FLAGS_DEBUG -g)
 ENDIF ()
 
 and set CMAKE_CXX_COMPILER together with some compiler flags. This also 
 works, however there is an important but.
 
 I would also like to use the option -ipo (interprocedural optimization) for 
 my code when compiling with icc plus I need to compile a static library 
 within the build process. For this to work, I need to use Intel's xiar (and 
 also xilink I guess).
 
 cmake actually offers a special property for this
 
 set_property(TARGET mytarget PROPERTY INTERPROCEDURAL_OPTIMIZATION 1)
 
 however this only seems to works properly when the compiler has been set via 
 the environment variable (then xiar is used). When setting the compiler via 
 CMAKE_CXX_COMPILER this property is ignored.
 
 Is there another way to do this?. Some recommended way? Or at least a 
 work-around?
 
 
 
 Cheers, Oliver
 
 --
 
 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] [Java] - Adding manifest information to a jar file

2012-02-07 Thread David Cole
2012/2/7 Nicolas Desprès nicolas.desp...@gmail.com:
 On Sat, Dec 10, 2011 at 3:46 PM, Andreas Schneider a...@cryptomilk.org 
 wrote:
 On Saturday 29 October 2011 23:34:50 Frank Glinka wrote:
 Hi,

 Hi,

 Hi,


 I am happy about the recently improved Java support within cmake.
 Thanks! Anyhow, I have a small point which should be easy to improve and
 which would deliver quite some usability, in my opinion.

 The current syntax for building and packaging Java files is:
  add_jar(${TARGETNAME} ${SOURCE_FILES} ${RESOURCE_FILES})

 This has some drawbacks:

 1) No executable jar can be created with that method. It seems there is
 already some effort on that issue as:
 https://github.com/viandfraich/CMake/commit/36b223e34f5d48339da39e833a2f5e7d
 f2866e87

 I don't like the way how it has been added here. I think it should be an
 optional vairable you set before like the others. Please open a feature
 request in the bug tracker. Patches are welcome.


 Here is a proposal: 
 https://github.com/polrop/CMake/commits/java-executable-jar

 2) A jar file can be annotated with a lot of more important information,
 e.g., version information, scope, main-class (would also catch the first
 issue), etc. This information is normally passed as a property/manifest
 file when calling the jar packager. Currently, the UseJava.cmake

 module creates the following command within 'add_jar':
  jar cf ${TARGETNAME} ${CLASS_FILES} ${RESOURCE_FILES}

 The following would solve my (and I guess many others') use cases:
  jar cmf ${TARGETNAME} MyManifest.mf ${CLASS_FILES} ${RESOURCE_FILES}

 Should be an optional option and should be done like the other options.

 set(CMAKE_JAVA_MANIFEST mymanifest.mf)
 add_jar(foo foo.java)


 I don't have any patch for this issue yet. Maybe in the future.

 An optional command to add_jar would be desirable which allows to
 provide an optional manifest file. If provided, the later syntax should
 be used for calling the 'jar' tool.

 Will there be progress towards supporting manifest information anytime
 soon within cmake?

 Open a feature request in the bugtracker.


 Please tell me what you think about the proposal.

 Regards,

 --
 Nicolas Desprès
 --

 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

The proposed commits (3 of them, right?) at
https://github.com/polrop/CMake/commits/java-executable-jar look
reasonable to me.

Any objections from people who care about Java to getting these into
CMake 'next' ...?
--

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] Bug fix requests for the *next* release of CMake...

2012-02-07 Thread Stephen Kelly
David Cole wrote:
 Replies requested. Short replies only. Read on. Just a short reply
 with bug numbers or links to the bugs is all we need here. Please move
 specific discussions into the bugs themselves or start a new thread to
 talk about it... Replies on this thread should just be a collector for
 bug numbers.
 

http://public.kitware.com/Bug/view.php?id=12588
Discussion: 
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/2285/focus=2299

Thanks,

--

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] Utilities/cmcurl/CMakeLists.txt patch

2012-02-07 Thread Kedzierski, Artur CIV NSWC Corona, PA13
Can we have an option to set built-in Curl's CA certificate bundle path? 
Currently,
there is no way to override it. 
Unfortunately, I cannot generate a patch using diff as I have to re-type it 
from another
computer.
Could this be added to Utilities/cmcurl/CMakeLists.txt? :

SET(CURL_CA_BUNDLE  CACHE FILEPATH Path to SSL CA Certificate Bundle)
MARK_AS_ADVANCED(CURL_CA_BUNDLE)
IF(CURL_CA_BUNDLE)
  ADD_DEFINITIONS(-DCURL_CA_BUNDLE=${CURL_CA_BUNDLE})
ENDIF(CURL_CA_BUNDLE)

On Linux, I just re-compile CMake to use system's libcurl. However, on Windows, 
I have
to modify the code.
By the way, any chance on having SSL-enabled CMake packages on cmake.org 
website?
Thank You.

--
Artur Kedzierski



smime.p7s
Description: S/MIME cryptographic signature
--

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] Under Visual Studio , allow developers to hit F7 to run the INSTALL target

2012-02-07 Thread david_bjornbak
Developers on our team have found issues with the difference between INSTALL 
and the default build or F7 build all under Visual Studio.  My question is, 
there's a reasonable way to configure cmake or Visual Studio to run the INSTALL 
target when you hit F7 or use the default Build Solution functionality to 
run INSTALL.

We're working a fairly large project and the default setting of having INSTALL 
dependent on ALL or separating out the two targets makes sense when you're 
building the entire project.

However, we allow developers to build sub projects and it makes sense if these 
sub project just install quickly into a larger pre-built installation 
directory.  The confusion currently is, they run ALL_BUILD or F7 and the 
build finishes and they forget to run INSTALL.Particularly we, had 
developers that worked formally on smaller non-Cmake Visual Studio projects and 
not Linux so, they're not used to the make all and then make install defacto 
standard.
This request is similar as the following on Selecting INSTALL target in Visual 
Studio Configuration by default  but, I wanted to see if anyone had any other 
suggestions on this topic.
http://www.cmake.org/pipermail/cmake/2011-April/044025.html

++David-Bjornbak;

--

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] build using separate compiler,assembler,linker

2012-02-07 Thread Alex
Hi all,
Since some days I’m trying to build a toolchain for crosscompiling but 
I stuck so far while trying to execute a buildprocess with two stages. 
According to a makefile I use as template, the processing looks as follows:

Given some .c sourcefiles the makefile executes:

Invoking: Compiler
CTC.EXE mcs0.c –I… --Flags… -o MCS0.src

Invoking: Assembler
ASTC.EXE MCS0.src –Flags… -o MCS0.o

Invoking: Linker
LTC.EXE MCS0.o … librt.a … -I –Flags… -L… 

I create a toolchain file and also some platform configuration for 
compiler and assembler. However I have in particular a problem to invoke the 
assembler. 
That is, when calling add_executable with the c-files as arguments the 
src-files 
are generated. But these files are fed to the linker without the intermediate 
step to build the object files. Of course the linker says ‘unknown file format’.
 
I have tried to provide an assembler configuration that is enabled 
with enable_language before, but this works only for src-files that are 
provided 
to the add_executable() instead of the c-files (c-src with a custom 
target before, calling the compiler). The assembler is not applied to the 
automatically generated .src files in the first step … that means if I 
provide (for testing) some c-files and some src-files, both are processed 
correctly, 
but not the src-files resulting from the compiler during the build of the 
target.

My third option was to implement both the compiler and assembler call 
by means of custom target … however .. don’t’ work until now 
and seems more or less the ugly solution.
 
Has anyone experience with this kind of building … without using custom 
targets? 
What is the general method to enable such two-step build process? 
My goal is to provide a toolchain-configuration with the specification 
of assembler, compiler, linker and archiver … for me is also not completely 
clear 
how to enable an assembler like the compiler with CMAKE_C_COMPILER. 
E.g. CMAKE_C_CREATE_ASSEMBLY_SOURCE has no effect on my configuration.

So far I did not found a comprehensive documentation of this feature(s), even 
in the cmake-book. Therefore I would be very thankfull for any kind of 
information ;-) 

Cu, Alex
--

Powered by www.kitware.com

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

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

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

Re: [CMake] Utilities/cmcurl/CMakeLists.txt patch

2012-02-07 Thread Jean-Christophe Fillion-Robin
There is a corresponding issue in the tracker:
http://www.cmake.org/Bug/view.php?id=11743
Jc

On Tue, Feb 7, 2012 at 2:38 PM, Kedzierski, Artur CIV NSWC Corona, PA13 
artur.kedzier...@navy.mil wrote:

 Can we have an option to set built-in Curl's CA certificate bundle path?
 Currently,
 there is no way to override it.
 Unfortunately, I cannot generate a patch using diff as I have to re-type
 it from another
 computer.
 Could this be added to Utilities/cmcurl/CMakeLists.txt? :

 SET(CURL_CA_BUNDLE  CACHE FILEPATH Path to SSL CA Certificate Bundle)
 MARK_AS_ADVANCED(CURL_CA_BUNDLE)
 IF(CURL_CA_BUNDLE)
  ADD_DEFINITIONS(-DCURL_CA_BUNDLE=${CURL_CA_BUNDLE})
 ENDIF(CURL_CA_BUNDLE)

 On Linux, I just re-compile CMake to use system's libcurl. However, on
 Windows, I have
 to modify the code.
 By the way, any chance on having SSL-enabled CMake packages on 
 cmake.orgwebsite?
 Thank You.

 --
 Artur Kedzierski


 --

 Powered by www.kitware.com

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

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

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




-- 
+1 919 869 8849
--

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 CMake with icc via configuration options when needing interprocedural optimization?

2012-02-07 Thread Alexander Neundorf
Hi Janitor,

On Tuesday 07 February 2012, janitor 048 wrote:
 Hello,
 
 this is a question I recently asked on stackoverflow (
 http://stackoverflow.com/questions/9129233/recommended-ways-to-use-cmake-wi
 th-icc-via-configuration-options) but that has not received any response
 since then. Maybe this mailing list is a better place to ask... Here goes
 
 I would like to use the Intel compiler icc (or icpc) with a CMake-based
 project (on Linux for what it's worth). I can of course export the CXX
 variable when calling cmake, e.g. like
 
 CXX=icpc cmake ../
 
 and this works fine. I would however like to make this choice available via
 a custom option. For this I parse custom option, e.g.
 
 cmake -DMY_COMPILER_OPTION=Intel ..
 
 as
 
 IF (MY_COMPILER_OPTION STREQUAL Intel)
   MESSAGE(STATUS ** Compiling with Intel settings **)
   SET(CMAKE_CXX_COMPILER icpc)
   SET(CMAKE_CXX_FLAGS_RELEASE -O3 -w)
   SET(CMAKE_CXX_FLAGS_DEBUG -g)
 ENDIF ()

Don't do that, this is too late in the initialization process.
The recommended way is to set the CXX environment variable. This is only 
necessary during the initial cmake run, afterwards this is stored in the cmake 
cmake cache.
It should also work to preset the compiler variables:
cmake -DCMAKE_C_COMPILER=icc -DCMAKE_CXX_COMPILER=icpc 

(I didn't check, but it should work).

Alex
--

Powered by www.kitware.com

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

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

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


Re: [CMake] Utilities/cmcurl/CMakeLists.txt patch

2012-02-07 Thread Kedzierski, Artur CIV NSWC Corona, PA13
The issue is corresponding to the last question in my email but not to the 
patch.
Should I create a new issue in the tracker?

--
Artur Kedzierski


-Original Message-
From: Jean-Christophe Fillion-Robin [mailto:jchris.filli...@kitware.com] 
Sent: Tuesday, February 07, 2012 12:38
To: Kedzierski, Artur CIV NSWC Corona, PA13
Cc: cmake@cmake.org
Subject: Re: [CMake] Utilities/cmcurl/CMakeLists.txt patch

There is a corresponding issue in the tracker: 
http://www.cmake.org/Bug/view.php?id=11743
Jc


On Tue, Feb 7, 2012 at 2:38 PM, Kedzierski, Artur CIV NSWC Corona, PA13 
artur.kedzier...@navy.mil wrote:


Can we have an option to set built-in Curl's CA certificate bundle 
path? Currently,
there is no way to override it.
Unfortunately, I cannot generate a patch using diff as I have to 
re-type it from another
computer.
Could this be added to Utilities/cmcurl/CMakeLists.txt? :

SET(CURL_CA_BUNDLE  CACHE FILEPATH Path to SSL CA Certificate 
Bundle)
MARK_AS_ADVANCED(CURL_CA_BUNDLE)
IF(CURL_CA_BUNDLE)
 ADD_DEFINITIONS(-DCURL_CA_BUNDLE=${CURL_CA_BUNDLE})
ENDIF(CURL_CA_BUNDLE)

On Linux, I just re-compile CMake to use system's libcurl. However, on 
Windows, I have
to modify the code.
By the way, any chance on having SSL-enabled CMake packages on 
cmake.org website?
Thank You.

--
Artur Kedzierski


--

Powered by www.kitware.com

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

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

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





-- 
+1 919 869 8849




smime.p7s
Description: S/MIME cryptographic signature
--

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] [Java] - Adding manifest information to a jar file

2012-02-07 Thread Nicolas Desprès
2012/2/7 David Cole david.c...@kitware.com:
[...]

 The proposed commits (3 of them, right?) at
 https://github.com/polrop/CMake/commits/java-executable-jar look
 reasonable to me.

Yes the three of them.

[...]

-- 
Nicolas Desprès
--

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 for cygwin

2012-02-07 Thread marco atzeri

Hi Bill,
any plan to update the cygwin package ?

Currently we are still on 2.8.4-1

Regards
Marco
--

Powered by www.kitware.com

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

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

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


Re: [CMake] cmake for cygwin

2012-02-07 Thread Robert Dailey
+1 to this as well

-
Robert Dailey


On Tue, Feb 7, 2012 at 4:16 PM, marco atzeri marco.atz...@gmail.com wrote:

 Hi Bill,
 any plan to update the cygwin package ?

 Currently we are still on 2.8.4-1

 Regards
 Marco
 --

 Powered by www.kitware.com

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

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

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

--

Powered by www.kitware.com

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

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

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

Re: [CMake] Enhancement to CHECK_C_RUNS_SOURCE

2012-02-07 Thread Clifford Yapp
On Thu, Feb 2, 2012 at 11:59 AM, Alexander Neundorf a.neundorf-w...@gmx.net
 wrote:


 I think so.
 In this case, this should also be added to CheckCXXSourceRuns,
 CheckCSourceCompiles and CheckCXXSourceCompiles.

 Alex


http://cmake.org/Bug/view.php?id=12944

Patch changes all four files and addes a note to the documentation at the
beginning of each file.

Cheers,
Cliff
--

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 generated DEB package can not create directories

2012-02-07 Thread Ralf Lange
I test it and it works. CMake 2.8.7 fix the problem. Great.

Thanks

Ralf

On Mon, 2012-02-06 at 20:05 +0100, Eric Noulard wrote:

 2012/2/6 Ralf Lange ralf.la...@longsoft.de:
  The CMake version is 2.8.2.
  The system is Debian 6.0.4 (squeez).
  The kernel is 2.6.32-5-amd64.
  The Desktop is Gnome 2.30.2.
 
 Could you try, cmake 2.8.7
 (may be this fix
  http://www.cmake.org/Bug/view.php?id=10325 could solve your problem)
 and/or
 run cpack in fakeroot like:
 
 $ cd /home/ralf/Animation-Dev/qStopMotion/qstopmotion-buil-makefile
 $ fakeroot cpack -G DEB
 
 Then retry the installation.
 
  CPack generates the deb package. Than I open the package using GDebi
  Packet Installer. The installer ask for the superuser password and ends
  without installation. The error message is:
  dpkg: Error processing
  of 
  /home/ralf/Animation-Dev/qStopMotion/qstopmotion-buil-makefile/qstopmotion-0.9.10-Linux.deb
   (--install):
  /usr/share/qstopmotion/graphics/qstopmotion_logo_transparent_75.png.dpkg-new
   can not be created (...): File or Directory not found.
 
 is the qstopmotion this project:
 http://www.qstopmotion.org/english/download_sources.html
 
 If yes did you made some change or could I theoretically try to
 reproduce the issue
 using the source I can find on this site?
 
  When I create all the directories on the command line bevor I start the
  installer, than it works.
 
 could you put the result of:
 
 dpkg-deb --contents yourdebfile.deb
 
 in a text file and send it to me?
 
 


--

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 generated DEB package can not create directories

2012-02-07 Thread Eric Noulard
2012/2/8 Ralf Lange ralf.la...@longsoft.de:
 I test it and it works. CMake 2.8.7 fix the problem. Great.

Ok fine, thanks.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.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


[Cmake-commits] CMake branch, master, updated. v2.8.7-273-g6c7a622

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  6c7a622279a8d02cd01b7c19d7eb3091b3765a23 (commit)
   via  c4a0bcea775981dea86d527f66161c98f5e05e95 (commit)
  from  45bba995381bd88895eb2e15ac9cdf91dc5c5080 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6c7a622279a8d02cd01b7c19d7eb3091b3765a23
commit 6c7a622279a8d02cd01b7c19d7eb3091b3765a23
Merge: 45bba99 c4a0bce
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:33:01 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:33:01 2012 -0500

Merge topic 'nsis-user-perm-issue-12923'

c4a0bce CPack: Fix NSIS handling of privileged users (#12923)


---

Summary of changes:
 Modules/NSIS.template.in |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-275-g941d533

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  941d533cc31cacde79e8fb3a6b61f0e93ccc3740 (commit)
   via  de289462efc070d831bf5e49d63fb47e1de57769 (commit)
  from  6c7a622279a8d02cd01b7c19d7eb3091b3765a23 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=941d533cc31cacde79e8fb3a6b61f0e93ccc3740
commit 941d533cc31cacde79e8fb3a6b61f0e93ccc3740
Merge: 6c7a622 de28946
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:33:23 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:33:23 2012 -0500

Merge topic 'find-vcexpress'

de28946 Find VC Express during default generator selection (#12917)


---

Summary of changes:
 Source/cmake.cxx |   23 +++
 1 files changed, 15 insertions(+), 8 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-280-g66145a3

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  66145a3e3b27921e6da0a06822c870664a528e34 (commit)
   via  ed1b12624dfe7f4b6afeb557aabb091904918bc7 (commit)
   via  2dee9294969ff5ef85a4dacb13de70b8a9de03db (commit)
   via  3c4b4fffd0a6739e8771e4d552d98d21d294a84b (commit)
   via  9d72b25a861bdcc69bf08e7494884027c341f7c9 (commit)
  from  941d533cc31cacde79e8fb3a6b61f0e93ccc3740 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=66145a3e3b27921e6da0a06822c870664a528e34
commit 66145a3e3b27921e6da0a06822c870664a528e34
Merge: 941d533 ed1b126
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:33:43 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:33:43 2012 -0500

Merge topic 'AllFindModules-test'

ed1b126 CMakeOnly.AllFindModules: require version for some modules
2dee929 CMakeOnly.AllFindModules: suppress two modules from testing
3c4b4ff CMakeOnly.AllFindModules: always check FindQt
9d72b25 CMakeOnly.AllFindModules: clean up the Qt3/Qt4 code


---

Summary of changes:
 Tests/CMakeOnly/AllFindModules/CMakeLists.txt |   51 +++-
 1 files changed, 40 insertions(+), 11 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-284-gaab8510

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  aab8510c256e6c1174218317c30541ea3594cf97 (commit)
   via  31826b5166f0921d34625d86e82dd73fb47652d5 (commit)
  from  c41020e873a6c7e3eff3293d639f382be6af3b18 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aab8510c256e6c1174218317c30541ea3594cf97
commit aab8510c256e6c1174218317c30541ea3594cf97
Merge: c41020e 31826b5
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:34:02 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:34:02 2012 -0500

Merge topic 'perl-version'

31826b5 FindPerl{,Libs}: move version detection into FindPerl


---

Summary of changes:
 Modules/FindPerl.cmake |   39 ---
 Modules/FindPerlLibs.cmake |   36 
 2 files changed, 48 insertions(+), 27 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-289-ga3e7913

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  a3e791389735224426de524db2af938602201395 (commit)
   via  5d18851b25af4f363d72371a5a6492741436eb37 (commit)
   via  3cab24a9740ad1d35e548629f6dda12e166ef49e (commit)
  from  38e6757cd3192b4c6048409feada7a8c397504cf (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a3e791389735224426de524db2af938602201395
commit a3e791389735224426de524db2af938602201395
Merge: 38e6757 5d18851
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:34:39 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:34:39 2012 -0500

Merge topic 'AddTopLevelForComponent'

5d18851 CPackArchive restore default behavior and provide new variable.
3cab24a CPack  Add top level directory in component install for Archive 
Generators


---

Summary of changes:
 Source/CPack/cmCPackArchiveGenerator.cxx |   11 +--
 Source/CPack/cmCPackGenerator.cxx|5 +
 2 files changed, 14 insertions(+), 2 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-291-g0d7727d

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  0d7727d1ccdf74dc5eb4298c8ecdea11dfe88cf1 (commit)
   via  bf2e385397d6feeafbc3d3df45bac47b325c6c7a (commit)
  from  a3e791389735224426de524db2af938602201395 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0d7727d1ccdf74dc5eb4298c8ecdea11dfe88cf1
commit 0d7727d1ccdf74dc5eb4298c8ecdea11dfe88cf1
Merge: a3e7913 bf2e385
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:34:49 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:34:49 2012 -0500

Merge topic 'change-trilinos-submit-url'

bf2e385 Tests: Update drop site value for the Trilinos contract test


---

Summary of changes:
 Tests/Contracts/Trilinos-10-6/Patch.cmake |   18 ++
 1 files changed, 18 insertions(+), 0 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-294-g43b463c

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  43b463cdfc8f1e2e595ab9cf0feec89b4b782e0b (commit)
   via  a03447b3dfb448b402a0451e4e436a135fee366e (commit)
   via  9e01aefd24cd23878bd88c2f3cae62b5e28802b0 (commit)
  from  0d7727d1ccdf74dc5eb4298c8ecdea11dfe88cf1 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=43b463cdfc8f1e2e595ab9cf0feec89b4b782e0b
commit 43b463cdfc8f1e2e595ab9cf0feec89b4b782e0b
Merge: 0d7727d a03447b
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:35:00 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:35:00 2012 -0500

Merge topic 'VS11-WinRT-project-issue-12930'

a03447b VS: Simplify ;-separated attribute value parsing
9e01aef VS: Add support for WinRT project properties (#12930)


---

Summary of changes:
 Source/cmTarget.cxx|   10 +
 Source/cmVisualStudio10TargetGenerator.cxx |   56 +++
 Source/cmVisualStudio10TargetGenerator.h   |1 +
 3 files changed, 50 insertions(+), 17 deletions(-)


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-298-g3921f1a

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  3921f1a559053dcf8c894321cb505dc4d24b3685 (commit)
   via  daa4101619514d2b7eebbce7a73cd2149b7679b8 (commit)
  from  986981ea03cac860c0128214144b97f18979a1ae (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3921f1a559053dcf8c894321cb505dc4d24b3685
commit 3921f1a559053dcf8c894321cb505dc4d24b3685
Merge: 986981e daa4101
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:35:21 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:35:21 2012 -0500

Merge topic 'remove-unused-test-code'

daa4101 Remove unused test code


---

Summary of changes:
 Tests/CMakeLists.txt |   78 ++
 Tests/ConvLibrary/CMakeLists.txt |   20 --
 Tests/ConvLibrary/bar.c  |4 --
 Tests/ConvLibrary/bartest.cxx|   37 --
 Tests/ConvLibrary/foo.cxx|4 --
 Tests/ConvLibrary/sub1/car.cxx   |4 --
 6 files changed, 29 insertions(+), 118 deletions(-)
 delete mode 100644 Tests/ConvLibrary/CMakeLists.txt
 delete mode 100644 Tests/ConvLibrary/bar.c
 delete mode 100644 Tests/ConvLibrary/bartest.cxx
 delete mode 100644 Tests/ConvLibrary/foo.cxx
 delete mode 100644 Tests/ConvLibrary/sub1/car.cxx


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-305-g7dcfd9a

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  7dcfd9aaf621672b3006fd5b084a17409d4435b2 (commit)
   via  495f8998458f06fac250d62ba948e21c2429565f (commit)
  from  3f359596a0984334e861fd0f64452ee9da6a26e6 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7dcfd9aaf621672b3006fd5b084a17409d4435b2
commit 7dcfd9aaf621672b3006fd5b084a17409d4435b2
Merge: 3f35959 495f899
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:36:21 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Feb 7 15:36:21 2012 -0500

Merge topic 'update-mini5-release-qt'

495f899 Update version of Qt for dashmacmini5 produced release binaries


---

Summary of changes:
 Utilities/Release/dashmacmini5_release.cmake |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


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


[Cmake-commits] CMake branch, next, updated. v2.8.7-2499-g200b760

2012-02-07 Thread David Cole
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, next has been updated
   via  200b7602eab3af933a85a8c8c85f11a9cff175b7 (commit)
   via  7dcfd9aaf621672b3006fd5b084a17409d4435b2 (commit)
   via  3f359596a0984334e861fd0f64452ee9da6a26e6 (commit)
   via  2619d765567bd4bee8e5976a2c5967d36487cdd6 (commit)
   via  3921f1a559053dcf8c894321cb505dc4d24b3685 (commit)
   via  986981ea03cac860c0128214144b97f18979a1ae (commit)
   via  43b463cdfc8f1e2e595ab9cf0feec89b4b782e0b (commit)
   via  0d7727d1ccdf74dc5eb4298c8ecdea11dfe88cf1 (commit)
   via  a3e791389735224426de524db2af938602201395 (commit)
   via  38e6757cd3192b4c6048409feada7a8c397504cf (commit)
   via  aab8510c256e6c1174218317c30541ea3594cf97 (commit)
   via  c41020e873a6c7e3eff3293d639f382be6af3b18 (commit)
   via  66145a3e3b27921e6da0a06822c870664a528e34 (commit)
   via  941d533cc31cacde79e8fb3a6b61f0e93ccc3740 (commit)
   via  6c7a622279a8d02cd01b7c19d7eb3091b3765a23 (commit)
   via  45bba995381bd88895eb2e15ac9cdf91dc5c5080 (commit)
  from  d3704dd6d8e8714b23fae3fe57cbe1d06a4a846f (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=200b7602eab3af933a85a8c8c85f11a9cff175b7
commit 200b7602eab3af933a85a8c8c85f11a9cff175b7
Merge: d3704dd 7dcfd9a
Author: David Cole david.c...@kitware.com
AuthorDate: Tue Feb 7 15:37:42 2012 -0500
Commit: David Cole david.c...@kitware.com
CommitDate: Tue Feb 7 15:37:42 2012 -0500

Merge branch 'master' into next


---

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


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


[Cmake-commits] CMake branch, master, updated. v2.8.7-306-g59ecc2c

2012-02-07 Thread KWSys Robot
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.

The branch, master has been updated
   via  59ecc2c8ac4f6e4e3e9b20a37763365060d8bb6d (commit)
  from  7dcfd9aaf621672b3006fd5b084a17409d4435b2 (commit)

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

- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=59ecc2c8ac4f6e4e3e9b20a37763365060d8bb6d
commit 59ecc2c8ac4f6e4e3e9b20a37763365060d8bb6d
Author: KWSys Robot kwro...@kitware.com
AuthorDate: Wed Feb 8 00:05:06 2012 -0500
Commit: KWSys Robot kwro...@kitware.com
CommitDate: Wed Feb 8 00:05:06 2012 -0500

KWSys Nightly Date Stamp

diff --git a/Source/kwsys/kwsysDateStamp.cmake 
b/Source/kwsys/kwsysDateStamp.cmake
index 2cbfe26..17f7339 100644
--- a/Source/kwsys/kwsysDateStamp.cmake
+++ b/Source/kwsys/kwsysDateStamp.cmake
@@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR  2012)
 SET(KWSYS_DATE_STAMP_MONTH 02)
 
 # KWSys version date day component.  Format is DD.
-SET(KWSYS_DATE_STAMP_DAY   07)
+SET(KWSYS_DATE_STAMP_DAY   08)

---

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


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