Re: [cmake-developers] Better Eclipse CDT support
On Sun, May 8, 2011 at 7:38 PM, Oliver Buchtala oliver.bucht...@jku.at wrote: Hi Alex, Manuel, and other interested watchers, I'd like to introduce a preview version of an Eclipse plugin 'CMakeWorkbench' which is combined with the CMake CDT7 generator developed lately. I try to reduce user actions for importing projects and managing working sets. By watching solution files generated with CDT7 generator automatic updating is achieved... Of course there are still some hitches... and obviously much space for improvement... but hey ;) that's is my first eclipse plugin Please find notes about installation: https://github.com/oliver/cmake-workbench/blob/master/doc/Install.markdown and a step by step HelloWorld on: https://github.com/oliver/cmake-workbench/blob/master/doc/examples/HelloWorld.markdown Please: I'd like to have your opinion and maybe some trying :) First impression: very nice. Somehow even the .h stuff works now :) /me is happy... will use it more and see how it behaves when the CMakeLists.txt change :D Cheers, /Manuel Bye, Oliver PS: I have developed and tested under Ubuntu LTS 10.04 + Eclipse 3.7 M6 + CDT 8.0 M6. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Better Eclipse CDT support
On Mon, May 9, 2011 at 2:30 PM, Manuel Klimek kli...@google.com wrote: On Sun, May 8, 2011 at 7:38 PM, Oliver Buchtala oliver.bucht...@jku.at wrote: Hi Alex, Manuel, and other interested watchers, I'd like to introduce a preview version of an Eclipse plugin 'CMakeWorkbench' which is combined with the CMake CDT7 generator developed lately. I try to reduce user actions for importing projects and managing working sets. By watching solution files generated with CDT7 generator automatic updating is achieved... Of course there are still some hitches... and obviously much space for improvement... but hey ;) that's is my first eclipse plugin Please find notes about installation: https://github.com/oliver/cmake-workbench/blob/master/doc/Install.markdown and a step by step HelloWorld on: https://github.com/oliver/cmake-workbench/blob/master/doc/examples/HelloWorld.markdown Please: I'd like to have your opinion and maybe some trying :) First impression: very nice. Somehow even the .h stuff works now :) No, it doesn't ... It now opens the projects in the background (which is nice) and had me thinking that there were no duplicated .cpp files in there any more for a moment. /me is happy... will use it more and see how it behaves when the CMakeLists.txt change :D Cheers, /Manuel Bye, Oliver PS: I have developed and tested under Ubuntu LTS 10.04 + Eclipse 3.7 M6 + CDT 8.0 M6. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Better Eclipse CDT support
Am 09.05.2011 23:32, schrieb Manuel Klimek: On Mon, May 9, 2011 at 2:30 PM, Manuel Klimek kli...@google.com wrote: On Sun, May 8, 2011 at 7:38 PM, Oliver Buchtala oliver.bucht...@jku.at wrote: Hi Alex, Manuel, and other interested watchers, I'd like to introduce a preview version of an Eclipse plugin 'CMakeWorkbench' which is combined with the CMake CDT7 generator developed lately. I try to reduce user actions for importing projects and managing working sets. By watching solution files generated with CDT7 generator automatic updating is achieved... Of course there are still some hitches... and obviously much space for improvement... but hey ;) that's is my first eclipse plugin Please find notes about installation: https://github.com/oliver/cmake-workbench/blob/master/doc/Install.markdown and a step by step HelloWorld on: https://github.com/oliver/cmake-workbench/blob/master/doc/examples/HelloWorld.markdown Please: I'd like to have your opinion and maybe some trying :) First impression: very nice. Somehow even the .h stuff works now :) No, it doesn't ... It now opens the projects in the background (which is nice) and had me thinking that there were no duplicated .cpp files in there any more for a moment. Yepp. This is still an issue. I filed issues on CDT and reopened the corresponding issue on my github. I hope I find a clean solution soon. Basically, I don't like my approach to have a link to the full tree. Causes trouble and brings redundancy. Hopefully, they (CDT gang) try to work on the Ctrl-Shift-R for includes. I will try to add more linked resources (e.g., flex input sources etc.) Linked folders raise so many problems right now :( Don't hesitate to add ideas, feelings, suggestions by means of issues or comments on my github :) Cheers, Oliver ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012171]: Runpaths incorrect for all hpux/pa_risc systems
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12171 == Reported By:Peter O'Gorman (The Written Word, Inc.) Assigned To: == Project:CMake Issue ID: 12171 Category: CMake Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2011-05-09 23:07 EDT Last Modified: 2011-05-09 23:07 EDT == Summary:Runpaths incorrect for all hpux/pa_risc systems Description: Installing a build with shared libraries on this system causes builddir runpaths to be coded into the installed shared libraries and executables. e.g. /opt/TWWfsw/libproxy04/lib/libproxy.sl: shared library shared library dynamic path search: SHLIB_PATH disabled second embedded path enabled first /opt/TWWfsw/libproxy04/lib:/usr/lib internal name: libproxy.sl.1 shared library list: static /opt/build/libproxy-0.4.6/libproxy/../libmodman/libmodman.sl.1 dynamic /usr/lib/libnsl.1 dynamic /usr/lib/libcma.2 Because ld is invoked with a command like aCC -o /path/to/libproxy.sl.1 ../libmodman/libmodman.sl.1 The library is added and its type is set to static, this means that the RPATH and env vars have no effect, if the library does not exist at /opt/build/libproxy-0.4.6/libmodman/libmodman.sl.1 the executable will abort. Steps to Reproduce: Build libproxy on HP-UX/PA 32bit. (the 64 bit linker behaves differently). Additional Information: Attached is the hack that we used to let hpux builds use -L.. -lfoo, which makes the entry dynamic so that SHLIB_PATH and the RPATH can have a chance to work. This includes a hack to the install to add -L flags for every path in RPATH prior to other -L paths, this allows us to do 'make install' then rm all the relinked binaries in the build dir, do 'make install' again and have no references to the build dir appear in the installed libraries, because the second relink will use the installed libraries. Relinking happens in a 'preinstall' rule, and I don't know how to move it to an install rule. If it were in the install: rule then it would work well. Assuming that cmake installs things in dependency order (it appears to, but I don't know if that is guaranteed), we would, for libproxy for example, relink libmodman, install libmodman, relink libproxy using the installed libmodman, install libproxy, relink the 'proxy' utility using both installed libraries, install proxy, and all the embedded paths would be correct. Time permitting, I will continue to look at fixing this properly. == Issue History Date ModifiedUsername FieldChange == 2011-05-09 23:07 Peter O'Gorman (The Written Word, Inc.)New Issue 2011-05-09 23:07 Peter O'Gorman (The Written Word, Inc.)File Added: cmake.hack.patch == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0012172]: [PATCH] FindRuby does not find ruby-1.9.1 shipped with (k)ubuntu
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12172 == Reported By:Luiz Angelo Daros de Luca Assigned To: == Project:CMake Issue ID: 12172 Category: Modules Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2011-05-09 23:12 EDT Last Modified: 2011-05-09 23:12 EDT == Summary:[PATCH] FindRuby does not find ruby-1.9.1 shipped with (k)ubuntu Description: Hello, FindRuby only found the 1.8.6 version of my ruby installation, even if I force the RUBY_EXECUTABLE name. Steps to Reproduce: install ubuntu install both ruby1.8-dev and ruby1.9.1-dev Use in cmake: FIND_PACKAGE( Ruby REQUIRED ) SET( RUBY_EXECUTABLE ruby1.9.1 ) It did not find the ruby library. because it misses a - and it does not use full version. Also, RUBY_EXECUTABLE is not an common input. My config is kind of a hack but the fix is still valid. Additional Information: I did a patch to fix this issue when library is libruby-1.x.x. I also noticed that there is both RUBY_MAJOR_VERSION and RUBY_VERSION_MAJOR. Is it all right? Also, some parameters use Ruby_XXX form instead of RUBY_XXX. I guess the default in cmake should be the latter (but it will break previous uses). At Last, if I have multiple ruby installations, I cannot simply set: (Ruby_FIND_VERSION 1.9) This should be the easiest solution. However, I'm no expert in cmake lang. == Issue History Date ModifiedUsername FieldChange == 2011-05-09 23:12 Luiz Angelo Daros de LucaNew Issue 2011-05-09 23:12 Luiz Angelo Daros de LucaFile Added: find-ruby-library.patch == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] RPM packages and install(SCRIPT...)
Hi Eric,
You should use:
execute_process(
COMMAND ${CMAKE_COMMAND} -E create_symlink file link
WORKING_DIRECTORY $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/share/TestLink
)
Thanks, it works fine.
so the INSTALL(SCRIPT ...) should work for all of them as soon as symlinks
are supported (which may not be the case on Windows).
Indeed, I have read a lot of CMake posts about create_symlink under Windows,
but for the moment, our software is only installed under Linux, so it should
be sufficient but I would better put a warning in the script...
Thanks,
J. Bedouet
2011/5/5 Eric Noulard eric.noul...@gmail.com
2011/5/5 Judicaël Bedouet j.bedo...@infonie.fr:
Hi,
Hi Judicaël,
I use install(SCRIPT...) to make links during installation. It works with
a
normal installation (make install) but the script seems not to be
executed
by CPack or CPack RPM (I have not tested other generators). I could solve
the problem by making a specific RPM spec but the post-install code would
be
duplicated in two files.
Is it intended that CPack doesn't execute install(SCRIPT...) ?
In fact it does but you did not see what happened.
Your install script:
execute_process(
COMMAND ${CMAKE_COMMAND} -E create_symlink file link
WORKING_DIRECTORY ${CMAKE_INSTALL_PREFIX}/share/TestLink
)
does not support DESTDIR, which is used by CPack in order to install
locally
(inside build/_CPack_Packages ... )
before packaging.
You should use:
execute_process(
COMMAND ${CMAKE_COMMAND} -E create_symlink file link
WORKING_DIRECTORY $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/share/TestLink
)
and this should work in both cases (make install and CPack run).
Is there a better way to create links between files ?
From a pure RPM perspective you should write an RPM post install script
and
set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE your-script.sh)
now I understand you want to have a single script for all package format
so the INSTALL(SCRIPT ...) should work for all of them as soon as
symlinks are supported (which may not be the case on Windows).
--
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] ProjectConfig.cmake files with both dynamic and static libraries?
Hi Michael, On Thu, May 5, 2011 at 10:48 PM, Michael Hertling mhertl...@online.dewrote: IMO, your approach looks quite reasonable; however, I'm not completely happy with it... ;) Please note that the following remarks are just my personal point of view, and of course, one can have different notions. The information if there is a static library is already available at mlvl's configuration time, so there's no actual need for the config file to make a dynamic decision, i.e. if(TARGET mlvl-static) and if(mlvl_LIBRARY_STATIC); this is typically done by find modules. Instead, one might consider to hard-code the affected passages, e.g. as an additional include file next to the export file: Thanks for the suggestions - they look really useful (and an improvement over my current setup)! I used the odd mlvl_LIBRARY_STATIC variable to try and allow for cases where a project might need the static library for one target but the shared library for another. The only case I can think of for this is if I build another library 'foo' which can be built static and shared, and which links to mlvl. I might then want to target_link_libraries foo-static to mlvl-static, and foo to mlvl so that clients of foo can get pure static or dynamic builds. I don't know if that'll be needed, or if it's even a good idea. Besides, an approach like the above-noted would make it much easier for the user to explicitly prefer a static library to a shared one without messing around with CMAKE_FIND_LIBRARY_SUFFIXES or setting XYZ_LIBRARY explicitly, an issue which comes up on the ML every now and then. In addition, if you drop the mutual exclusion, you gain the possibility to link against the shared and the static library at the same time in case they differ in some regard. That's hardly possibly with the usual single-component approach although I don't have an example at hand ATM. However, when thinking about multi-component packages, be aware of some issues that do not matter for single-component packages, refer to [1,2] for discussions of this topic. Furthermore, note that an export file as mlvlLibraryDepends.cmake needs to be protected from being included more than once in the current scope, see [3]. Regards, Michael [1] http://www.mail-archive.com/cmake@cmake.org/msg28431.html [2] http://www.mail-archive.com/cmake@cmake.org/msg32836.html [3] http://www.mail-archive.com/cmake@cmake.org/msg35873.html Yes, the basic idea was to provide the option for static or dynamic linking in an easy way. The ProjectConfig.cmake approach is very nice for handling this, with the caveats you mention above. Many thanks for the example code for components and the links - they're going to be really helpful. Cheers, Ben. ___ 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] Additional manifest
Hi, I am using cmake 2.8.3 and the generator for vs2005. How can I specify Additional Manifest file through cmakelist.txt . This option is found in Project Properties - Manifest Tool -Input and Output-Additional Manifest Files . ___ 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] Adding notes to a CTestScript.cmake?
Try searching for notes on this page: http://www.cmake.org/cmake/help/ctest-2-8-docs.html On Mon, May 9, 2011 at 5:06 AM, NoRulez noru...@me.com wrote: Hi, can anyone tell me how I can add CDash notes which i can fill up in a CTestScript file? The Problem is that i want to add the library versions from the build slave to know on which system the tests are running ok and on which the tests fails. Thanks in advance Best Regards ___ 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] Conditional post test behavior
I think the canonical way to do this is by handling this logic in a
wrapper script.
add_test - wrapper script - run test
- check status and delete if OK
hth,
tyler
On Sat, May 7, 2011 at 3:13 PM, Belcourt, K. Noel kbe...@sandia.gov wrote:
Hi,
I apologize if this has been asked and answered. Is there a way to execute
some commands after a test has run where the commands can be different
depending on whether the test passes or not? Here's my test.
add_test(
NAME ex7_2_fmelcor
WORKING_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}
COMMAND fmelcor.x ex7_variant2.inp
)
Because these tests generate enormous files (in both quantity and size) and
run for very long times (days in some cases) I want all generated files to
be deleted after the test runs, but only if the test passes. If the test
fails, I need to leave the files around so I can use them to debug the test.
So can I conditionally call this file remove function only if the test
passes?
file(REMOVE ${Ex7_2_Files})
Is there CMake support for this that I'm not seeing or is this even
possible?
-- Noel
___
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] Trying to use CMake, Visual Studio 8 2005 and Intel Fortran 11.2...
with absolutely no joy. Whenever I try to build a solution for my project, the cmake test for the fortran compiler generates a solution file for VS 8 that can't be processed by VS 8. So far I've pissed away about 2/3 of a day between trying to rebuild CMake (I found a reference to something like this problem back in 2.6, but it seems to still be there in 2.8 and a manual patch to cmLocalVisualStudio7Generator.cxx), zlib, etc. so far unsuccessfully. Any hints at how to tackle this problem? There was an oblique reference to --debug-trycompile, but nothing detailed and the CMake documentation is a little short on real examples of how to use the interactive version to try to generate solutions. Best, Dick Munroe ___ 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] manifest version mismatch with VS 2008 and InstallRequiredSystemLibraries
On Tue, May 3, 2011 at 12:17 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
My blog entry might help:
http://www.kitware.com/blog/home/post/4
Thanks, Bill. That's a good summary of the issues. It would have been
really useful to me a few days ago :), but hopefully this saves
someone else some time. The tip about CMakeVerifyManifest is quite
handy.
To close the loop, here's what I ended up doing.
It's possible to tell Visual Studio to embed a newer version in
generated binaries (by insuring that _BIND_TO_CURRENT_VCLIBS_VERSION
is set to 1 sufficiently early in your project), but each time the
version number increases you have to rebuild everything, including
third-party libraries. We build and cache our 3rdpartylibs on a
network share and I didn't want to run on the Microsoft treadmill by
rebuilding everything each time Microsoft releases a Visual Studio
update. Instead, I decided to treat the CRT libs as yet another
3rdpartylib, pinned to version 9.0.21022.8, and just include them
manually.
I considered modifying InstallRequiredSystemLibraries so that it could
use CRT libraries from somewhere other than the default, but there are
many combinations of different versions of VS and components I don't
use (MFC, ATL, etc.). Also, it seems that no one else has this
problem, so making the solution general for the community would not be
useful. Instead I hacked together the function below.
Thanks,
tyler
# This is a dumb version of the CMake module InstallRequiredSystemLibraries.
# We would like to replace this hand-rolled function with include
# (InstallRequiredSystemLibraries) but the default CRT libraries don't work
# for us and the provided module doesn't allow us to customize where the CRT
# libraries are pulled from. See
# http://wiki/bin/view/Main/PackagingWithCMake#microsoft_crt for details.
function (tp_install_required_system_libraries)
if (NOT DEFINED TP_CRT_ROOT)
set (TP_CRT_ROOT ${TP_3RDPARTYLIBS_ROOT}/microsoft_crt/9.0.21022.8)
endif ()
set (TP_CRT_BASE ${TP_CRT_ROOT}/build/${TP_PLATFORM})
set (runtime_libs
${TP_CRT_BASE}/Microsoft.VC90.CRT.manifest
${TP_CRT_BASE}/msvcm90.dll
${TP_CRT_BASE}/msvcp90.dll
${TP_CRT_BASE}/msvcr90.dll
)
install (PROGRAMS ${runtime_libs}
DESTINATION bin
)
endfunction ()
___
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] manifest version mismatch with VS 2008 and InstallRequiredSystemLibraries
I am a bit late to the thread but I also had this problem so I made it a
policy NOT to install the VS update that broke the Manifest thing. Easy for
me as I am a single guy shop :-) but it did get rid of the problem, or more
correctly worked around the problem. Of course the downside is that I am not
getting any updates to VS. Just my 2 cents.
___
Mike Jackson www.bluequartz.net
On May 9, 2011, at 4:28 PM, Tyler wrote:
On Tue, May 3, 2011 at 12:17 PM, Bill Hoffman bill.hoff...@kitware.com
wrote:
My blog entry might help:
http://www.kitware.com/blog/home/post/4
Thanks, Bill. That's a good summary of the issues. It would have been
really useful to me a few days ago :), but hopefully this saves
someone else some time. The tip about CMakeVerifyManifest is quite
handy.
To close the loop, here's what I ended up doing.
It's possible to tell Visual Studio to embed a newer version in
generated binaries (by insuring that _BIND_TO_CURRENT_VCLIBS_VERSION
is set to 1 sufficiently early in your project), but each time the
version number increases you have to rebuild everything, including
third-party libraries. We build and cache our 3rdpartylibs on a
network share and I didn't want to run on the Microsoft treadmill by
rebuilding everything each time Microsoft releases a Visual Studio
update. Instead, I decided to treat the CRT libs as yet another
3rdpartylib, pinned to version 9.0.21022.8, and just include them
manually.
I considered modifying InstallRequiredSystemLibraries so that it could
use CRT libraries from somewhere other than the default, but there are
many combinations of different versions of VS and components I don't
use (MFC, ATL, etc.). Also, it seems that no one else has this
problem, so making the solution general for the community would not be
useful. Instead I hacked together the function below.
Thanks,
tyler
# This is a dumb version of the CMake module InstallRequiredSystemLibraries.
# We would like to replace this hand-rolled function with include
# (InstallRequiredSystemLibraries) but the default CRT libraries don't work
# for us and the provided module doesn't allow us to customize where the CRT
# libraries are pulled from. See
# http://wiki/bin/view/Main/PackagingWithCMake#microsoft_crt for details.
function (tp_install_required_system_libraries)
if (NOT DEFINED TP_CRT_ROOT)
set (TP_CRT_ROOT ${TP_3RDPARTYLIBS_ROOT}/microsoft_crt/9.0.21022.8)
endif ()
set (TP_CRT_BASE ${TP_CRT_ROOT}/build/${TP_PLATFORM})
set (runtime_libs
${TP_CRT_BASE}/Microsoft.VC90.CRT.manifest
${TP_CRT_BASE}/msvcm90.dll
${TP_CRT_BASE}/msvcp90.dll
${TP_CRT_BASE}/msvcr90.dll
)
install (PROGRAMS ${runtime_libs}
DESTINATION bin
)
endfunction ()
___
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-commits] CMake branch, master, updated. v2.8.4-416-gee9fc4b
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 ee9fc4b1d314d2c1804fec1286d9f317e9ed5a1b (commit)
via afa83eb4cfb19f4019e4199f17907d6c27f36cbf (commit)
from 6aa45ac2eedb4a4bd16892c7a416dc4b029da57f (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=ee9fc4b1d314d2c1804fec1286d9f317e9ed5a1b
commit ee9fc4b1d314d2c1804fec1286d9f317e9ed5a1b
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon May 9 08:36:59 2011 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon May 9 08:40:03 2011 -0400
KWSys: Fix leaked FILE in EncodeExecutable error case
This leak was detected by cppcheck static analysis.
Author: Hans Johnson hans-john...@uiowa.edu
Change-Id: I1b81cb245acb9a6033f24ecc8d1452ca4df8371a
diff --git a/Source/kwsys/EncodeExecutable.c b/Source/kwsys/EncodeExecutable.c
index ba474b8..bc30568 100644
--- a/Source/kwsys/EncodeExecutable.c
+++ b/Source/kwsys/EncodeExecutable.c
@@ -41,6 +41,7 @@ int main(int argc, char* argv[])
if(!ofp)
{
fprintf(stderr, Cannot open output file: \%s\\n, argv[2]);
+fclose(ifp);
return 2;
}
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afa83eb4cfb19f4019e4199f17907d6c27f36cbf
commit afa83eb4cfb19f4019e4199f17907d6c27f36cbf
Author: KWSys Robot kwro...@kitware.com
AuthorDate: Mon May 9 08:36:40 2011 -0400
Commit: KWSys Robot kwro...@kitware.com
CommitDate: Mon May 9 08:40:03 2011 -0400
KWSys Nightly Date Stamp
diff --git a/Source/kwsys/kwsysDateStamp.cmake
b/Source/kwsys/kwsysDateStamp.cmake
index c38fe66..9d3a823 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 05)
# 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/EncodeExecutable.c |1 +
Source/kwsys/kwsysDateStamp.cmake |2 +-
2 files changed, 2 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.4-1508-geafa3b5
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 eafa3b5e5e16fa6229090d487982aec6f9ef21e3 (commit) via ee9fc4b1d314d2c1804fec1286d9f317e9ed5a1b (commit) via afa83eb4cfb19f4019e4199f17907d6c27f36cbf (commit) via 6aa45ac2eedb4a4bd16892c7a416dc4b029da57f (commit) via d3e09bba6a6203635ce04b2b7f52506336eedd5d (commit) from 07dd1ba82769c1437b970624a80afca1f6516929 (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=eafa3b5e5e16fa6229090d487982aec6f9ef21e3 commit eafa3b5e5e16fa6229090d487982aec6f9ef21e3 Merge: 07dd1ba ee9fc4b Author: Brad King brad.k...@kitware.com AuthorDate: Mon May 9 09:21:12 2011 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Mon May 9 09:21:12 2011 -0400 Merge branch 'master' into next --- Summary of changes: Source/kwsys/EncodeExecutable.c |1 + Source/kwsys/kwsysDateStamp.cmake |2 +- 2 files changed, 2 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.4-417-gc32262b
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 c32262bc040837d7abe80a1f003887485ad43261 (commit) from ee9fc4b1d314d2c1804fec1286d9f317e9ed5a1b (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=c32262bc040837d7abe80a1f003887485ad43261 commit c32262bc040837d7abe80a1f003887485ad43261 Author: KWSys Robot kwro...@kitware.com AuthorDate: Tue May 10 00:01:09 2011 -0400 Commit: KWSys Robot kwro...@kitware.com CommitDate: Tue May 10 00:10:21 2011 -0400 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 9d3a823..0dd966e 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 05) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 09) +SET(KWSYS_DATE_STAMP_DAY 10) --- 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
