Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On 04/04/2011 12:01 PM, Manuel Klimek wrote: Done. Thanks! I also have the previous patches ready (re-based with master). Let me know how we'll go on about submitting all that. I still have them on a local topic branch. See below. Have you changed anything since then? If you prefer to send the new versions, please use git format-patch to construct the patch series. Then send the files by email. Thanks, -Brad commit c8ed16a373adf98cf21a619349de8c0bde6a0eed Author: Manuel Klimek kli...@google.com Date: Mon Jan 17 11:44:44 2011 -0500 Make compile line export optional Add option CMAKE_EXPORT_COMPILE_COMMANDS to control the behavior. Modules/CMakeGenericSystem.cmake |3 +++ Source/cmGlobalUnixMakefileGenerator3.cxx |2 +- Source/cmMakefileTargetGenerator.cxx |3 ++- 3 files changed, 6 insertions(+), 2 deletions(-) commit 357fdbb1d7c472991323d36c6a431a36f16918bd Author: Manuel Klimek kli...@google.com Date: Thu Jan 13 16:15:54 2011 -0500 Export all compile command lines to json database Source/cmGlobalUnixMakefileGenerator3.cxx | 41 + Source/cmGlobalUnixMakefileGenerator3.h |6 Source/cmMakefileTargetGenerator.cxx | 21 +- 3 files changed, 66 insertions(+), 2 deletions(-) commit a75e21cadeb48c257d870db925131994f7da4995 Author: Manuel Klimek kli...@google.com Date: Thu Jan 13 16:06:20 2011 -0500 Factor Makefile flag and define lookup into methods Cache results over repeated calls. Source/cmMakefileTargetGenerator.cxx | 107 +++-- Source/cmMakefileTargetGenerator.h |5 ++ 2 files changed, 67 insertions(+), 45 deletions(-) ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Small patch to support build-setting conditions in XCode
On 04/05/2011 09:17 AM, Johan Björk wrote: Tiny patch attached to support build-setting conditions in XCode (XCODE_ATTRIBUTE_...[sdk=iphone]) for example. The issue was simply that XCode requires the key to be quoted when it contains []. I think the right place for this is in cmXCodeObject::PrintString where it already checks for characters that need quoting. Does that work? -Brad ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On Tue, Apr 5, 2011 at 6:19 AM, Brad King brad.k...@kitware.com wrote: On 04/05/2011 08:33 AM, Brad King wrote: On 04/04/2011 12:01 PM, Manuel Klimek wrote: Done. Thanks! While running the test on more platforms I ran into a problem. On Windows makefile tools like Borland and NMake we use custom inline response file syntax to handle long command lines: http://cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/Platform/Windows.cmake;hb=v2.8.4#l16 This syntax ends up in compile_commands.json and then makes no sense. This opens a can of worms. Unless we can refactor the generators to avoid using inline response file syntax then this whole feature will not work. Recently I added support for using cmake-generated response files for -I paths on some platforms: http://cmake.org/gitweb?p=cmake.git;a=commit;h=1c3233a8 It is a start, but I have no time to work further on ensuring command lines in the makefiles stay short enough for the ancient Windows make tools. For what platforms do you actually need this feature? The first version is completely fine as unix-only - clang on Windows is not exactly there yet, so I think doing the Windows stuff as a second step when we have proven the usefulness in unix land by integrating some tools will make sense. Cheers, /Manuel ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Generating information for C++ tools in cmake (patch)
On Tue, Apr 5, 2011 at 5:33 AM, Brad King brad.k...@kitware.com wrote: On 04/04/2011 12:01 PM, Manuel Klimek wrote: Done. Thanks! I also have the previous patches ready (re-based with master). Let me know how we'll go on about submitting all that. I still have them on a local topic branch. See below. Have you changed anything since then? Well, the git rebase led to conflicts which I resolved - otherwise I didn't change anything on the other patches. So I can re-export the changes to save you some work with merging, if you want :) Cheers, /Manuel If you prefer to send the new versions, please use git format-patch to construct the patch series. Then send the files by email. Thanks, -Brad commit c8ed16a373adf98cf21a619349de8c0bde6a0eed Author: Manuel Klimek kli...@google.com Date: Mon Jan 17 11:44:44 2011 -0500 Make compile line export optional Add option CMAKE_EXPORT_COMPILE_COMMANDS to control the behavior. Modules/CMakeGenericSystem.cmake | 3 +++ Source/cmGlobalUnixMakefileGenerator3.cxx | 2 +- Source/cmMakefileTargetGenerator.cxx | 3 ++- 3 files changed, 6 insertions(+), 2 deletions(-) commit 357fdbb1d7c472991323d36c6a431a36f16918bd Author: Manuel Klimek kli...@google.com Date: Thu Jan 13 16:15:54 2011 -0500 Export all compile command lines to json database Source/cmGlobalUnixMakefileGenerator3.cxx | 41 + Source/cmGlobalUnixMakefileGenerator3.h | 6 Source/cmMakefileTargetGenerator.cxx | 21 +- 3 files changed, 66 insertions(+), 2 deletions(-) commit a75e21cadeb48c257d870db925131994f7da4995 Author: Manuel Klimek kli...@google.com Date: Thu Jan 13 16:06:20 2011 -0500 Factor Makefile flag and define lookup into methods Cache results over repeated calls. Source/cmMakefileTargetGenerator.cxx | 107 +++-- Source/cmMakefileTargetGenerator.h | 5 ++ 2 files changed, 67 insertions(+), 45 deletions(-) -- Manuel Klimek (http://go/klimek) ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] problems with CMAKE_CFG_INTDIR in initial cache
On Tue, Apr 5, 2011 at 6:54 AM, Micha Renner micha.ren...@t-online.de wrote:
Am Montag, den 04.04.2011, 21:22 +0200 schrieb Dominik Szczerba:
CMAKE_CFG_INTDIR
This value is evaluated by the native build system - this variable is
suitable only for use in command lines that will be evaluated at build
time (after the cmake run).
Why does it work through the GUI then?
BTW. I do not want it to expand to the actual configuration, I want it
to expand to verbatim ${Configuration} string.
Dominik
Please see:
www.cmake.org/cmake/help/cmake-2-8-docs.html#variable:CMAKE_CFG_INTDIR
Micha
___
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] CMake and include only libraries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2011 03:53 AM, Michael Hertling wrote:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(HEADERLIBRARY C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
FILE(WRITE ${CMAKE_BINARY_DIR}/f.h void f(void)\n)
ADD_LIBRARY(f STATIC f.h)
SET_TARGET_PROPERTIES(f PROPERTIES
LINKER_LANGUAGE C PUBLIC_HEADER ${CMAKE_BINARY_DIR}/f.h)
ADD_CUSTOM_COMMAND(TARGET f POST_BUILD
COMMAND ${CMAKE_COMMAND} -E remove $TARGET_FILE:f)
INSTALL(TARGETS f EXPORT f
PUBLIC_HEADER DESTINATION include
ARCHIVE DESTINATION include OPTIONAL)
INSTALL(EXPORT f DESTINATION share)
Note the ARCHIVE DESTINATION *include* to prevent the INSTALL() command
from creating a directory for the non-existing library. The downside of
that approach is a little extra cost to build the empty library each
time make is run.
Nevertheless, the export file created by INSTALL(EXPORT ...) will still
contain a reference to the non-existing libf.a, so I wonder what's the
point of using the INSTALL() command's EXPORT feature with a header-
only library, i.e. what's so bad with INSTALL(FILES ...) or - after
setting up the library's headers - with INSTALL(DIRECTORY ...)?
I tried that, and indeed there remains a reference to the libf.a.
The idea is to have a single uniform mecanism to do export, all the more
that things get more complex when you want to use the built library
either at the build location or at the install location
Since the EXPORT seems to be done for that, I expected it to work with
INSTALL(FILES ...) or INSTALL(DIRECTORY ...) (exactly for headers) but
it does not
Honestly, headers seem sometimes a second class citizen in cmake: there
are some properties related to headers but few header knowledgeable
commands...
On 04/05/2011 03:53 AM, Michael Wild wrote:
I don't see what the problem with install(FILES ...) is? If you have a
header-only library, you just don't need any of the complex EXPORT
stuff. That is only related to the dependencies between libraries,
executables and transitive linking. In the case of a header-only library
you dump the files, create a XXXConfig.cmake and XXXConfigVersion.cmake
file, and be done with.
Well, I tend to disagree. Headers also have dependencies (to other
headers or even to other libraries), so the concepts of transitive
linking are useful as well for header-only libraries.
Again, headers are a full part of software development, so (at least to
me) it makes sense to treat them as well as libraries, executables,...
That they happen to be readble and (usually) machine independent, does
not mean that they do not convey dependencies, have version problems,
... I really think that having a target of type INCLUDES might bring
consistency to cmake, and ease of use to users.
If peope share this view, I might even try to add such a thing.
For now, I guess I have to rely on INSTALL(FILES|DIRECTORY ...)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk2a2q0ACgkQEr8WrU8nPV12FgCeIDw5V0stl8pNcRRIVONNrvwz
Y9AAoIjKekrhJZ3seSG2VthEqEQXaPWV
=ew7D
-END PGP SIGNATURE-
___
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] CMake and include only libraries
On 04/05/2011 11:02 AM, Theodore Papadopoulo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2011 03:53 AM, Michael Hertling wrote:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(HEADERLIBRARY C)
SET(CMAKE_VERBOSE_MAKEFILE ON)
FILE(WRITE ${CMAKE_BINARY_DIR}/f.h void f(void)\n)
ADD_LIBRARY(f STATIC f.h)
SET_TARGET_PROPERTIES(f PROPERTIES
LINKER_LANGUAGE C PUBLIC_HEADER ${CMAKE_BINARY_DIR}/f.h)
ADD_CUSTOM_COMMAND(TARGET f POST_BUILD
COMMAND ${CMAKE_COMMAND} -E remove $TARGET_FILE:f)
INSTALL(TARGETS f EXPORT f
PUBLIC_HEADER DESTINATION include
ARCHIVE DESTINATION include OPTIONAL)
INSTALL(EXPORT f DESTINATION share)
Note the ARCHIVE DESTINATION *include* to prevent the INSTALL() command
from creating a directory for the non-existing library. The downside of
that approach is a little extra cost to build the empty library each
time make is run.
Nevertheless, the export file created by INSTALL(EXPORT ...) will still
contain a reference to the non-existing libf.a, so I wonder what's the
point of using the INSTALL() command's EXPORT feature with a header-
only library, i.e. what's so bad with INSTALL(FILES ...) or - after
setting up the library's headers - with INSTALL(DIRECTORY ...)?
I tried that, and indeed there remains a reference to the libf.a.
The idea is to have a single uniform mecanism to do export, all the more
that things get more complex when you want to use the built library
either at the build location or at the install location
Since the EXPORT seems to be done for that, I expected it to work with
INSTALL(FILES ...) or INSTALL(DIRECTORY ...) (exactly for headers) but
it does not
Honestly, headers seem sometimes a second class citizen in cmake: there
are some properties related to headers but few header knowledgeable
commands...
On 04/05/2011 03:53 AM, Michael Wild wrote:
I don't see what the problem with install(FILES ...) is? If you have a
header-only library, you just don't need any of the complex EXPORT
stuff. That is only related to the dependencies between libraries,
executables and transitive linking. In the case of a header-only library
you dump the files, create a XXXConfig.cmake and XXXConfigVersion.cmake
file, and be done with.
Well, I tend to disagree. Headers also have dependencies (to other
headers or even to other libraries), so the concepts of transitive
linking are useful as well for header-only libraries.
Again, headers are a full part of software development, so (at least to
me) it makes sense to treat them as well as libraries, executables,...
That they happen to be readble and (usually) machine independent, does
not mean that they do not convey dependencies, have version problems,
... I really think that having a target of type INCLUDES might bring
consistency to cmake, and ease of use to users.
If peope share this view, I might even try to add such a thing.
For now, I guess I have to rely on INSTALL(FILES|DIRECTORY ...)
The whole EXPORT stuff is target at ABI compatibility, not API
compatibility. As I said, it is fairly easy to write a fully functional
XXXConfig.cmake.in file for a header-only library. Put something like
the following in it:
# Tell the user project where to find our headers
set(XXX_INCLUDE_DIR @XXX_INCLUDE_DIR@)
# Find required dependency
find_package(YYY REQUIRED)
# Set things up for the user-project
set(XXX_INCLUDE_DIRS ${XXX_INCLUDE_DIR} ${YYY_INCLUDE_DIRS})
set(XXX_LIBRARIES ${YYY_LIBRARIES})
#
I really don't see how CMake could automate this any more, or what
additional information it could generate for you. If your headers have
dependencies, just put the appropriate find_{package,path,library} calls
in there. Besides, you'll have to create a XXXConfig.cmake file anyways
where you would need to include the exported targets, so this is just as
simple.
I'm still a bit wondering what you actually want CMake to do for you.
Michael
___
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] missing file causes an empty solution
I found one possible VS2008 bug, just following these steps: 1 - Create a VS2008 solution based on a correct CMakeLists.txt 2 - Open the solution and edit CMakeLists.txt adding a non-existent file into the list of sources. 3 - Build the solution (F7 is my shortcut) 4 - It appears the message: The solution 'name' has been modified outside the environment. Press Reload to load the update solution from disk. Press Ignore to ignore the external changes. The changes will be used the next time you open the solution. 5 - If you press Reload, VS2008 will open a solution containing none projects, so it's not possible to recovery the situation. The only way is to fix the CMakeLists.txt by an external editor and generate the solution again by using cmake-gui or cmake command line. Is it an already known bug? Should I open a bug in the bug-lists? Cheers ___ 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] problems with CMAKE_CFG_INTDIR in initial cache
On Tuesday, April 5, 2011, Dominik Szczerba domi...@itis.ethz.ch wrote:
On Tue, Apr 5, 2011 at 6:54 AM, Micha Renner micha.ren...@t-online.de wrote:
Am Montag, den 04.04.2011, 21:22 +0200 schrieb Dominik Szczerba:
CMAKE_CFG_INTDIR
This value is evaluated by the native build system - this variable is
suitable only for use in command lines that will be evaluated at build
time (after the cmake run).
Why does it work through the GUI then?
BTW. I do not want it to expand to the actual configuration, I want it
to expand to verbatim ${Configuration} string.
Dominik
Please see:
www.cmake.org/cmake/help/cmake-2-8-docs.html#variable:CMAKE_CFG_INTDIR
Micha
___
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
Doesn't this work like you want it to if you simply escape the $ with \$ ?
___
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] Overriding Win-Registry search in UseJNI.cmake
Hello, I am working with CMake 2.8 and using UseJNI.cmake I have a JDK installed locally (registered in Win-Registry) but want to configure a project to use a different JDK lying on my disk. Looking at UseJNI.cmake I find that the environment variable JAVA_HOME could be handy, but unfortunately UseJNI prefers the Windows-Registry entries above all other search paths. Did I miss something? Shall I file an issue? Oliver ___ 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] Overriding Win-Registry search in UseJNI.cmake
Am 05.04.2011 13:12, schrieb Oliver Buchtala: Hello, I am working with CMake 2.8 and using UseJNI.cmake I have a JDK installed locally (registered in Win-Registry) but want to configure a project to use a different JDK lying on my disk. Looking at UseJNI.cmake I find that the environment variable JAVA_HOME could be handy, but unfortunately UseJNI prefers the Windows-Registry entries above all other search paths. Did I miss something? Shall I file an issue? Oliver Sorry, the macro file is called FindJNI.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] problems with CMAKE_CFG_INTDIR in initial cache
On Tue, Apr 5, 2011 at 1:00 PM, David Cole david.c...@kitware.com wrote:
Doesn't this work like you want it to if you simply escape the $ with \$ ?
Ah, yes, it does. I was simply prefixing also the brackets \$\{...\}
to get an error.
Many thanks!
Dominik
___
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] CMake 2.8.4 RPMs available (finally)
The openSUSE build service now offers CMake 2.8.4 for some newer distributions (SUSE ones) for those that don't want to build themselves: https://build.opensuse.org/package/show?package=cmakeproject=devel%3Atools%3Abuilding If anyone needs a package from the other distributions listed there that are currently disabled please drop me a note, I'll relay it to the maintainer of that repository then (or if you have a Novell Bugzilla account add a comment on bug 684733: https://bugzilla.novell.com/show_bug.cgi?id=684733#c3). When 2.8.5 is released I'll try to get an update request for that repository earlier. Greetings, Eike ___ 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] CMake and include only libraries
Honestly, headers seem sometimes a second class citizen in cmake: there
are some properties related to headers but few header knowledgeable
commands...
I really don't see how CMake could automate this any more, or what
additional information it could generate for you.
Well, since you asked: it *would* be nice if cmake would know about the
headers needed by a target, or even support header-only targets. Currently
it feels like an artificial divide between shared object files and header
files:
# find required dependency which correctly sets up import targets:
find_package(BAR)
# additional step for headers (with side-effects for other targets)...
include_directories(${BAR_INCLUDE_DIRS})
# ... that is not needed (and in fact discouraged) for libs:
#NO: link_directories(${BAR_LIBRARY_DIRS})
target_link_libraries(foo bar)
To be fair though, most other build-systems are not any better at
handling header files. And since this feature request has already been
discussed in http://public.kitware.com/Bug/view.php?id=115, I'm content
with it only being deferred, not dismissed...
--
Johannes Zarl
Virtual Reality Services
Johannes Kepler University
Informationsmanagement
Altenbergerstrasze 69
4040 Linz, Austria
Phone: +43 732 2468-8321
johannes.z...@jku.at
http://vrc.zid.jku.at
___
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] CMake 2.8.4 RPMs available (finally)
Fedora isn't listed there but is it possible to have it? Rolf Eike Beer ha scritto: The openSUSE build service now offers CMake 2.8.4 for some newer distributions (SUSE ones) for those that don't want to build themselves: https://build.opensuse.org/package/show?package=cmakeproject=devel%3Atools%3Abuilding If anyone needs a package from the other distributions listed there that are currently disabled please drop me a note, I'll relay it to the maintainer of that repository then (or if you have a Novell Bugzilla account add a comment on bug 684733: https://bugzilla.novell.com/show_bug.cgi?id=684733#c3). When 2.8.5 is released I'll try to get an update request for that repository earlier. Greetings, Eike ___ 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 __ Informazioni da ESET NOD32 Antivirus, versione del database delle firme digitali 6014 (20110404) __ Il messaggio è stato controllato da ESET NOD32 Antivirus. www.nod32.it -- *KORG ITALY SPA* *Via Cagiata, 85 – 60027 Osimo (AN) - ITALY* *Ph. +39 071 727161 - Fax +39 071 7231228* *P.IVA e Cod. fiscale IT01460580424* *Soggetta al controllo della Società KORG Inc. - Giappone* *Reg. Imprese di n. 212056/1996 del 23/12/96* *REA di Ancona al n. 133105 del 06/12/96* *Capitale sociale Euro 814.253,16 i.v.* Ai sensi del D.Lgs. 30 giugno 2003, n. 196, “Codice in materia di protezione dei dati personali” si precisa che le informazioni contenute nel messaggio sono riservate e destinate esclusivamente alla persona od organizzazione sopra indicata. A chi legge il presente avviso - se non è l'effettivo destinatario, o un dipendente, o la persona responsabile della consegna del messaggio - si notifica che sono proibite copie, distribuzione o divulgazione di quanto in esso contenuto (C.P. 616). Se questo messaggio Vi è pervenuto per errore, Vi preghiamo di informarci immediatamente, di non leggerlo e di distruggerlo. Grazie. /According to Legislative Decree n. 196 of 30 June 2003 about “Personal Data Protection Code” we point out that the information contained in this message may be privileged and confidential and is intended only for the use of the individual entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately and destroy the original message. //Thank you./ ___ 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] CMake 2.8.4 RPMs available (finally)
Fedora isn't listed there but is it possible to have it? I doubt they will add it just for CMake, but I can ask. Maybe we end up creating a special CMake build project there? Eike ___ 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] CMake 2.8.4 RPMs available (finally)
Packages for Ubuntu are already available from my PPA. You probably don't want to use my PPA because it will also contain some other updates. Not all of them are stable. If there is enough interest, I may create a PPA dedicated to just CMake. cheers, Daniel ___ 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] Overriding Win-Registry search in UseJNI.cmake
On Tue, Apr 5, 2011 at 7:16 AM, Oliver Buchtala oliver.bucht...@jku.atwrote: Am 05.04.2011 13:12, schrieb Oliver Buchtala: Hello, I am working with CMake 2.8 and using UseJNI.cmake I have a JDK installed locally (registered in Win-Registry) but want to configure a project to use a different JDK lying on my disk. Looking at UseJNI.cmake I find that the environment variable JAVA_HOME could be handy, but unfortunately UseJNI prefers the Windows-Registry entries above all other search paths. Did I miss something? Shall I file an issue? Oliver Sorry, the macro file is called FindJNI.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 The only find_* calls I see in FindJNI.cmake are: FIND_LIBRARY(JAVA_AWT_LIBRARY jawt FIND_LIBRARY(JAVA_JVM_LIBRARY NAMES jvm JavaVM FIND_PATH(JAVA_INCLUDE_PATH jni.h FIND_PATH(JAVA_INCLUDE_PATH2 jni_md.h FIND_PATH(JAVA_AWT_INCLUDE_PATH jawt.h If you want to override the default locations to find a specific installation of java stuff, just set those variables in your cache to point to the right stuff before calling find_package(JNI). For example: set(JAVA_AWT_LIBRARY /full/path/to/libjawt.a CACHE FILEPATH jawt library) find_package(JNI) If a variable is already set before calling a find_* command, then the find is a no-op and it trusts that you've set it correctly. HTH, David ___ 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] Overriding Win-Registry search in UseJNI.cmake
Am 05.04.2011 16:33, schrieb David Cole: On Tue, Apr 5, 2011 at 7:16 AM, Oliver Buchtala oliver.bucht...@jku.at mailto:oliver.bucht...@jku.at wrote: Am 05.04.2011 13:12, schrieb Oliver Buchtala: Hello, I am working with CMake 2.8 and using UseJNI.cmake I have a JDK installed locally (registered in Win-Registry) but want to configure a project to use a different JDK lying on my disk. Looking at UseJNI.cmake I find that the environment variable JAVA_HOME could be handy, but unfortunately UseJNI prefers the Windows-Registry entries above all other search paths. Did I miss something? Shall I file an issue? Oliver Sorry, the macro file is called FindJNI.cmake. ___ Powered by www.kitware.com http://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 The only find_* calls I see in FindJNI.cmake are: FIND_LIBRARY(JAVA_AWT_LIBRARY jawt FIND_LIBRARY(JAVA_JVM_LIBRARY NAMES jvm JavaVM FIND_PATH(JAVA_INCLUDE_PATH jni.h FIND_PATH(JAVA_INCLUDE_PATH2 jni_md.h FIND_PATH(JAVA_AWT_INCLUDE_PATH jawt.h If you want to override the default locations to find a specific installation of java stuff, just set those variables in your cache to point to the right stuff before calling find_package(JNI). For example: set(JAVA_AWT_LIBRARY /full/path/to/libjawt.a CACHE FILEPATH jawt library) find_package(JNI) If a variable is already set before calling a find_* command, then the find is a no-op and it trusts that you've set it correctly. HTH, David Hi David, ok. I thought it could even be easier ;) If I disable the win-Registry lookup stuff and set JAVA_HOME appropriately then everything is found perfectly. And if disabling would be just changing the order of search paths this would be more control for me and still powerful (i.e., when not using JAVA_HOME). Nevertheless, I can also live with your suggestion... Thank you, Oliver ___ 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] Overriding Win-Registry search in UseJNI.cmake
Am 05.04.2011 17:11, schrieb Oliver Buchtala: Am 05.04.2011 16:33, schrieb David Cole: On Tue, Apr 5, 2011 at 7:16 AM, Oliver Buchtala oliver.bucht...@jku.at mailto:oliver.bucht...@jku.at wrote: Am 05.04.2011 13:12, schrieb Oliver Buchtala: Hello, I am working with CMake 2.8 and using UseJNI.cmake I have a JDK installed locally (registered in Win-Registry) but want to configure a project to use a different JDK lying on my disk. Looking at UseJNI.cmake I find that the environment variable JAVA_HOME could be handy, but unfortunately UseJNI prefers the Windows-Registry entries above all other search paths. Did I miss something? Shall I file an issue? Oliver Sorry, the macro file is called FindJNI.cmake. ___ Powered by www.kitware.com http://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 The only find_* calls I see in FindJNI.cmake are: FIND_LIBRARY(JAVA_AWT_LIBRARY jawt FIND_LIBRARY(JAVA_JVM_LIBRARY NAMES jvm JavaVM FIND_PATH(JAVA_INCLUDE_PATH jni.h FIND_PATH(JAVA_INCLUDE_PATH2 jni_md.h FIND_PATH(JAVA_AWT_INCLUDE_PATH jawt.h If you want to override the default locations to find a specific installation of java stuff, just set those variables in your cache to point to the right stuff before calling find_package(JNI). For example: set(JAVA_AWT_LIBRARY /full/path/to/libjawt.a CACHE FILEPATH jawt library) find_package(JNI) If a variable is already set before calling a find_* command, then the find is a no-op and it trusts that you've set it correctly. HTH, David Hi David, ok. I thought it could even be easier ;) If I disable the win-Registry lookup stuff and set JAVA_HOME appropriately then everything is found perfectly. And if disabling would be just changing the order of search paths this would be more control for me and still powerful (i.e., when not using JAVA_HOME). Nevertheless, I can also live with your suggestion... Thank you, Oliver Hi David, Thinking it over again, I am getting to like it less... Setting these variables is in fact the stuff that FindJNI does. For now I will live with a monkey patched version that allows disabling the registry search stuff. Is this an option for the core FindJNI.cmake too - i.e., introducing a means to disable win registry search? Bye, Oliver ___ 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] Dependencies scanning for non-c/c++ files
On 04/03/2011 02:25 AM, aaron_wri...@selinc.com wrote:
I have some m4 files in my build that include other m4 files, so there's a
dependency between m4 files that can change at any time. I can calculate
the dependency at configure time, but what can I do when the files change
and I need to recalculate the dependencies? This is obviously handled for
c/c++ files by CMake. Any ideas?
---
Aaron Wright
Build-time dependency scanning without resorting to CMake's built-in
dependency scanner is possible but ugly, in a sort. First of all, you
need a custom target which suitably sets up the dependencies, and you
need to make the CMakeLists.txt file depend on them so that a change
of the dependencies will trigger a reconfiguration-before-rebuild in
order to recognize these new dependencies. In the following examples,
this gets done by a CMake script that gathers all files in a denoted
directory and writes their names to a file containing a CMake SET()
command, and this file gets included in the CMakeLists.txt. In that
way, changing dependencies invalidate the CMakeLists.txt file, and
the filenames - assigned to a variable by the SET() command - are
used to populate the OBJECT_DEPENDS property of a target, so the
latter gets also rebuilt when those files are touched.
Now, the key consideration is that you need two independent Make runs
for the home-brewed build-time dependency scanning to work: The first
run triggers the above-mentioned custom target to update dependencies,
and the second run builds your project with up-to-date dependencies -
maybe after a reconfiguration. AFAICS, this cannot be done in one go
because of the possibly needed intermediate CMake run to reconfigure.
In order to perform these two independent Make runs, you might:
1) Do it manually, e.g. make dependencies; make. The downside is
that you'll miss changed dependencies if you forget to perform
the dependencies run.
2) For each affected target, introduce a helper target which triggers
the dependencies target and subsequently builds the actual target
via cmake --build. Look at the following:
# CMakeLists.txt:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(DEPENDENCIES C)
ADD_CUSTOM_TARGET(dependencies
${CMAKE_COMMAND}
-DTEMPLATE=${CMAKE_SOURCE_DIR}/filelist.cmake.in
-DVARIABLE=DEPENDENCIES
-DDIRECTORY=${CMAKE_SOURCE_DIR}/dependencies
-DOUTPUT=${CMAKE_BINARY_DIR}/dependencies.txt
-P ${CMAKE_SOURCE_DIR}/dependencies.cmake)
IF(NOT EXISTS ${CMAKE_BINARY_DIR}/dependencies.txt)
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND}
-DTEMPLATE=${CMAKE_SOURCE_DIR}/filelist.cmake.in
-DVARIABLE=DEPENDENCIES
-DDIRECTORY=${CMAKE_SOURCE_DIR}/dependencies
-DOUTPUT=${CMAKE_BINARY_DIR}/dependencies.txt
-P ${CMAKE_SOURCE_DIR}/dependencies.cmake)
ENDIF()
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c int main(void){return 0;}\n)
INCLUDE(${CMAKE_BINARY_DIR}/dependencies.txt)
SET_SOURCE_FILES_PROPERTIES(${CMAKE_BINARY_DIR}/main.c
PROPERTIES OBJECT_DEPENDS ${DEPENDENCIES})
ADD_EXECUTABLE(main0 EXCLUDE_FROM_ALL main.c)
ADD_CUSTOM_TARGET(main ALL
COMMAND ${CMAKE_COMMAND}
--build ${CMAKE_BINARY_DIR}
--target dependencies
COMMAND ${CMAKE_COMMAND}
--build ${CMAKE_BINARY_DIR}
--target main0)
# dependencies.cmake:
FILE(GLOB FILES ${DIRECTORY}/*)
CONFIGURE_FILE(${TEMPLATE} ${OUTPUT} @ONLY)
# filelist.cmake.in:
SET(@VARIABLE@ @FILES@)
The dependencies target runs the dependencies.cmake script which
generates the dependencies.txt file with the filenames from the
dependencies directory; the dependencies.txt file must be created
once initially and it contains the above-mentioned SET() command,
i.e. SET(DEPENDENCIES dependencies-directory-files). The actual
target is main0, but the target which is triggered when building
the project is main, and it's this main target that performs the
two independent Make runs using the CMake --build option. Note
that due to the use of CONFIGULE_FILE(), the dependencies target
can run each time without causing the project's reconfiguration,
provided the dependencies have not changed. However, if a file
in the dependencies directory is just touched, the main target
gets rebuilt due to the OBJECT_DEPENDS property.
3) Use a helper project which allows unmodified target names:
# CMakeLists.txt:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(DEPENDENCIES C)
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND}
-E make_directory ${CMAKE_BINARY_DIR}/helper)
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND}
-DTOPLEVEL=${CMAKE_BINARY_DIR}
${CMAKE_SOURCE_DIR}/helper
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/helper)
ADD_CUSTOM_TARGET(dependencies
${CMAKE_COMMAND}
-DTEMPLATE=${CMAKE_SOURCE_DIR}/filelist.cmake.in
-DVARIABLE=DEPENDENCIES
-DDIRECTORY=${CMAKE_SOURCE_DIR}/dependencies
-DOUTPUT=${CMAKE_BINARY_DIR}/dependencies.txt
-P ${CMAKE_SOURCE_DIR}/dependencies.cmake)
IF(NOT EXISTS
[CMake] multiple targets depending on generated file
I'm looking at bug #11884
http://public.kitware.com/Bug/view.php?id=11884
And I've noticed there is a problem with depending on generated headers across
directories but not within the same directory.
For example:
# section A
add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/out.h COMMAND )
add_executable(... ${CMAKE_BINARY_DIR}/out.h ...)
# section B
add_custom_command(OUTPUT out2.h COMMAND .. DEPENDS ${CMAKE_BINARY_DIR}/out.h)
add_executable(... out2.h ...)
If section A and B are in the same CMakeLists.txt, then there is no problem.
If they are in sibling directories, then building section B first will lead to
an error about out.h missing. A workaround involves the user of
add_dependencies() and/or a custom target.
Is this a bug in CMake? It seems there is enough information given that CMake
could notice the dependency. But maybe it can't quite do it because its a
separate directory? Maybe cmake can do the add_dependencies() automatically?
--
Clinton Stimpson
Elemental Technologies, Inc
Computational Simulation Software, LLC
www.csimsoft.com
___
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] Dependencies scanning for non-c/c++ files
Wow. Thanks Michael. That's a very thorough answer. I like your idea, but
it just doesn't feel right. It seems to me that the right way to do it
would be to patch CMake.
There's a base class for the dependency scanners and several derived
classes for C, java, fortan, etc. Would it not be easy to just derive
another class for each file type I need? These dependency scanner classes
seemed to just regex each line in the file looking for include or
import, or some other language specific keyword. That would work for me,
I could just scan for m4_include.
In the mean time however, I think I could slip in one of your solutions.
Thanks again.
---
Aaron Wright
From: Michael Hertling mhertl...@online.de
To: cmake@cmake.org
Date: 04/05/2011 08:36 AM
Subject:Re: [CMake] Dependencies scanning for non-c/c++ files
Sent by:cmake-boun...@cmake.org
On 04/03/2011 02:25 AM, aaron_wri...@selinc.com wrote:
I have some m4 files in my build that include other m4 files, so there's
a
dependency between m4 files that can change at any time. I can calculate
the dependency at configure time, but what can I do when the files
change
and I need to recalculate the dependencies? This is obviously handled
for
c/c++ files by CMake. Any ideas?
---
Aaron Wright
Build-time dependency scanning without resorting to CMake's built-in
dependency scanner is possible but ugly, in a sort. First of all, you
need a custom target which suitably sets up the dependencies, and you
need to make the CMakeLists.txt file depend on them so that a change
of the dependencies will trigger a reconfiguration-before-rebuild in
order to recognize these new dependencies. In the following examples,
this gets done by a CMake script that gathers all files in a denoted
directory and writes their names to a file containing a CMake SET()
command, and this file gets included in the CMakeLists.txt. In that
way, changing dependencies invalidate the CMakeLists.txt file, and
the filenames - assigned to a variable by the SET() command - are
used to populate the OBJECT_DEPENDS property of a target, so the
latter gets also rebuilt when those files are touched.
Now, the key consideration is that you need two independent Make runs
for the home-brewed build-time dependency scanning to work: The first
run triggers the above-mentioned custom target to update dependencies,
and the second run builds your project with up-to-date dependencies -
maybe after a reconfiguration. AFAICS, this cannot be done in one go
because of the possibly needed intermediate CMake run to reconfigure.
In order to perform these two independent Make runs, you might:
1) Do it manually, e.g. make dependencies; make. The downside is
that you'll miss changed dependencies if you forget to perform
the dependencies run.
2) For each affected target, introduce a helper target which triggers
the dependencies target and subsequently builds the actual target
via cmake --build. Look at the following:
# CMakeLists.txt:
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(DEPENDENCIES C)
ADD_CUSTOM_TARGET(dependencies
${CMAKE_COMMAND}
-DTEMPLATE=${CMAKE_SOURCE_DIR}/filelist.cmake.in
-DVARIABLE=DEPENDENCIES
-DDIRECTORY=${CMAKE_SOURCE_DIR}/dependencies
-DOUTPUT=${CMAKE_BINARY_DIR}/dependencies.txt
-P ${CMAKE_SOURCE_DIR}/dependencies.cmake)
IF(NOT EXISTS ${CMAKE_BINARY_DIR}/dependencies.txt)
EXECUTE_PROCESS(
COMMAND ${CMAKE_COMMAND}
-DTEMPLATE=${CMAKE_SOURCE_DIR}/filelist.cmake.in
-DVARIABLE=DEPENDENCIES
-DDIRECTORY=${CMAKE_SOURCE_DIR}/dependencies
-DOUTPUT=${CMAKE_BINARY_DIR}/dependencies.txt
-P ${CMAKE_SOURCE_DIR}/dependencies.cmake)
ENDIF()
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c int main(void){return 0;}\n)
INCLUDE(${CMAKE_BINARY_DIR}/dependencies.txt)
SET_SOURCE_FILES_PROPERTIES(${CMAKE_BINARY_DIR}/main.c
PROPERTIES OBJECT_DEPENDS ${DEPENDENCIES})
ADD_EXECUTABLE(main0 EXCLUDE_FROM_ALL main.c)
ADD_CUSTOM_TARGET(main ALL
COMMAND ${CMAKE_COMMAND}
--build ${CMAKE_BINARY_DIR}
--target dependencies
COMMAND ${CMAKE_COMMAND}
--build ${CMAKE_BINARY_DIR}
--target main0)
# dependencies.cmake:
FILE(GLOB FILES ${DIRECTORY}/*)
CONFIGURE_FILE(${TEMPLATE} ${OUTPUT} @ONLY)
# filelist.cmake.in:
SET(@VARIABLE@ @FILES@)
The dependencies target runs the dependencies.cmake script which
generates the dependencies.txt file with the filenames from the
dependencies directory; the dependencies.txt file must be created
once initially and it contains the above-mentioned SET() command,
i.e. SET(DEPENDENCIES dependencies-directory-files). The actual
target is main0, but the target which is triggered when building
the project is main, and it's this main target that performs the
two independent Make runs using the CMake --build option. Note
that due to the use of CONFIGULE_FILE(), the dependencies target
can run each time without causing the project's reconfiguration,
provided
[CMake] Outputting VS projects under Linux
Is it possible to create visual studio/msbuild projects under Linux? (It would ease the flow of our automation chain, and it'd be handy for working with MonoDevelop). - Oliver ___ 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] multiple targets depending on generated file
On 04/05/2011 12:22 PM, Clinton Stimpson wrote:
I'm looking at bug #11884
http://public.kitware.com/Bug/view.php?id=11884
And I've noticed there is a problem with depending on generated headers
across
directories but not within the same directory.
For example:
# section A
add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/out.h COMMAND )
add_executable(... ${CMAKE_BINARY_DIR}/out.h ...)
# section B
add_custom_command(OUTPUT out2.h COMMAND .. DEPENDS ${CMAKE_BINARY_DIR}/out.h)
add_executable(... out2.h ...)
If section A and B are in the same CMakeLists.txt, then there is no problem.
If they are in sibling directories, then building section B first will lead
to
an error about out.h missing. A workaround involves the user of
add_dependencies() and/or a custom target.
Is this a bug in CMake? It seems there is enough information given that
CMake
could notice the dependency. But maybe it can't quite do it because its a
separate directory? Maybe cmake can do the add_dependencies() automatically?
This is expected. You need to do add_dependencies or use a separate custom
target and then make both targets depend on that. CMake cannot just magically
introduce an extra custom target or arbitrary dependency between existing
targets.
-Brad
___
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.4-1340-g1501b2d
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 1501b2dd73a05061fcb576842c6b795c4c11e83d (commit) via 0460916752f4303a7cf12ec2c7ee87768918411d (commit) from 1160bdef4f7da8d20eb82aedcdde5b398ac3c42b (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=1501b2dd73a05061fcb576842c6b795c4c11e83d commit 1501b2dd73a05061fcb576842c6b795c4c11e83d Merge: 1160bde 0460916 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 08:28:21 2011 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Tue Apr 5 08:28:21 2011 -0400 Merge branch 'master' into next --- 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
[Cmake-commits] CMake branch, master, updated. v2.8.4-284-ga2907bf
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 a2907bfb8419397dee4a28aeac63556f648df31d (commit) via b4c3ff7ce89aea7e0e5d9329a78e45e70e2036ee (commit) from 0460916752f4303a7cf12ec2c7ee87768918411d (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=a2907bfb8419397dee4a28aeac63556f648df31d commit a2907bfb8419397dee4a28aeac63556f648df31d Merge: 0460916 b4c3ff7 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:09 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:09 2011 -0400 Merge topic 'fixbug_0010316' b4c3ff7 This commit fixes bug #0010316 --- Summary of changes: Modules/FindOpenSSL.cmake | 53 1 files changed, 43 insertions(+), 10 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-289-g485b50c
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 485b50c357d325c40cf185d3917af5dc8ec14391 (commit) via 112f1dd7e36b9ce398e7082b48a3770e18b04f94 (commit) via a091ba61ceec68069be8416d8c96571b16491f3a (commit) via a164649f9d4664e192b421d5b72f8bcfaacd7a16 (commit) via 0fb5142e40a5a1d13478477af29a6d1a79a8b40e (commit) from a2907bfb8419397dee4a28aeac63556f648df31d (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=485b50c357d325c40cf185d3917af5dc8ec14391 commit 485b50c357d325c40cf185d3917af5dc8ec14391 Merge: a2907bf 112f1dd Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:14 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:14 2011 -0400 Merge topic 'asn_openssl_fixes' 112f1dd FindOpenSSL: Use find_package_handle_standard_args for version check. a091ba6 FindOpenSSL: Fixed crypto und ssl variable names. a164649 FindOpenSSL: We should only use hints to find OpenSSL. 0fb5142 FindOpenSSL: Added support for pkg-config. --- Summary of changes: Modules/FindOpenSSL.cmake | 218 - 1 files changed, 156 insertions(+), 62 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-293-g3b16aa6
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 3b16aa622e12f9fff46140291bb423d2b03cf90a (commit) via 126c993d031f6f7be4970a67621da92f580d4e5a (commit) from e252320793bd06b19366ef785734bb2d09b8ccbe (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=3b16aa622e12f9fff46140291bb423d2b03cf90a commit 3b16aa622e12f9fff46140291bb423d2b03cf90a Merge: e252320 126c993 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:23 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:23 2011 -0400 Merge topic 'linux-lib64-handling' 126c993 Fix #11964 Handle lib64 library on Linux --- Summary of changes: Modules/GNUInstallDirs.cmake | 25 +++- Tests/CPackComponentsForAll/CMakeLists.txt | 11 +- .../SystemSpecificInformations.cmake | 164 3 files changed, 26 insertions(+), 174 deletions(-) delete mode 100644 Tests/CPackComponentsForAll/SystemSpecificInformations.cmake 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-295-gcc2585b
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 cc2585b1ebe39815250296d1e493931a4456d72b (commit) via 9c78ef13951de5a4b648823bb574e9436e6b7504 (commit) from 3b16aa622e12f9fff46140291bb423d2b03cf90a (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=cc2585b1ebe39815250296d1e493931a4456d72b commit cc2585b1ebe39815250296d1e493931a4456d72b Merge: 3b16aa6 9c78ef1 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:28 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:28 2011 -0400 Merge topic 'nonstandard-system-libarchive' 9c78ef1 COMP: Fix build against non-standard outside libarchive --- Summary of changes: CMakeLists.txt |1 + 1 files changed, 1 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, master, updated. v2.8.4-304-gfff3a74
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 fff3a742b256afdbc6515f451a7283c1b34f5af4 (commit)
via 3e32db79216f145c4f0560387b83c3a9b7da2964 (commit)
via 6b6f309c5f2fa5c327afb98ac57d0b9f4f79a980 (commit)
via 28cdd0a5be086004e5afedbbe5adb61be7adc9cc (commit)
via fbe435652d97a16911d418ad6dd0b455905256ca (commit)
via 350546db3aa956e34487bd38dd048fe9a0689e4a (commit)
from c3c19c7cb76a2522bb01421ce1f790b1f7638ebe (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=fff3a742b256afdbc6515f451a7283c1b34f5af4
commit fff3a742b256afdbc6515f451a7283c1b34f5af4
Merge: c3c19c7 3e32db7
Author: Brad King brad.k...@kitware.com
AuthorDate: Tue Apr 5 14:28:38 2011 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Apr 5 14:28:38 2011 -0400
Merge topic 'upload-built-files'
3e32db7 cmCTestUploadCommand::CheckArgumentKeyword should return false if
not FILES
6b6f309 Add the FILES keyword to ctest_upload command
28cdd0a Don't tar/gz ctest_upload() files
fbe4356 Change 'Files' tag to 'Upload' in Upload.xml
350546d Implement ctest_upload command
---
Summary of changes:
Source/CMakeLists.txt |2 +
Source/CTest/cmCTestScriptHandler.cxx |2 +
Source/CTest/cmCTestSubmitHandler.cxx |1 +
Source/CTest/cmCTestTestHandler.cxx| 44 +---
Source/CTest/cmCTestTestHandler.h |2 -
Source/CTest/cmCTestUploadCommand.cxx | 69 ++
...CTestUpdateCommand.h = cmCTestUploadCommand.h} | 44 +++
Source/CTest/cmCTestUploadHandler.cxx | 77
...stConfigureHandler.h = cmCTestUploadHandler.h} | 30 +---
Source/cmCTest.cxx | 56 ++-
Source/cmCTest.h | 10 ++-
Tests/CMakeLists.txt | 10 +++
Tests/CTestTestUpload/CMakeLists.txt |4 +
Tests/CTestTestUpload/CTestConfig.cmake|7 ++
.../{CTestTestStopTime = CTestTestUpload}/sleep.c |0
.../test.cmake.in | 12 ++--
16 files changed, 287 insertions(+), 83 deletions(-)
create mode 100644 Source/CTest/cmCTestUploadCommand.cxx
copy Source/CTest/{cmCTestUpdateCommand.h = cmCTestUploadCommand.h} (57%)
create mode 100644 Source/CTest/cmCTestUploadHandler.cxx
copy Source/CTest/{cmCTestConfigureHandler.h = cmCTestUploadHandler.h} (55%)
create mode 100644 Tests/CTestTestUpload/CMakeLists.txt
create mode 100644 Tests/CTestTestUpload/CTestConfig.cmake
copy Tests/{CTestTestStopTime = CTestTestUpload}/sleep.c (100%)
copy Tests/{CTestTestCycle = CTestTestUpload}/test.cmake.in (61%)
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-306-gfc6addc
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 fc6addccfdb734c48a76aaec96fef5fcad2940c9 (commit) via 4bb79402e8f4e5c9c01637f70ca9e4d7b682473b (commit) from fff3a742b256afdbc6515f451a7283c1b34f5af4 (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=fc6addccfdb734c48a76aaec96fef5fcad2940c9 commit fc6addccfdb734c48a76aaec96fef5fcad2940c9 Merge: fff3a74 4bb7940 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:43 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:43 2011 -0400 Merge topic 'ModularizeCPack-dot-CMake' 4bb7940 Split CPack.cmake in more manageable parts --- Summary of changes: Modules/CPack.cmake | 503 +- Modules/CPackBundle.cmake| 37 +++ Modules/CPackComponent.cmake | 456 ++ Modules/CPackNSIS.cmake | 83 +++ 4 files changed, 588 insertions(+), 491 deletions(-) create mode 100644 Modules/CPackBundle.cmake create mode 100644 Modules/CPackComponent.cmake create mode 100644 Modules/CPackNSIS.cmake 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-309-gca10dc4
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 ca10dc47865bd764409c5600ba46d9ceb7367350 (commit) via 6a38cab2de2a529779c18e0c3872112e3851665b (commit) via 4371147ef4549feeb88c080cf5ba99281cbb7df3 (commit) from fc6addccfdb734c48a76aaec96fef5fcad2940c9 (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=ca10dc47865bd764409c5600ba46d9ceb7367350 commit ca10dc47865bd764409c5600ba46d9ceb7367350 Merge: fc6addc 6a38cab Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:49 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:49 2011 -0400 Merge topic 'BuiltinIncludeDirFixesForEclipse' 6a38cab Don't skip the last builtin include dir for the Eclipse project file 4371147 Fix parsing include dirs and builtin macros for CXX-only projects --- Summary of changes: Modules/CMakeFindEclipseCDT4.cmake | 12 +--- 1 files changed, 9 insertions(+), 3 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-314-gc90fa7c
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 c90fa7c00c142d42067ce90c07d52c6d489fe815 (commit) via 9c438240661c68da7c0b09b2d08a1facc4fe1dcc (commit) via 64a5e209998f12662a56346f855b1973cbbd0440 (commit) from e560bf4ba3cf860afe5bc8e23cd6d02dd1c366c1 (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=c90fa7c00c142d42067ce90c07d52c6d489fe815 commit c90fa7c00c142d42067ce90c07d52c6d489fe815 Merge: e560bf4 9c43824 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:28:59 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:28:59 2011 -0400 Merge topic 'cpack-grouping-enum' 9c43824 Fix KWStyle warnings 64a5e20 Combine component packaging methods into an enum. --- Summary of changes: Source/CPack/cmCPackArchiveGenerator.cxx |5 +- Source/CPack/cmCPackDebGenerator.cxx |9 ++- Source/CPack/cmCPackGenerator.cxx| 94 -- Source/CPack/cmCPackGenerator.h | 28 +++-- Source/CPack/cmCPackRPMGenerator.cxx |9 ++- 5 files changed, 97 insertions(+), 48 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-317-gb7b9597
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 b7b9597b75ef44b4e7b03020aedfc2466be4dc89 (commit) via dd04608132f6580df6fd857d5bfc4f67ad2b0ec3 (commit) via 2973c1fbebcbaff944ff2d75e5a44437bf9725c7 (commit) from c90fa7c00c142d42067ce90c07d52c6d489fe815 (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=b7b9597b75ef44b4e7b03020aedfc2466be4dc89 commit b7b9597b75ef44b4e7b03020aedfc2466be4dc89 Merge: c90fa7c dd04608 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:29:06 2011 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Apr 5 14:29:06 2011 -0400 Merge topic 'drag-n-drop-components' dd04608 Fix KWStyle warnings 2973c1f Add component support to DragNDrop generator. --- Summary of changes: Source/CPack/cmCPackBundleGenerator.cxx|7 +- Source/CPack/cmCPackBundleGenerator.h |1 + Source/CPack/cmCPackDragNDropGenerator.cxx | 106 +++- Source/CPack/cmCPackDragNDropGenerator.h |7 +- Tests/CMakeLists.txt |3 + .../MyLibCPackConfig-OnePackPerGroup.cmake.in |6 +- .../RunCPackVerifyResult.cmake | 13 +++ 7 files changed, 135 insertions(+), 8 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-1353-g0a27821
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 0a278211183ddbb9bb9417de265612e825e242df (commit) via b7b9597b75ef44b4e7b03020aedfc2466be4dc89 (commit) via c90fa7c00c142d42067ce90c07d52c6d489fe815 (commit) via e560bf4ba3cf860afe5bc8e23cd6d02dd1c366c1 (commit) via ca10dc47865bd764409c5600ba46d9ceb7367350 (commit) via fc6addccfdb734c48a76aaec96fef5fcad2940c9 (commit) via fff3a742b256afdbc6515f451a7283c1b34f5af4 (commit) via c3c19c7cb76a2522bb01421ce1f790b1f7638ebe (commit) via cc2585b1ebe39815250296d1e493931a4456d72b (commit) via 3b16aa622e12f9fff46140291bb423d2b03cf90a (commit) via e252320793bd06b19366ef785734bb2d09b8ccbe (commit) via 485b50c357d325c40cf185d3917af5dc8ec14391 (commit) via a2907bfb8419397dee4a28aeac63556f648df31d (commit) from 1501b2dd73a05061fcb576842c6b795c4c11e83d (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=0a278211183ddbb9bb9417de265612e825e242df commit 0a278211183ddbb9bb9417de265612e825e242df Merge: 1501b2d b7b9597 Author: Brad King brad.k...@kitware.com AuthorDate: Tue Apr 5 14:32:46 2011 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Tue Apr 5 14:32:46 2011 -0400 Merge branch 'master' into next --- Summary of changes: 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-318-g6d7e4d4
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 6d7e4d4043dce6dcfe1fb0b98a3483ee7e02421e (commit) from b7b9597b75ef44b4e7b03020aedfc2466be4dc89 (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=6d7e4d4043dce6dcfe1fb0b98a3483ee7e02421e commit 6d7e4d4043dce6dcfe1fb0b98a3483ee7e02421e Author: KWSys Robot kwro...@kitware.com AuthorDate: Wed Apr 6 00:01:04 2011 -0400 Commit: KWSys Robot kwro...@kitware.com CommitDate: Wed Apr 6 00:12:33 2011 -0400 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index 27324f6..e0acdd7 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 04) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 05) +SET(KWSYS_DATE_STAMP_DAY 06) --- 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
