[cmake-developers] [CMake 0014444]: INSTALL TARGET command does not work with targets outside the current directory

2013-09-26 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=1 
== 
Reported By:Blaise Gassend
Assigned To:
== 
Project:CMake
Issue ID:   1
Category:   (No Category)
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2013-09-26 18:14 EDT
Last Modified:  2013-09-26 18:14 EDT
== 
Summary:INSTALL TARGET command does not work with targets
outside the current directory
Description: 
If you try to INSTALL TARGET a target that was defined in a different directory,
CMake fails with an error. 

This is behaviour is really annoying. We are trying to install only libraries
that get used by executables that need to be installed. However, if the library
and executable are defined in different directories, this bug prevents you from
INSTALLing the library at the place where you know you need to install it. Using
INSTALL FILES partially works, but causes stripping and rpath changing to break,
as CMake no longer recognizes the library as a library.

If this behaviour is a feature, it would be really nice to have documentation of
why it is a feature. (I can't seem to be able to define targets with the same
name in different directories, so why on earth would INSTALL TARGETS be the only
command that only considers 

Steps to Reproduce: 
I'll attach a tarball for a directory that reproduces this. To reproduce:

cd cmake_deb_test
mkdir build
cd build
cmake ..

[ret=2] blaise@bnl: /st/stor1/blaise/work/cmake_deb_test/build $ cmake ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/lib/ccache/gcc
-- Check for working C compiler: /usr/lib/ccache/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
m-- Check for working CXX compiler: /usr/lib/ccache/c++
ak-- Check for working CXX compiler: /usr/lib/ccache/c++ -- works
-- Detecting CXX compiler ABI info
e -- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:10 (install):
  install TARGETS given target "mylib2" which does not exist in this
  directory.


-- Configuring incomplete, errors occurred!


Additional Information: 
The following patch fixes the problem. I don't understand the cmake philosophy
enough to know if it hopelessly breaks something else though.


Description: INSTALL TARGETS will find non-local targets
 .
 cmake (2.8.7-0ubuntu5) precise-proposed; urgency=low
 .
   * Fix corrupted tarballs when using DEB generator in CPack.
 (LP: http://www.cmake.org/Bug/view.php?id=972419)
Author: David Dunsmore 
Bug-Ubuntu: https://bugs.launchpad.net/bugs/972419
 
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: http://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 

--- cmake-2.8.7.orig/Source/cmInstallCommand.cxx
+++ cmake-2.8.7/Source/cmInstallCommand.cxx
@@ -350,8 +350,8 @@ bool cmInstallCommand::HandleTargetsMode
   targetIt!=targetList.GetVector().end();
   ++targetIt)
 {
-  // Lookup this target in the current directory.
-  if(cmTarget* target=this->Makefile->FindTarget(targetIt->c_str()))
+  // Lookup this target 
+  if(cmTarget* target=this->Makefile->FindTargetToUse(targetIt->c_str()))
 {
 // Found the target.  Check its type.
 if(target->GetType() != cmTarget::EXECUTABLE &&
@@ -373,7 +373,7 @@ bool cmInstallCommand::HandleTargetsMode
 // Did not find the target.
 cmOStringStream e;
 e << "TARGETS given target \"" << (*targetIt)
-  << "\" which does not exist in this directory.";
+  << "\" which does not exist.";
 this->SetError(e.str().c_str());
 return false;
 } 

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2013-09-26 18:14 Blaise Gassend New Issue
2013-09-26 18:14 Blaise Gassend File Added: cmake_deb_test.tgz  
 
==

--

Powered by www.kitware.com

Visit other Kitware open-sou

Re: [cmake-developers] CMake*.app/Contents/Info.plist version information

2013-09-26 Thread quest4insight 
On Sep 26, 2013, at 1:22 PM, Sean McBride  wrote:

> On Thu, 26 Sep 2013 13:11:21 -0700, quest4insi...@earthlink.net said:
> 
>> For the Mac OS X build of CMake, can the version number be added to
>> CMake*.app/Contents/Info.plist ?
>> 
>> The Info.plist version entries are currently empty ...
>> 
>>  CFBundleShortVersionString
>>  
>>  CFBundleVersion
>>  
> 
> FYI I have filed a bug about that a couple of years ago:
> 

OK.  Thanks.  I added a note to the existing bug report 11694.

The motivation for the question is that, apparently, www.macupdate.com software 
listing service needs the version information to be present the info.plist 
file. 

Best regards,

--Marc

--

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-developers] [CMake 0014443]: FindwxWidgets reports incorrect debug definitions

2013-09-26 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=14443 
== 
Reported By:philrosenberg
Assigned To:
== 
Project:CMake
Issue ID:   14443
Category:   (No Category)
Reproducibility:have not tried
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2013-09-26 16:45 EDT
Last Modified:  2013-09-26 16:45 EDT
== 
Summary:FindwxWidgets reports incorrect debug definitions
Description: 
On Windows FindwxWidgets fills wxWidgets_DEFINITIONS_DEBUG with _DEBUG;
__WXDEBUG__ even when wxWidgets_CONFIGURATION does not include a d, i.e. it is
not a debug configuration.
On linux wxWidgets_DEFINITIONS_DEBUG is only filled for a debug configuration so
the behaviour needs to be made the same on both systems.

Steps to Reproduce: 
Behaviour was discovered when building PLplot. The devs have just implemented a
workaround but any version dated 25th Sep 2013 or before shows this problem
which causes linker errors
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2013-09-26 16:45 philrosenberg  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

Re: [cmake-developers] CMake*.app/Contents/Info.plist version information

2013-09-26 Thread Sean McBride 
On Thu, 26 Sep 2013 13:11:21 -0700, quest4insi...@earthlink.net said:

>For the Mac OS X build of CMake, can the version number be added to
>CMake*.app/Contents/Info.plist ?
>
>The Info.plist version entries are currently empty ...
>
>   CFBundleShortVersionString
>   
>   CFBundleVersion
>   

FYI I have filed a bug about that a couple of years ago:


Cheers,

-- 

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com 
Mac Software Developer  Montréal, Québec, Canada


--

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-developers] CMake*.app/Contents/Info.plist version information

2013-09-26 Thread quest4insight 
For the Mac OS X build of CMake, can the version number be added to 
CMake*.app/Contents/Info.plist ?

The Info.plist version entries are currently empty ...

CFBundleShortVersionString

CFBundleVersion


Thanks.

--Marc 
--

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-developers] bash-completion and "<" ">" character

