Hello all,
I am mainly asking having glib-compile-resources in mind. This little
program translates files into C source code to be used with the
gresource system. It works in the following way: You have a file.xml
describing the resources:
?xml version=1.0 encoding=UTF-8?
gresources
gresource
On 2014-12-09 08:56+0100 Nils Gladitz wrote:
On 12/09/2014 08:30 AM, Micha Renner wrote:
Hi,
what does this message mean?
The ASM_MASM compiler identification is MSVC
CMake Warning (dev) at C:/Program
Files/CMake/share/cmake-3.1/Modules/CMakeFindBinUtils.cmake:33 (if):
Policy CMP0054 is
Hi Nils:
I have never understood CMP0054 until now when I read your above
clear explanation. So thanks very much for that!
My problem was the bad/ambiguous documentation of CMP0054 at
http://www.cmake.org/cmake/help/v3.1/policy/CMP0054.html which
states
Only interpret if() arguments as
On 12/8/2014 10:05 PM, Bartlett, Roscoe A. wrote:
The problem with the current implementation of
CMakePackageConfigHelpers.cmake is that it does not have a mode where X
in X.Y.Z defines a backward compatible set.
It has a SameMajorVersion mode which is close, but IIUC a
SemanticVersion mode
Am Dienstag, den 09.12.2014, 01:52 -0800 schrieb Alan W. Irwin:
Hi Nils:
I have never understood CMP0054 until now when I read your above
clear explanation. So thanks very much for that!
Same from me. Excellent work. It makes things clearer.
Greetings
Michael
--
Powered by
No one?
The patch is already working.
Am 12.11.2014 um 09:45 schrieb NoRulez noru...@me.com:
Hi,
is it possible to get the patch for the green hills generator into CMake 3.1
Thanks in advance
Best Regards
--
Powered by www.kitware.com
Please keep messages on-topic and
Well of course it had to not be all that simple. My first attempt to
create a simple (2 header files in library) example failed to fail in the
same way as my much more complex real-life project. :-p
I will continue to try to whittle down the real problem to the smallest
possible set, but it may
On 12/09/2014 03:25 PM, NoRulez wrote:
No one?
The patch is already working.
3.1 has been closed for a while now since it is being prepared for
release. New features are unlikely to get accepted at this stage.
Looking at the mailing list thread it sounds like the patch is still
work in
Is Mastering CMake still the only book out there?
BTW, the doc site for 3.0 is great, I really appreciate the effort
that went into it.
- Dan
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various
On 12/9/2014 9:45 AM, Chris Johnson wrote:
Well of course it had to not be all that simple. My first attempt to
create a simple (2 header files in library) example failed to fail in
the same way as my much more complex real-life project. :-p
I will continue to try to whittle down the real
Let's try again...
I submitted a question last week but got no responses so I have assumed my
question and/or example was not explicit enough. I have stripped out all
unnecessary structure from the code and am posing the question better (I
hope)...
The functionality that I am using is expressed
Hi all,
check_cxx_source_compiles is failing for me.
I can compile the test program from the command line, no problem.
I'm taking the flags passed to the working command line and setting them to
CMAKE_REQUIRED_FLAGS before check_cxx_source_compiles.
How do I see the command line that cmake is
On 12/9/2014 1:53 PM, Vince Harron via CMake wrote:
How do I see the command line that cmake is trying?
Look in CMakeFiles/CMakeError.log.
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971
Pretty much. There is also the slim e-book Introduction to CMake [0].
[0]
http://www.amazon.com/Introduction-CMake-Software-Tool-Book-ebook/dp/B00KE807Q0/ref=la_B00GPU8HLS_1_1?s=booksie=UTF8qid=1418153199sr=1-1
On Tue, Dec 9, 2014 at 9:47 AM, Dan Kegel d...@kegel.com wrote:
Is Mastering CMake
On 12/09/2014 12:26 PM, J. Caleb Wherry wrote:
add_library(ExtLib SHARED IMPORTED)
set_property(TARGET ExtLib PROPERTY IMPORTED_LOCATION
${CMAKE_BINARY_DIR}/${EXT_LIB_NAME})
add_dependencies(ExtLib ExtLibBuild)
Thanks for the complete/simple example. The problem is that
the libExtLib.so
That's the strange thing. All the dependencies in those files in the real
project look right. It's as if they are just not getting used during the
library compile, although they do get used when the program is linked to
the library and the current-ness of the library is checked before the
actual
Works like a charm, I knew I was overlooking something small. Thanks, Brad!
-Caleb
On Tue, Dec 9, 2014 at 2:30 PM, Brad King brad.k...@kitware.com wrote:
On 12/09/2014 12:26 PM, J. Caleb Wherry wrote:
add_library(ExtLib SHARED IMPORTED)
set_property(TARGET ExtLib PROPERTY IMPORTED_LOCATION
I am proud to announce the CMake 3.1 third release candidate.
Sources and binaries are available at:
http://www.cmake.org/files/v3.1/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.1
Release notes appear below and are also published at
Hey all,
I'm working on a module that will allow me to automatically copy all the
required .dll files as defined by well-formed import library targets to
the appropriate location (same folder for windows, Frameworks folder for
OSX bundle, ect). I've got the code that scans an executable's
This sounds more like an install phase... to bring the whole package
together in one appropriate place.
if( WIN32 )
INSTALL( TARGET target RUNTIME DESTINATION bin LIBRARY DESTINATION bin
ARCHIVE DESTINATION lib )
else( WIN32 )
INSTALL( TARGET target RUNTIME DESTINATION bin LIBRARY DESTINATION lib
Mind you 'install' doesn't have to be '/usr' or 'program files/whatever'
but could be 'output' which will be relative to ${CMAKE_BINARY_DIR} if not
absolute
On Tue, Dec 9, 2014 at 4:15 PM, J Decker d3c...@gmail.com wrote:
This sounds more like an install phase... to bring the whole package
On 12/9/14, Walter Gray chrysal...@gmail.com wrote:
Hey all,
I'm working on a module that will allow me to automatically copy all the
required .dll files as defined by well-formed import library targets to
the appropriate location (same folder for windows, Frameworks folder for
OSX bundle,
This is all handled by install.
Plugins get installed in their correct directory
resources; data files etc get installed in their correct directory...
each type of target is handled with INSTALL( TARGET ) but you get 3
destinations; RUNTIME (exe), LIBRARY(.dll,.so) and ARCHIVE (.lib,.a) ; they
On 12/9/14, J Decker d3c...@gmail.com wrote:
This is all handled by install.
I already addressed INSTALL. I know you can change the directory. That
is irrelevant to the point which I already addressed.
Sounds really like you're working to build a package, which install is
intended to do.
On Tue, Dec 9, 2014 at 4:58 PM, Eric Wing ewmail...@gmail.com wrote:
On 12/9/14, J Decker d3c...@gmail.com wrote:
This is all handled by install.
I already addressed INSTALL. I know you can change the directory. That
is irrelevant to the point which I already addressed.
You gave a
Your scripts would still only work for one target... since you'd have to
pick one to build the rest of the package around, so if I have a build
product that has a dozen utilities, rather than having one place they can
all work from, I have now to either duplicate all files to all runnable
I'm now calling it out as a design problem in
CMake, especially as the winds have shifted to more platforms focusing
on shipping binaries than the former and now treat packaging as a
first class citizen. It is an impediment to the natural workflow on
those platforms, it is an impediment to
Fixed typo in commit message:
VS, WINCE: Fix entry point for Unicode builds
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=681cda02
I figured out that the combination /ENTRY:mainCRTStartup is also possible even
if UNICODE is enabled.
The question is now what should CMake do as
On 12/09/2014 09:40 AM, Daniel Scharrer wrote:
This caused find_package(Qt4) to appear successful when it was not.
Note that the legacy QT4_FOUND variable is unconditionally overwritten
at the end of the file with the value of Qt4_FOUND.
Applied with slightly modified commit message:
On 12/09/2014 09:45 AM, Bach, Pascal wrote:
the old behavior was better. The user should then be able to set the
entry point independent of the UNICODE setting via a target property.
This would be similar to how WIN32_EXECUTABLE selects WinMain as
startup.
Good catch. They are
On 12/09/2014 10:46 AM, Bach, Pascal wrote:
Is there a place where we could document things like this in the
CMake documentation? Something like a platform specific collection
of best practice and commonly required tasks.
The closest place to something like that is here:
On 12/09/2014 10:57 AM, Bach, Pascal wrote:
set_target_properties(target PROPERTIES LINK_FLAGS /ENTRY:mainCRTStartup)
I prefer to use LINK_FLAGS only as a last resort. For common settings
we should provide a first-class setting.
For consistency reason there could be something like a
08.12.2014, 17:26, Brad King brad.k...@kitware.com:
On 12/07/2014 05:34 PM, Konstantin Podsvirov wrote:
Well, work has started!
Good work so far.
I tried :-)
Please reorganize the commits to have the first one add the install
COMPONENT options and the second one add the CPack configuration.
Hi,
is there an easy way to compile Qt 5.2.1 using CMake?
Thanks,Imran
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each
On 12/9/2014 6:02 AM, Gregor Jasny wrote:
See:
https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/testing_with_xcode/
Thanks.
On non-Apple platforms and Xcode 5.0 those XCTest bundles are pretty
useless.
What should CMake do on those platforms? The fact that
On 12/9/2014 6:02 AM, Gregor Jasny wrote:
+XCTEST_HOST
+---
+
+XCTest works by injecting an XCTest CFBundle directly into an AppBundle
+or Framework. This property names this destination target under test.
Please add mention of :prop_tgt:`XCTEST` here.
\ No newline at end of file
On 12/9/2014 1:39 PM, Konstantin Podsvirov wrote:
That looks good, except that cmake/ctest/cpack must all be in
one component.
specify whether the component is required and can be specified as
any of the components referenced by this component.
I suppose they can be separate components as
I am proud to announce the CMake 3.1 third release candidate.
Sources and binaries are available at:
http://www.cmake.org/files/v3.1/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.1
Release notes appear below and are also published at
Stephen Kelly wrote:
This looks like it needs a suffix. GSL_CONFIG_EXECUTABLE would seem
appropriate.
# Windows with dlls, but only Release libraries.
set_target_properties( GSL::gslcblas PROPERTIES
IMPORTED_LOCATION ${GSL_CBLAS_LIBRARY_DLL}
This should be
Brad King wrote:
0002-first-try-to-see-if-what-user-provided-produces-an-m.patch
The check for whether the CMAKE_LANG_COMPILER is already a
MPI compiler requires a try_compile. Is there some other way
to check to see if there is any chance before the full test?
I have been looking into
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 391654193b2be0815c0a546ca0a9a3d6a092af8e (commit)
via
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 5e666d80cabcae57555df81df15cd2e70177b865 (commit)
via
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 98d9f6e3e107a5c17b03e3003d7ab92ffdc33677 (commit)
via
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 3b9477231d2947fa6281a1e29b4459d3f66d4a49 (commit)
via
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 c58581c63a990ff54882b61c64249a63a37b9d51 (commit)
via
45 matches
Mail list logo
