[cmake-developers] [CMake 0012392]: CMakeFindEclipseCDT4.cmake ignores CMAKE_CXX_COMPILER_ARG1 in compiler invocation

2011-08-08 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=12392 
== 
Reported By:Axel Sander
Assigned To:
== 
Project:CMake
Issue ID:   12392
Category:   CCMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2011-08-08 03:55 EDT
Last Modified:  2011-08-08 03:55 EDT
== 
Summary:CMakeFindEclipseCDT4.cmake ignores
CMAKE_CXX_COMPILER_ARG1 in compiler invocation
Description: 
While trying to find system include dirs, in the script
CMakeFindEclipseCDT4.cmake the compile is called with:
 ... COMMAND ${_compilerExecutable} -v -E -P -x ${_lang} -dD dummy ...
When using something like ccache or distcc these commands are called directly
with the parameter above and complain about unknown options -v.
In the lines:
  SET(_compilerExecutable ${CMAKE_CXX_COMPILER});
and
  SET(_compilerExecutable ${CMAKE_C_COMPILER});
the compiler arguments like ${CMAKE_CXX_COMPILER_ARG1},
${CMAKE_C_COMPILER_ARG1}... are not used.

Steps to Reproduce: 
with:
  CC=ccache gcc CXX=ccache g++ cmake -G Eclipse CDT4 - Unix Makefiles .
the .cproject does not contain system includes.

To view the problem use:
  MESSAGE(STATUS gccOutput: ${_gccOutput})
  MESSAGE(STATUS gccStdout: ${_gccStdout})
after invocation of
  EXECUTE_PROCESS(COMMAND ${_compilerExecutable}...)
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2011-08-08 03:55 Axel SanderNew Issue
==

___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] Setting environment variables for builds

2011-08-08 Thread Johan Björk
Hey guys,

This has been discussed a billion times, so I'll keep it short.

Problem: Some parts of the build requires a environment variable to be set
Solution: Several workarounds, use custom commands, wrapper scripts etc.

While the solution works fine for basic stuff, I have several toolchains etc
that requires environment variables to be installed for them to work.

Since I'm using cmake --build for all my building, I am thinking about
creating a new command in cmake that will store certain environment
variables in the cache, and if building using cmake --build, they will be
set before the build starts.

Any comments before I go and build this?

Cheers
-Johan
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Setting environment variables for builds

2011-08-08 Thread Brad King

On 8/8/2011 4:24 AM, Johan Björk wrote:

This has been discussed a billion times, so I'll keep it short.

Problem: Some parts of the build requires a environment variable to be set
Solution: Several workarounds, use custom commands, wrapper scripts etc.

While the solution works fine for basic stuff, I have several toolchains

 etc that requires environment variables to be installed for them to work.

CMake has always assumed that the environment is setup correctly for the
desired toolchain before either cmake or make runs.  Typically developers
have dealt with this by naming the build tree after the toolchain needed
as a reminder of the environment needed.  I'm sure an alternative would
be welcomed by many.


Since I'm using cmake --build for all my building, I am thinking about

 creating a new command in cmake that will store certain environment
 variables in the cache, and if building using cmake --build, they will
 be set before the build starts.

This sounds like a great compromise.  I don't think the cache is the
right place to put this though.  I think you can create your own file
like CMakeFiles/cmake--build.env and give it a format customized for
this purpose (like one line per variable or something).

Please post a proposed interface here first for adding/setting/removing
variables from the environment configuration.

Thanks,
-Brad
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


Re: [cmake-developers] Adding MacroWriteBasicCMakeVersionFile.cmake file to cmake ?

2011-08-08 Thread Brad King

On 8/5/2011 5:14 PM, Alexander Neundorf wrote:

(2) The documentation of the module has a few typos.  Please
proofread it again.  Also, please use the word compatible rather
than suitable to refer version acceptability.  This makes the
distinction noted above in (1).


I hope it's better now. But I didn't merge it yet to next.


