Re: [cmake-developers] Unknown CMake bugs

2015-01-21 Thread Rolf Eike Beer
  http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/devel/cmake/patches/patch-b
  ootstrap?rev=1.7content-type=text/x-cvsweb-markup
 They just want to bootstrap with Ninja, except on specific
 architectures.  Not an upstream concern.

Yes, because:

XXX: broken on arm and m88k

It's the same as with the other stuff: as long as they don't report what 
actually went wrong it will be hard to fix.

I'll see if I can do a CMake run on a BeagleBoard on Linux in the next time, 
maybe that will give a clue.

Eike
-- 

signature.asc
Description: This is a digitally signed message part.
-- 

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-developers

[cmake-developers] [CMake 0015363]: CMake 3.1.0 with Visual Studio 12 2013 ARM generator for WP8.1 fails to compile simple test program if path length 91 chars

2015-01-21 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15363 
== 
Reported By:Moshe Rubin
Assigned To:
== 
Project:CMake
Issue ID:   15363
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2015-01-21 13:45 EST
Last Modified:  2015-01-21 13:45 EST
== 
Summary:CMake 3.1.0 with Visual Studio 12 2013 ARM
generator for WP8.1 fails to compile simple test program if path length  91
chars
Description: 
When running CMake with the Visual Studio 12 2013 ARM generator to create a
Windows Phone 8.1 project file, the run will fail with the message:

quote
The C compiler C:/Program Files (x86)/Microsoft Visual Studio
12.0/VC/bin/x86_arm/cl.exe is not able to compile a simple test program.
/quote

I have been able to confirm that CMake will fail consistently if the full path
to the folder from which CMake is being run is greater than ninety (90)
characters.  If equal to, or less, than 90 characters, the run succeeds.

I have only been able to consistently reproduce this problem with the Visual
Studio 12 2013 ARM generator.


Steps to Reproduce: 
I attach a Windows batch file called cmake-mantis.bat that will reproduce the
two cases, successful and unsuccessful.  Here are the steps:

(1) Copy the Windows batch file cmake-matis.bat to any folder in the file
system.

(2) cd to above folder.

(3) To reproduce an unsuccessful run, execute the following command:

cmake-mantis.bat bad

In this case, the folder from where CMake is execute is:

   
%TEMP%\CMakeTest\12345678901234567890\12345678901234567890\12345678901234567890\12345678901234567890\12345678901234567890

(4) To reproduce a successful run, execute the following command:

cmake-mantis.bat good

In this case, the folder from which CMake is executed is:

%TEMP%\CMakeTest

(5) The batch file leaves the try_compile build trees intact for debugging
purposes.


Additional Information: 
I added the --trace command line option for both the 'good' and the 'bad' runs
and have uploaded them as the files foo.good and foo.bad.  Doing a diff on
them both shows the following strange phenomenon: both logs are essentially
identical (except for folder names) until foo.good:2649 and foo.bad:2650.  At
this point, inexplicably, CMAKE_C_COMPILER_WORKS is TRUE in foo.good but FALSE
in goo.bad:

Starting at line 2649 in foo.good:

snippet
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(56):  if(NOT
CMAKE_C_COMPILER_WORKS )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(65):  else()
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(66): 
if(C_TEST_WAS_RUN )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(67): 
PrintTestCompilerStatus(C  -- works )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(16): 
if(CMAKE_GENERATOR MATCHES Make )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(18):  else()
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(19): 
message(STATUS Check for working ${LANG} compiler using:
${CMAKE_GENERATOR}${MSG} )
-- Check for working C compiler using: Visual Studio 12 2013 ARM -- works
/snippet

Starting at line 2650 in foo.bad:

snippet
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(56):  if(NOT
CMAKE_C_COMPILER_WORKS )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCCompiler.cmake(57): 
PrintTestCompilerStatus(C  -- broken )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(16): 
if(CMAKE_GENERATOR MATCHES Make )
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(18):  else()
C:/Program Files
(x86)/CMake/share/cmake-3.1/Modules/CMakeTestCompilerCommon.cmake(19): 
message(STATUS Check for working ${LANG} compiler using:
${CMAKE_GENERATOR}${MSG} )
-- Check for working C compiler using: Visual Studio 12 2013 ARM -- broken
/snippet

There are no differences in the traces leading up to these points to explain the
discrepancy.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-01-21 13:45 Moshe RubinNew Issue   

[cmake-developers] Cmake 2.8.8 -- can't find curses.h

2015-01-21 Thread Sharath Prasad
Hello.

I am trying to use a specific version of cmake (v2.8.8). I also need ccmake
(v2.8.8). I located the folders uploaded for this release. I plan to use it
on ubuntu. I downloaded cmake folders and extracted all the folders related
to Linux. However, only one folder has options to build from scratch. Other
folders have binaries that do not run on my machine.

The folder that compiles from scratch cannot locate CURSES or NCURSES and
has trouble locating curses.h

