Re: [cmake-developers] GenerateExportHeader macro in CMake?
Stephen, The test you recently added is failing on many platforms on the CMake dashboard today. Are you working on resolving these test failures? This output: *** Exception executing: Exit code 0xc135 means that one of the dlls could not be loaded properly by the built executable. Are you putting the dlls in the same directory with the executables by setting CMAKE_RUNTIME_OUTPUT_DIR ... ? Do you have a Windows machine with Visual Studio on it for local testing? Thanks, David On Tue, Aug 2, 2011 at 9:38 AM, Brad King brad.k...@kitware.com wrote: On 8/2/2011 3:40 AM, Stephen Kelly wrote: Brad King wrote: I've now also tested with MSVC and MinGW on Windows. I couldn't seem to get cmake to work on cygwin though. I'll see if I can test on Mac too before pushing to the cmake repo. One question I have is: Will the unit tests for this be run on all platforms before it gets to master? Yes. You will create a topic branch starting from 'master' but it will initially be merged into 'next' for testing. If there are failures you will be able to extend the topic with corresponding fixes. Only after the whole topic is mature will upstream developers merge it to 'master'. Thanks, -Brad __**_ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developershttp://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] GenerateExportHeader macro in CMake?
Make that CMAKE_RUNTIME_OUTPUT_DIRECTORY ... On Wed, Aug 10, 2011 at 1:58 PM, David Cole david.c...@kitware.com wrote: Stephen, The test you recently added is failing on many platforms on the CMake dashboard today. Are you working on resolving these test failures? This output: *** Exception executing: Exit code 0xc135 means that one of the dlls could not be loaded properly by the built executable. Are you putting the dlls in the same directory with the executables by setting CMAKE_RUNTIME_OUTPUT_DIR ... ? Do you have a Windows machine with Visual Studio on it for local testing? Thanks, David On Tue, Aug 2, 2011 at 9:38 AM, Brad King brad.k...@kitware.com wrote: On 8/2/2011 3:40 AM, Stephen Kelly wrote: Brad King wrote: I've now also tested with MSVC and MinGW on Windows. I couldn't seem to get cmake to work on cygwin though. I'll see if I can test on Mac too before pushing to the cmake repo. One question I have is: Will the unit tests for this be run on all platforms before it gets to master? Yes. You will create a topic branch starting from 'master' but it will initially be merged into 'next' for testing. If there are failures you will be able to extend the topic with corresponding fixes. Only after the whole topic is mature will upstream developers merge it to 'master'. Thanks, -Brad __**_ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developershttp://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012396]: CDash should indicate the git hash of builds
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12396 == Reported By:Stephen Kelly Assigned To: == Project:CMake Issue ID: 12396 Category: CTest Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-08-10 16:38 EDT Last Modified: 2011-08-10 16:38 EDT == Summary:CDash should indicate the git hash of builds Description: It should be possible to see in build reports such as http://www.cdash.org/CDash/testDetails.php?test=109040029build=1418444 which hash was built to get the result. Otherwise it is difficult to know if a recent commit fixed it, but the recent build was started after the commit. == Issue History Date ModifiedUsername FieldChange == 2011-08-10 16:38 Stephen Kelly New Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] GenerateExportHeader macro in CMake?
I worked with Stephen today on this and it needs to put all the dll's in
the same place as the main executable.
The following makes the test pass on my windows box:
diff --git a/Tests/Module/GenerateExportHeader/CMakeLists.txt
b/Tests/Module/GenerateExportH
index 6374087..0f5d792 100644
--- a/Tests/Module/GenerateExportHeader/CMakeLists.txt
+++ b/Tests/Module/GenerateExportHeader/CMakeLists.txt
@@ -40,6 +40,8 @@ macro(_do_build Include Library LibrarySource Source)
set(CMAKE_INCLUDE_CURRENT_DIR ON)\n
+set(CMAKE_RUNTIME_OUTPUT_DIRECTORY
\${GenerateExportHeader_BINARY_DIR}\)\n
+
include(GenerateExportHeader)\n
add_compiler_export_flags()\n
Can you or Brad push this to the branch?
-Bill
On 8/10/2011 1:58 PM, David Cole wrote:
Stephen,
The test you recently added is failing on many platforms on the CMake
dashboard today. Are you working on resolving these test failures?
This output:
*** Exception executing: Exit code 0xc135
means that one of the dlls could not be loaded properly by the built
executable. Are you putting the dlls in the same directory with the executables
by setting CMAKE_RUNTIME_OUTPUT_DIR ... ?
Do you have a Windows machine with Visual Studio on it for local testing?
Thanks,
David
On Tue, Aug 2, 2011 at 9:38 AM, Brad King brad.k...@kitware.com
mailto:brad.k...@kitware.com wrote:
On 8/2/2011 3:40 AM, Stephen Kelly wrote:
Brad King wrote:
I've now also tested with MSVC and MinGW on Windows. I couldn't
seem to get
cmake to work on cygwin though.
I'll see if I can test on Mac too before pushing to the cmake repo.
One question I have is: Will the unit tests for this be run on
all platforms
before it gets to master?
Yes. You will create a topic branch starting from 'master' but it will
initially be merged into 'next' for testing. If there are failures you
will be able to extend the topic with corresponding fixes. Only after
the whole topic is mature will upstream developers merge it to 'master'.
Thanks,
-Brad
_
cmake-developers mailing list
cmake-developers@cmake.org mailto:cmake-developers@cmake.org
http://public.kitware.com/cgi-__bin/mailman/listinfo/cmake-__developers
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
___
cmake-developers mailing list
cmake-developers@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012397]: It is not clear how to report CDash bugs
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12397 == Reported By:Stephen Kelly Assigned To: == Project:CMake Issue ID: 12397 Category: Development Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2011-08-10 17:28 EDT Last Modified: 2011-08-10 17:28 EDT == Summary:It is not clear how to report CDash bugs Description: On this page: http://public.kitware.com/Bug/bug_report_page.php the Category combobox does not contain an entry for CDash. It seems to be possible to change the project field to CDash, but I do not seem to have the karma to do that. == Issue History Date ModifiedUsername FieldChange == 2011-08-10 17:28 Stephen Kelly New Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