2013-09-26 Thread Eric Noulard 
Switching thread of discussion.

2013/9/25 Matthew Woehlke :
> On 2013-09-25 16:14, Eric Noulard wrote:
>>
>> 2013/9/25 Matthew Woehlke :
>>>
>>> On 2013-09-25 12:18, Eric Noulard wrote:

 $ cmake --help-variable CMAKE_>>
>>> If you  at the end of this line, aren't you trying to complete a
>>> local
>>> file name 'L'?
>>
>> Yes and in fact it "restart" the completion, i.e. you get
>> cmake --help-variable CMAKE_
> That's odd...
>
> Maybe I don't understand what context you are in.
>
> If I type exactly what you showed at a bash prompt, then according to bash
> syntax (and verified by hitting 'enter' and receiving the expected error)
> 'L' is the name of a file which is redirected to cmake's stdin.

Yes this is the case if you type 'enter'
but if you type 'tab' then completion code is invoked

> Therefore, I
> would expect the completion context if one hits 'tab' having types exactly
> that to be 'L', in the context of a stdin redirection.

This is not the case in the first place because bash completion
already knows that you are in "--help-variable" case.

> It sounds like you are seeing something different. I'm by no means a bash
> completion expert, but that seems odd. Maybe you should ask on the bash list
> if you haven't already?

Nope, I will.

>>> Does it work if you escape the '<'?
>>
>>
>> I don't really know how to do that inside a partial completion.
>> The only option I see is to forcibly add a ' " 'prefix to the completion.
>
> Again, maybe I am confused. Did *you* type the '<'? Or was the '<' emitted
> due to partial completion?

I typed " If the former, does completion work better if you instead try to complete:
>
>
> $ cmake --help-variable CMAKE_\ $ cmake --help-variable CMAKE__
second  $ cmake --help-variable CMAKE_CMAKE__

> If the latter... I'm not sure (see previous comment about not being a bash
> completion expert). Still, this works for e.g. file names, usually spaces
> are escaped automatically. I wonder if you were to simply do a replacement
> of '<' with '\<' in generated completions if it would work better?

I tried that with no success.
I will try to ask my question on bash-completion ML.

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

[cmake-developers] [CMake 0014442]: Support of different toolchains during VS2012 project generation

2013-09-26 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=14442 
== 
Reported By:ilebedie
Assigned To:
== 
Project:CMake
Issue ID:   14442
Category:   CMake
Reproducibility:N/A
Severity:   feature
Priority:   none
Status: new
== 
Date Submitted: 2013-09-26 06:33 EDT
Last Modified:  2013-09-26 06:33 EDT
== 
Summary:Support of different toolchains during VS2012
project generation
Description: 
Visual Studio 2012 allows to choose different toolchains to build it's
projects(e.g. Visual Studio 2012 (v110), Intel C++ Compiler XE 13.0,
Windows7.1SDK)
When trying to set compiler in cmakelists.txt (include(CMakeForceCompiler)
CMAKE_FORCE_C_COMPILER(icl "Intel C Compiler") ) cmake generates VS project
files with default compiler(v110).
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2013-09-26 06:33 ilebedie   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-developers] [CMake 0012886]: Add a manifest or main-class file to the created jar

2013-09-26 Thread Sebastian Pölsterl 

Hi everyone,

since this bug did not see any progress for more than a year, I wanted 
to draw attention to the proposed patch I attached to 
http://public.kitware.com/Bug/view.php?id=12886


I would appreciate it if someone could review it.

Thanks!

--
Sebastian Pölsterl
--

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