The use of unsuitable in the implementation looks good, but see below.


(3) After noting the implementation detail with configure_file the
documentation should state that users should never directly configure
the files themselves.


Done.


I don't see any commits on the WriteConfigVersionFile_2TemplateFiles
topic that make changes to the main module file.  Where did you put
the new documentation changes?

Thanks,
-Brad
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0012394]: Check compiler flags for Clang

2011-08-08 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=12394 
== 
Reported By:Giuseppe Bilotta
Assigned To:
== 
Project:CMake
Issue ID:   12394
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2011-08-08 11:56 EDT
Last Modified:  2011-08-08 11:56 EDT
== 
Summary:Check compiler flags for Clang
Description: 
The CHECK_C_COMPILER_FLAG and CHECK_CXX_COMPILER_FLAG macros do not properly
detect the warning message with which clang complains about unknown flags

Steps to Reproduce: 
A test such as
CHECK_CXX_COMPILER_FLAG(-Wagoiuhaoigfh FLAG_IS_KNOWN)
will report Success instead of Fail
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2011-08-08 11:56 Giuseppe BilottaNew Issue
==

___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers


[CMake] CMAKE_MODULE_PATH

2011-08-08 Thread Andreas Kelle-Emden
Hi all,

the variable CMAKE_PREFIX_PATH is automatically set if the corresponding
environment variable is set. This does not apply to CMAKE_MODULE_PATH.
Is this behaviour intended?

Best regards,
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] Assembler handling in 2.8.5 vs 2.8.4

2011-08-08 Thread Florian Reinhard
2011/8/1 Alexander Neundorf a.neundorf-w...@gmx.net:
 I attached the gdb output i got. I've been running gdb from a minGW32
 installation on a normal windows cmd.exe on windows7 x64.
 Unfortunately there's no backtrace (or i'm just don't know gdb well
 enough) and as soon as i execute strace after the cmake crash, gdb
 crashes as well.

 Can you try to catch throw in gdb, then gdb should break when the exception
 is thrown, and you should be able to get a backtrace then, so we can see where
 it is thrown.
Catch throw isn't able to produce a backtrace either. See attachment

 I'm compiling a complete firmware for a Texas
 Instruments DSP (674x family) and no single binaries.

 Just to make sure I understand correctly: the firmware consists of one big
 binary which contains everything and there are no shared libraries or anything
 like this, right ?

Right, everything get's linked together into one single big binary, no
shared libraries.
I doubt anyone runs a real OS on these chips. There is the TI OMAP
platform which have a ARM Core which run Linux, but i can't tell which
compiler they use for the ARM Core.


Besides the issues above: the commandline options you provided do work
with the 7.2.x series but aren't compatible with the 6.1.x series
which is still maintained by TI but doesn't feature verbose (=long)
commandline options. Using short commandline options 7.2.x and 6.1.x
are compatible on CLI.
What's the way to go here? Duplicate the code in the .cmake modules,
keep the more readable 7.2.x version and add the same ones for 6.1.x
again?

Kind Regards,
Florian
C:\work\test\build_cmakegdb c:\tools\cmake\bin\cmake.exe
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as mingw32.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from c:\tools\cmake\bin\cmake.exe...done.
(gdb) catch throw
Function __cxa_throw not defined.
Catchpoint 1 (throw)
(gdb) run -GMinGW Makefiles -DCMAKE_BUILD_TYPE=release
Starting program: c:\tools\cmake\bin\cmake.exe -GMinGW Makefiles 
-DCMAKE_BUILD_TYPE=release
[New Thread 4940.0x1734]
CMake Error: The source directory C:\work\test/build_cmake does not appear to 
contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

Program exited with code 01.
(gdb) run -GMinGW Makefiles -DCMAKE_BUILD_TYPE=release ..
Starting program: c:\tools\cmake\bin\cmake.exe -GMinGW Makefiles 
-DCMAKE_BUILD_TYPE=release ..
[New Thread 4348.0x3bd8]
[New Thread 4348.0x210c]
[New Thread 4348.0x2184]
[New Thread 4348.0x5118]
[New Thread 4348.0x1154]
-- Checked for GNU
--Output: - WARNING: invalid compiler option --version (ignored)
 ERROR: no source files, nothing to do
