The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15042
==
Reported By:Lucas Betschart
Assigned To:
On 07/24/2014 03:57 AM, Mathieu MARACHE wrote:
I added two plugins qnativewifi and qtga that where missing in FindQt4.cmake
Applied, thanks:
FindQt4: Add nativewifi and qtga plugins
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4b5052b0
-Brad
--
Powered by www.kitware.com
Please
On 07/25/2014 09:54 AM, Daniele E. Domenichelli wrote:
Some projects also arrange their layout within the build tree to look
like the install tree by setting CMAKE_RUNTIME_OUTPUT_DIRECTORY[_CONFIG]
and related variables appropriately.
That's exactly what I would like to be able to do, but
On 07/25/2014 10:00 AM, Daniele E. Domenichelli wrote:
Sorry if I insist, but I still don't understand why not allowing to be
able to use CMakePackageConfigHelpers for the build tree
I didn't mean to imply that the patch is not acceptable. After the
revisions to the documentation from our
On 07/24/2014 05:47 PM, Nick Overdijk wrote:
I'm using target_include_directories of A to get some include
directories into B well, so I can't use
target_link_libraries(A INTERFACE B),
Can you clarify this with sample code please?
and I can't seem to use the OBJECT-way neither since B's
On 07/23/2014 04:44 PM, Brad King wrote:
These draft commits are now in 'next' for upstream testing.
After squashing in one fixup for building with CMake 2.8.9
this feature is now in master:
CPack: Add an IFW generator for Qt Framework Installer
On 28/07/14 16:11, Brad King wrote:
On 07/25/2014 10:00 AM, Daniele E. Domenichelli wrote:
Sorry if I insist, but I still don't understand why not allowing to be
able to use CMakePackageConfigHelpers for the build tree
I didn't mean to imply that the patch is not acceptable. After the
The following issue has been SUBMITTED.
==
http://www.gccxml.org/Bug/view.php?id=15043
==
Reported By:Ravi Raman
Assigned To:
The following issue has been SUBMITTED.
==
http://www.gccxml.org/Bug/view.php?id=15044
==
Reported By:Ravi Raman
Assigned To:
Hi!
i am using the cmake feature with target_link_libraries for static libraries to
describe additional link dependencies from static libs e.g. to system libs and
qt libraries.
The cmake files is use are used for developper build and customer build, but
the customer does not get all source
On 07/28/2014 10:33 AM, Jörg Kreuzberger wrote:
But on this imported targets i cannot define these link dependencies with
target_link_libraries. Which properties could i set on the IMPORTED Targets to
get the same behaviour?
Hi,
In cmake-packages(7) [1], there is a typo that prevents the example from
working correctly.
The command
configure_file(cmake/ClimbingStatsConfig.cmake
${CMAKE_CURRENT_BINARY_DIR}/ClimbingStats/ClimbingStatsConfig.cmake
COPY_ONLY
)
should use COPYONLY, not COPY_ONLY.
Cheers,
In fact, it's not just a documentation typo.. It occurs three times
in cmake 'next' and 'master':
$ git grep COPY_ONLY
Help/manual/cmake-packages.7.rst:COPY_ONLY
Modules/Qt4Macros.cmake: configure_file(${infile}
${out_depends} COPY_ONLY)
Source/kwsys/CMakeLists.txt:
Hi David,
You can add to the search path CMake uses by appending to the
CMAKE_MODULE_PATH variable. In your case, you'll probably want to set it
before the project command to make sure it's present for you're entire
project. For example:
In your project, you create CMake directory where you
Hi there,
We’re looking to update our CMake packaging scripts so that we can deploy to
OSX 10.9 Mavericks. For previous OSX releases, we have used the PackageMaker
generator with CPack to create .pkg files inside .dmg files. I believe
PackageMaker has now disappeared (I can’t run the old
Thanks Mihai,
That’s good to know. Having said that, I’m now knee deep in this stuff so
if anyone has any recommendations on how to proceed going forward (e.g.
with app bundles), that would be great.
Regards,
Lachlan Hetherton
Software Engineer (Visualisation)
☎ +613-9545-8041
On 7/29/14,
On 29.07.2014 03:06 am, lachlan.hether...@csiro.au wrote:
I believe PackageMaker has now disappeared (I can’t run the old version on my
current machine and there doesn’t seem to be a new version available anywhere)
A Mavericks-compatible version of PackageMaker is available on
As a further FYI, I have tried installing that version of PackageMaker and
it simply crashes on load, so I’m not sure whether this is even an option
any more.
Regards,
Lachlan Hetherton
Software Engineer (Visualisation)
☎ +613-9545-8041
On 7/29/14, 11:31 AM, Mihai Moldovan io...@ionic.de
I lie, it does run - the wrong version of the PackageMaker executable was
on my PATH.
As you say - at least this will keep me going for the time being, but we
will need a way of building our application as a framework bundle or
something similar going forward (keep in mind that we also deploy to
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 d655bffdfa67691dccbcad2acf5be9891e9f37e7 (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 a658e61dadbc1619eda8a10da0b7d237eb737036 (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 f8d67f90f0a88a368d154cc1e6bbe6566d9f7dc4 (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 89907b37665ab05492a496eac7fdf19990e550e8 (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 d128c6c9b33f4ca3139352baee774a9e08f6c32e (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 2699ac5ef727c824e22dc515149529783d8b9a8f (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 fd0229e8c5bffa4807962dbe4e077ae7ac2d3dda (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 68f4a0ee306e5b5aec1252d0e7ed2af93273ee9f (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 107db681e3a1298463c7f432a2756ee59516ad47 (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 9303da53ce980bf71df52f3e75ed18f93127d7b9 (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 d7ab2e432828b7af15840956a643900ff22479d6 (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 90f6de8a0192eb169be2a7e0ddbe8bce9d6714fb (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 0f06bb52baafca335d495a14de5a942fae8dffe8 (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, release has been updated
via ce7a5ca895d0669b33d213c6fc94f484611d6e24 (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 f188845237cdfee74dae065a61c855e285b3 (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 309d1a645e358d0b88414d6b95e0d13185d8c1f6 (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 df5e2d8d9bd26508d1d3e4fa974928ff16aaf42d (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 32adeae6c4c1edae5087c0a7ddb833f65aa79de8 (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 53ecb02357acb3e5b520aa400d1205e8d823b957 (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 e5c672d0d46ee61ccd9c789ba0aaf0c20916b567 (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 2a4a4c3f152c7de8ca4cf13170d0ddbfdb587274 (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 4dbe18970588193b9b181bd6c8b5102bb2cfb1c9 (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 4cedb1e377afb5ee7f6cbf8f2016bb0ff6d03e95 (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 7f962dfebf65a6d0aa386c5def86d85725da34bd (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 b2c6c531909aa6c58c5a89bf99f0e0767cb39208 (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 767c8c39ef2a37ab0c3cbe4c50a429abd1613886 (commit)
via
20140728)
+set(CMake_VERSION_PATCH 20140729)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
46 matches
Mail list logo
