On 11/09/2014 12:05 PM, Daniele E. Domenichelli wrote:
Fix regression in link order introduced by the link-line-dedup topic
Thanks. I revised the implementation slightly to avoid prepending
to a vector on every iteration. I've merged to 'next' for testing:
Fix link line order when shared
On 11/10/2014 10:46 AM, Daniele E. Domenichelli wrote:
- See if it can be integrated into the Tests/Dependency test,
perhaps as a new Case5 directory.
Done, see:
Convert the test to use C only and move it into Tests/Dependency/Case5
On 10/11/14 15:18, Brad King wrote:
However, the test does not fail for me even without the fix. I
think for 3.1.0-rc2 I will take this fix but not the test yet.
Please extend the topic to revise the test:
The test fails for me on a ubuntu precise chroot using gcc 4.6.3 (I
wasn't able to
On 11/07/2014 09:58 AM, Brad King wrote:
I need to resolve the issues with the curl update and also
get Clinton's 3.1 regression fix through.
This is done, but a couple more regression-fix topics now need to
go through in preparation for 3.1.0-rc2, so please continue to
hold off on new topics
On 11/08/2014 04:17 PM, Domen Vrankar wrote:
Patch add support for symlink handling in RPM packages.
Symlinks to directories and files are correctly recognized as such so
directory symlinks are no longer prefixed with %dir.
In case of relocatable RPM packages the patch also tries to make
On 10/11/14 16:49, Brad King wrote:
Thanks. Please rename the 'foo' and 'bar' libs to 'case5Foo' and
'case5Bar' to avoid conflict with other cases in the future.
Done:
Rename the 'foo' and 'bar' libs to 'case5Foo' and 'case5Bar'
Done
On 31-Oct-14 16:39, Brad King wrote:
On 10/31/2014 09:07 AM, Ruslan Baratov wrote:
Does anybody ready to implement it or you want me to send the patches?
Please work on the patches. You can use git format-patch to format
them and post here either inline or as attachments.
Thanks,
-Brad
On 11/10/2014 06:32 AM, Nicholas Yue wrote:
I am improving an in-house Find*.cmake and need to determine
(programmatically) where it (the Find*.cmake file) is located because I
need to run a companion python script. Is there some variable I can query ?
CMAKE_CURRENT_LIST_DIR for the full
On 11/10/2014 07:44 AM, Nicholas Yue wrote:
Hi,
Using CMake 2.8.12.2 on Windows 7 x64 with Visual Studio 2012
WDExpress, my include_directories() information are being embedded in
the AdditionalOptions part of the generated *.vcxproj XML file instead
of the AdditionalIncludeDirectories part
On 11/09/2014 08:34 PM, SF Markus Elfring wrote:
Hello,
I configured a specific software to use the CPack modules to generate
corresponding DEB and RPM packages together with CMake 3 a while ago.
I notice now that package specifications and control files contain
outdated version data after
On 11/10/2014 07:40 PM, SF Markus Elfring wrote:
You could, as a workaround for the problem, define a add_custom_target
that removes the corresponding rpm/deb packages and just calls 'cmake
--build --target package' to regenerate them.
Thanks for your suggestion.
It's not an ideal solution,
You could, as a workaround for the problem, define a add_custom_target
that removes the corresponding rpm/deb packages and just calls 'cmake
--build --target package' to regenerate them.
Thanks for your suggestion.
It's not an ideal solution, but it worked just fine for me.
Does this
I actually don't know if this is an omission or a deliberate design choice.
How often do use DEB and RPM package generation with CPack for your software?
Regards,
Markus
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 11/10/2014 07:50 PM, SF Markus Elfring wrote:
I actually don't know if this is an omission or a deliberate design choice.
How often do use DEB and RPM package generation with CPack for your software?
Regards,
Markus
I used it quite often (only rpm), but having said that: I had a need for
Hello,
Software package formats like DEB and RPM can help to distinguish
the provided contents between source and binary files.
https://wiki.debian.org/SourcePackage
http://www.rpm.org/max-rpm/s1-rpm-miscellania-srpms.html
How can I achieve a corresponding distinction with CPack?
Hello CMake Team,
I would like to know how to import Visual studio project properties using
CMAKE? And what is the equivalent command for Import element in CMake?
Below is the section in the *.vcxproj file where I am importing
General_Project_Properties.props file.
Example :
ImportGroup
Rolf Eike Beer wrote
Yes, but the preferable solution would be that you ship a
OpenBLASConfig.cmake
with your installation, so it would work with any CMake version and you
can
adapt that file yourself in case of new components, library locations or
other
things.
Why would OpenBLAS
Am 10. November 2014 21:45:26 MEZ, schrieb SF Markus Elfring
elfr...@users.sourceforge.net:
Hello,
Software package formats like DEB and RPM can help to distinguish
the provided contents between source and binary files.
https://wiki.debian.org/SourcePackage
On Nov 10, 2014, at 5:03 PM, cgorac cgo...@gmail.com wrote:
Rolf Eike Beer wrote
Yes, but the preferable solution would be that you ship a
OpenBLASConfig.cmake
with your installation, so it would work with any CMake version and you
can
adapt that file yourself in case of new
There is no need for a .src.rpm when you don't embed the build rules into it.
However, that only makes sense for distributions that have a package
maintainer for the software,
creates a source package with all build options and distribution adaptions.
Have you got any more ideas for the
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 5e10724b877305a5a3c563f375d25937789935bd (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 a164662de75029eabb903dde17bb9ce54e367c9f (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 98bdf4a06ab89ef5d992827f7493902eee38819d (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 705f2acf56b79ec0479fb652a143229d954c6769 (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 ebd81079a5735fafb10f7902720ed88e7dadc84d (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 81deda391e459e271e14a4759838c9b6dddc37bc (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 f62e476990df9814b6be61a231b6b4e3ff140547 (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 8532a4f9a061883dea639b2f7942c93a6682bc49 (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 6431cc641bf42551ef6b5d7019fe857909d593fc (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 a1f964ef6897343cd47f904b7cf7ad94b2b65e70 (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 ee6c79d1a34fba29d321ff00b19e79bda472c0d7 (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 472f9204eeb6eaebf3c26e1e6404bc023149cbf8 (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 742e6f8f06a635bbc0cb10a36ce68d5b9987f1f5 (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 75f3a282b76baf615b17767d3768b781bfc463a7 (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 e9371739dd907e0309fbaa034e583efb54f100dd (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 89dcb01ee34bc45f43f34cda1a72fa3abde7a153 (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 224ece3d2e7c8b4d5f1b8b0ce7dcd623812597d0 (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 dfddf17df79aa61b1a305d0480ab8c1b7f95a5c8 (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 47374d622e9f0543875c4dfca4174ed60a19323b (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 a5ac2c8c66194e177ba45ed328c1fcc0fbbda143 (commit)
via
20141110)
+set(CMake_VERSION_PATCH 2014)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
41 matches
Mail list logo