-
--Result: -0-
[New Thread 4348.0x1898]
[New Thread 4348.0x1528]
[New Thread 4348.0xb4c]
[New Thread 4348.0x18d8]
-- Checked for HP
--Output: - WARNING: invalid compiler option -V (ignored)
 ERROR: no source files, nothing to do
-
--Result: -0-
[New Thread 4348.0x2478]
[New Thread 4348.0x2c88]
[New Thread 4348.0x4ed0]
[New Thread 4348.0x4b54]
-- Checked for Intel
--Output: - WARNING: invalid compiler option --version (ignored)
 ERROR: no source files, nothing to do
-
--Result: -0-
[New Thread 4348.0x5ebc]
[New Thread 4348.0x1ffc]
[New Thread 4348.0x388c]
[New Thread 4348.0x2514]
-- Checked for SunPro
--Output: - WARNING: invalid compiler option -V (ignored)
 ERROR: no source files, nothing to do
-
--Result: -0-
[New Thread 4348.0x447c]
[New Thread 4348.0x2fec]
[New Thread 4348.0x1b60]
[New Thread 4348.0x3184]
-- Checked for XL
--Output: -TMS320C6x C/C++ Compilerv7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U

TMS320C6x C/C++ Parser  v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x EABI C/C++ Parser v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x C/C++ File Merge  v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x C/C++ Optimizer   v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x C/C++ Codegen v7.2.4
Build Number 1LFFQ-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x Consultant Generator  v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x Assembly Preprocessor v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x Assembler v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x Compressorv7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x Embed Utility v7.2.4
Build Number 1LFFP-KDADEMDK-RTARQ-TAV-ZAZG_X_S_U
TMS320C6x C Source Interlister  v7.2.4
Build Number 

Re: [CMake] Bug fix requests for the *next* release of CMake...

2011-08-08 Thread Johan Björk
http://public.kitware.com/Bug/view.php?id=12284 (cpack copies data in
symlinks)


On Mon, Aug 1, 2011 at 9:26 PM, Alexander Neundorf
a.neundorf-w...@gmx.netwrote:

 On Saturday 30 July 2011, Alan W. Irwin wrote:
  Please do a fundamental fix for
  http://public.kitware.com/Bug/view.php?id=9220.

 Since I implemented this, I feel responsible for it.
 But most probably I will not be able to do this for 2.8.6.
 At least I'll try to make it work again for ASM.

 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

___
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] server paths on windows

2011-08-08 Thread Yngve Inntjore Levinsen
Dear developers,

I believe I *potentially* have found a problem with cmake on windows. I had my 
project path starting with \\my.url\dfs\bla\bla\project, and when I 
tried to generate MinGW makefiles I got errors telling me that the compilers 
were broken. I moved my project to D:\bla\My Documents\project, and 
the generation went fine. I suspect that \\ was replaced by single \, hence 
using an invalid path. I could also be simply wrong, I am completely lost in 
a non-unix environment (it took me an hour to understand there actually is 
something called PATH on Windows as well..).

Please ask if any information is needed. I am using CMake 2.8.5 I believe 
(definitely 2.8). Things are a bit confusing for me since I am not used to 
Windows, and this is a remote desktop. I believe it is XP 32 bit.

Actually, now I'm lost again. I moved my project folder one level down from My 
Documents, and then I got the same errors. The full path was then
D:\Profiles\username\project\, with a build folder inside. I post this mail 
anyway in case it is useful for any debugging purposes. Add My Documents 
between username and project, and it works.

Best Regards,
Yngve
___
Powered by www.kitware.com

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

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

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


[Cmake-commits] CMake branch, next, updated. v2.8.5-1449-gb3b858b