So ccmake does not work. If I install ccmake, it updates to the latest
version 2.8.12 or so.

I need v2.8.8 specifically, Can you help?


Thanks,
Sharath
-- 

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-developers

Re: [cmake-developers] Cmake 2.8.8 -- can't find curses.h

2015-01-21 Thread David Cole via cmake-developers
This is a pre-built Linux binary that should work on that system, and
should include ccmake:

http://www.cmake.org/files/v2.8/cmake-2.8.8-Linux-i386.tar.gz

If you can't run it, it's probably because you're on an x64 box, and
you need the run the 32-bit exes and libs library -- hopefully
somebody else can chime in with the package to install, because I can
never remember the name of it.


HTH,
David C.



On Wed, Jan 21, 2015 at 10:57 AM, Sharath Prasad
prasad.shar...@gmail.com wrote:
 Hello.

 I am trying to use a specific version of cmake (v2.8.8). I also need ccmake
 (v2.8.8). I located the folders uploaded for this release. I plan to use it
 on ubuntu. I downloaded cmake folders and extracted all the folders related
 to Linux. However, only one folder has options to build from scratch. Other
 folders have binaries that do not run on my machine.

 The folder that compiles from scratch cannot locate CURSES or NCURSES and
 has trouble locating curses.h

 So ccmake does not work. If I install ccmake, it updates to the latest
 version 2.8.12 or so.

 I need v2.8.8 specifically, Can you help?


 Thanks,
 Sharath

 --

 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-developers
-- 

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-developers


Re: [cmake-developers] [PATCH] FindCUDA: add cuSOLVER

2015-01-21 Thread Brad King
On 01/21/2015 03:19 PM, Andrew Seidl wrote:
 Here's a small patch for FindCUDA for finding the new cuSOLVER
 library included in the upcoming CUDA 7.0.

Applied, thanks:

 FindCUDA: Add cuSOLVER library from CUDA 7.0
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e56c9327

-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-developers


[cmake-developers] [PATCH] FindCUDA: add cuSOLVER

2015-01-21 Thread Andrew Seidl
Hi all,

Here's a small patch for FindCUDA for finding the new cuSOLVER library
included in the upcoming CUDA 7.0.

Andrew


0001-FindCUDA-add-cuSOLVER.patch
Description: Binary data
-- 

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-developers

[cmake-developers] Improving Vim support in CMake

2015-01-21 Thread Ben Boeckel
Hi all,

Any Vim users out there who would like to try out the changes I've made
to the Vim files shipped with CMake can grab it from either stage
(vim-support-overhaul) or my GitHub fork[1]. It is not in next yet since
I expect further changes to come and that would only make unnecessary
churn on the dashboards.

List of improvements to the syntax file:

  - drop support for  7.0 (which is 7.5 years old now);
  - add support for Lua-style comments;
  - update the list of system variables;
  - update the list of operators;
  - make only commands case-insensitive;
  - update the list of built-in commands (and deprecated ones);
  - highlight user-defined function and macro calls; and
  - tweak colors a bit.

One thing which was also changed that isn't in that list (from the
commit message) is that deprecated commands are now highlighted as
WarningMsg so they stand out.

The cmake-help code has also been changed to use 'K' rather than F1 to
get help about a command (and the global binding was removed since I
don't expect it is used much and it's only going to be a surprise).

I don't have enough experience with indentation logic, but that also
needs some work.

Testers and comments welcome :) .

--Ben

[1]https://github.com/mathstuf/CMake/tree/vim-support-overhaul
-- 

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-developers


Re: [cmake-developers] Introduction and volunteering for the Matlab package

2015-01-21 Thread Brad King
On 01/21/2015 12:01 PM, Raffi Enficiaud wrote:
 Ok. What do you think about mimicking the mex compiler in terms
 of options set to the compiler? The -Wl,--exclude-libs,ALL is in
 fact set by the mex compiler for compiling the mex extensions under
 Linux. Then I will just drop the REDUCE_VISIBILITY from the
 interface and add some doc about the best practices that work better.

I think suggesting it in the documentation is fine.  If some common
cross-platform solutions evolve then we can revisit adding official
support.

 But I have a quick question about the proper way of adding a test:
[snip]
 should fail because of a component lacking the the find_package option

The best place to put tests covering bad CMake code and error cases
is under the Tests/RunCMake infrastructure.  That allows explicit
matching of return codes and error messages.

Thanks,
-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-developers


Re: [cmake-developers] [PATCH] Retrieve Xcode CompilerId via static libraries

2015-01-21 Thread Brad King
On 01/20/2015 02:44 PM, Gregor Jasny wrote:
 Do you plan to make this patch available in 3.1.1 release?

Yes.  It's already been backported to the 'release' branch:

 Xcode: Do not require code signing for compiler id (#15214)
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7b7209f6

and the commit message revised to reference a more appropriate
issue number.

-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-developers