2011-08-08 Thread Stephen Kelly
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  b3b858b07fe64cd1ec97d9dade2f9d8f28bc1144 (commit)
   via  def0a54e0ae20d783aecf2761a4add5f40687cd6 (commit)
   via  30880707c094ac5c0edd85d0857afb6fbae55326 (commit)
  from  12e8a0afc502db73b0d324bcfe2a1e97897e56b7 (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=b3b858b07fe64cd1ec97d9dade2f9d8f28bc1144
commit b3b858b07fe64cd1ec97d9dade2f9d8f28bc1144
Merge: 12e8a0a def0a54
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Mon Aug 8 11:17:06 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 8 11:17:06 2011 -0400

Merge topic 'generate_export_header' into next

def0a54 Handle the case where the user changes the DEFINE_SYMBOL property.
3088070 Add the GenerateExportMacro with unit tests.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=def0a54e0ae20d783aecf2761a4add5f40687cd6
commit def0a54e0ae20d783aecf2761a4add5f40687cd6
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Mon Aug 8 02:08:10 2011 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Mon Aug 8 02:08:10 2011 +0200

Handle the case where the user changes the DEFINE_SYMBOL property.

This eases porting of KDE code.

diff --git a/Modules/GenerateExportHeader.cmake 
b/Modules/GenerateExportHeader.cmake
index c717899..3665817 100644
--- a/Modules/GenerateExportHeader.cmake
+++ b/Modules/GenerateExportHeader.cmake
@@ -188,6 +188,12 @@ macro(_DO_GENERATE_EXPORT_HEADER TARGET_LIBRARY)
 
   set(INCLUDE_GUARD_NAME ${PREFIX}${EXPORT_MACRO_NAME}_H)
 
+  get_target_property(EXPORT_IMPORT_CONDITION ${TARGET_LIBRARY} DEFINE_SYMBOL)
+
+  if (NOT EXPORT_IMPORT_CONDITION)
+set(EXPORT_IMPORT_CONDITION ${TARGET_LIBRARY}_EXPORTS)
+  endif()
+
   configure_file(${myDir}/exportheader.cmake.in ${EXPORT_FILE_NAME} @ONLY)
 endmacro()
 
diff --git a/Modules/exportheader.cmake.in b/Modules/exportheader.cmake.in
index 083e95c..62ed3ff 100644
--- a/Modules/exportheader.cmake.in
+++ b/Modules/exportheader.cmake.in
@@ -7,7 +7,7 @@
 #  define @NO_EXPORT_MACRO_NAME@
 #else
 #  ifndef @EXPORT_MACRO_NAME@
-#ifdef @TARGET_LIBRARY@_EXPORTS
+#ifdef @EXPORT_IMPORT_CONDITION@
 /* We are building this library */
 #  define @EXPORT_MACRO_NAME@ @DEFINE_EXPORT@
 #else
diff --git a/Tests/Module/GenerateExportHeader/CMakeLists.txt 
b/Tests/Module/GenerateExportHeader/CMakeLists.txt
index 2d6eabe..4570280 100644
--- a/Tests/Module/GenerateExportHeader/CMakeLists.txt
+++ b/Tests/Module/GenerateExportHeader/CMakeLists.txt
@@ -107,6 +107,8 @@ macro_add_test_library(libstatic)
 add_subdirectory(lib_shared_and_static)
 add_subdirectory(lib_shared_and_statictest)
 
+add_subdirectory(override_symbol)
+
 if (CMAKE_COMPILER_IS_GNUCXX)
   # We deliberately call deprecated methods, and test for that elsewhere.
   # No need to clutter the test output with warnings.
diff --git a/Tests/Module/GenerateExportHeader/override_symbol/CMakeLists.txt 
b/Tests/Module/GenerateExportHeader/override_symbol/CMakeLists.txt
new file mode 100644
index 000..aeeef20
--- /dev/null
+++ b/Tests/Module/GenerateExportHeader/override_symbol/CMakeLists.txt
@@ -0,0 +1,11 @@
+project(override_symbol)
+
+add_library(somelib SHARED someclass.cpp)
+
+set_target_properties(somelib PROPERTIES DEFINE_SYMBOL SOMELIB_MAKEDLL)
+
+generate_export_header(somelib)
+
+add_executable(consumer main.cpp)
+
+target_link_libraries(consumer somelib)
diff --git a/Tests/Module/GenerateExportHeader/override_symbol/main.cpp 
b/Tests/Module/GenerateExportHeader/override_symbol/main.cpp
new file mode 100644
index 000..445a652
--- /dev/null
+++ b/Tests/Module/GenerateExportHeader/override_symbol/main.cpp
@@ -0,0 +1,9 @@
+
+#include someclass.h
+
+int main(int, char**)
+{
+  SomeClass sc;
+  sc.someMethod();
+  return 0;
+}
\ No newline at end of file
diff --git a/Tests/Module/GenerateExportHeader/override_symbol/someclass.cpp 
b/Tests/Module/GenerateExportHeader/override_symbol/someclass.cpp
new file mode 100644
index 000..7326b78
--- /dev/null
+++ b/Tests/Module/GenerateExportHeader/override_symbol/someclass.cpp
@@ -0,0 +1,7 @@
+
+#include someclass.h
+
+void SomeClass::someMethod() const
+{
+
+}
\ No newline at end of file
diff --git a/Tests/Module/GenerateExportHeader/override_symbol/someclass.h 
b/Tests/Module/GenerateExportHeader/override_symbol/someclass.h
new file mode 100644
index 000..ae5e844
--- /dev/null
+++ b/Tests/Module/GenerateExportHeader/override_symbol/someclass.h
@@ -0,0 +1,8 @@
+
+#include somelib_export.h
+
+class SOMELIB_EXPORT SomeClass
+{
+public:
+  

[Cmake-commits] CMake branch, next, updated. v2.8.5-1451-gf1c4765

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

The branch, next has been updated
   via  f1c4765623e9d6d81dbe4bff366011185245e58e (commit)
   via  ed6be501de960a21fc756d08e9a0a2318f276307 (commit)
  from  b3b858b07fe64cd1ec97d9dade2f9d8f28bc1144 (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=f1c4765623e9d6d81dbe4bff366011185245e58e
commit f1c4765623e9d6d81dbe4bff366011185245e58e
Merge: b3b858b ed6be50
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 8 12:59:34 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 8 12:59:34 2011 -0400

Merge topic 'fix-clang-flag-check-issue-12394' into next

ed6be50 Fix CHECK_(C|CXX)_COMPILER_FLAG for Clang (#12394)


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ed6be501de960a21fc756d08e9a0a2318f276307
commit ed6be501de960a21fc756d08e9a0a2318f276307
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 8 12:53:17 2011 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 8 12:53:17 2011 -0400

Fix CHECK_(C|CXX)_COMPILER_FLAG for Clang (#12394)

This compiler warns and returns 0 for unrecognized flags.  We fix the
compiler flag check macros by looking for a warning in the output.

diff --git a/Modules/CheckCCompilerFlag.cmake b/Modules/CheckCCompilerFlag.cmake
index a390b38..ec0a773 100644
--- a/Modules/CheckCCompilerFlag.cmake
+++ b/Modules/CheckCCompilerFlag.cmake
@@ -30,6 +30,7 @@ MACRO (CHECK_C_COMPILER_FLAG _FLAG _RESULT)
  FAIL_REGEX warning: command line option .* is valid for .* but not for C
 # Apple gcc
  FAIL_REGEX unrecognized .*option # GNU
+ FAIL_REGEX unknown .*option  # Clang
  FAIL_REGEX ignoring unknown option   # MSVC
  FAIL_REGEX warning D9002 # MSVC, any lang
  FAIL_REGEX [Uu]nknown option # HP
diff --git a/Modules/CheckCXXCompilerFlag.cmake 
b/Modules/CheckCXXCompilerFlag.cmake
index 788bf35..f646e78 100644
--- a/Modules/CheckCXXCompilerFlag.cmake
+++ b/Modules/CheckCXXCompilerFlag.cmake
@@ -28,6 +28,7 @@ MACRO (CHECK_CXX_COMPILER_FLAG _FLAG _RESULT)
CHECK_CXX_SOURCE_COMPILES(int main() { return 0;} ${_RESULT}
  # Some compilers do not fail with a bad flag
  FAIL_REGEX unrecognized .*option # GNU
+ FAIL_REGEX unknown .*option  # Clang
  FAIL_REGEX ignoring unknown option   # MSVC
  FAIL_REGEX warning D9002 # MSVC, any lang
  FAIL_REGEX [Uu]nknown option # HP

---

Summary of changes:
 Modules/CheckCCompilerFlag.cmake   |1 +
 Modules/CheckCXXCompilerFlag.cmake |1 +
 2 files changed, 2 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, next, updated. v2.8.5-1453-g83c00cd

2011-08-08 Thread Stephen Kelly
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  83c00cdf9677682ab4761bfb6c00ef5497217e18 (commit)
   via  896371661504fa0a3b5c7a611dbfc7a4bc44a889 (commit)
  from  f1c4765623e9d6d81dbe4bff366011185245e58e (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=83c00cdf9677682ab4761bfb6c00ef5497217e18
commit 83c00cdf9677682ab4761bfb6c00ef5497217e18
Merge: f1c4765 8963716
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Mon Aug 8 18:22:30 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 8 18:22:30 2011 -0400

Merge topic 'generate_export_header' into next

8963716 Add a newline at the end of the file.


http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=896371661504fa0a3b5c7a611dbfc7a4bc44a889
commit 896371661504fa0a3b5c7a611dbfc7a4bc44a889
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Tue Aug 9 00:18:00 2011 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Tue Aug 9 00:18:00 2011 +0200

Add a newline at the end of the file.

Hopefully fix the test execution reported on CDash.

diff --git a/Tests/Module/GenerateExportHeader/libshared/libshared.cpp 
b/Tests/Module/GenerateExportHeader/libshared/libshared.cpp
index 9812f55..d4041b3 100644
--- a/Tests/Module/GenerateExportHeader/libshared/libshared.cpp
+++ b/Tests/Module/GenerateExportHeader/libshared/libshared.cpp
@@ -88,4 +88,4 @@ int libshared_not_exported() {
 
 int libshared_excluded() {
   return 0;
-}
\ No newline at end of file
+}

---

Summary of changes:
 .../GenerateExportHeader/libshared/libshared.cpp   |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.5-145-g4675f5d

2011-08-08 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  4675f5d20423cd3331570a75794468bb3af1edaf (commit)
  from  867c3dcd245790553635c7fd8e3faaed6fbc0fb8 (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=4675f5d20423cd3331570a75794468bb3af1edaf
commit 4675f5d20423cd3331570a75794468bb3af1edaf
Author: KWSys Robot kwro...@kitware.com
AuthorDate: Tue Aug 9 00:01:04 2011 -0400
Commit: KWSys Robot kwro...@kitware.com
CommitDate: Tue Aug 9 00:13:06 2011 -0400

KWSys Nightly Date Stamp

diff --git a/Source/kwsys/kwsysDateStamp.cmake 
b/Source/kwsys/kwsysDateStamp.cmake
index eb1ed8a..e7f3f3a 100644
--- a/Source/kwsys/kwsysDateStamp.cmake
+++ b/Source/kwsys/kwsysDateStamp.cmake
@@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR  2011)
 SET(KWSYS_DATE_STAMP_MONTH 08)
 
 # KWSys version date day component.  Format is DD.
-SET(KWSYS_DATE_STAMP_DAY   08)
+SET(KWSYS_DATE_STAMP_DAY   09)

---

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