Well, I tried upstreaming the new build scripts to some projects and it
didn’t go well.
Some of the reasons I’ve heard of:
> I installed CMake 2.8.6 five years ago and I don’t want to update yet
> again! People relying on old versions is quite common and any attempt
> to raise the min version
_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160816)
+set(CMake_VERSION_PATCH 20160817)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Ah, I misunderstood what you were asking about. It would be pretty
weird if CMake didn't know that static libraries always need all their
dependencies linked regardless of privacy, but I agree it should at
least be mentioned somewhere. My bad.
As for include path bloat, I cannot replicate this in
TBH, I do not see the "PRIVATE dependencies are made PUBLIC for the
purposes of linking when the dependent is static library" there.
--
Ivan Shapovalov / intelfx /
On 2016-08-16 at 02:35 -0500, Nicholas Braden wrote:
> Yes, the behavior is documented in several places, the most prominent
>
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 662661b2b462946f8ba6c82af22f014a18619756 (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 11d0fcfcfecdcef2e21a1acb550979d208e43aa0 (commit)
via
Hi CMake people!
I notice that there is no CPack generator for Microsoft's .appx package format.
I would like there to be. It seems pretty straightforward to do...basically
just get all the files into the right directory structure (similarly to the
archive generators, I think), and then call
For what it's worth, what I've done here is to create binary packages of each
third-party library for each supported platform (i.e. .deb packages for Ubuntu,
.rpm packages for RHEL/CentOS, Chocolatey packages for Windows). Except for
cases where the system already provided sufficient versions
On 16-Aug-16 16:37, Florent Castelli wrote:
Well, I tried upstreaming the new build scripts to some projects and
it didn’t go well.
Some of the reasons I’ve heard of:
- Windows developpers don’t use CMake, they have project files on the
repository.
The CMake files for Windows will never be
On 13-Aug-16 03:12, Elizabeth A. Fischer wrote:
I don't think CMake is the best place to do it, for a number of
reasons. I would not try to re-invent the wheel here.
Can you provide any details? I personally think that CMake is a natural
and the only place where it should be done.
On
On 08/16/2016 02:39 PM, Tobias Hunger wrote:
> Did you make any progress with libuv? I would love to start pushing
> the server-mode patches. All the other pieces are in place already!
Great. I haven't gotten a chance to import libuv yet. Now that
you're ready for it I'll try to raise priority
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 bbafe31c4f905a77622f6da7307c05dba838ac80 (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 1dde35c113c24ec4d47e1a624ee68ae797e6a2c6 (commit)
via
On 08/15/2016 04:34 PM, Dāvis Mosāns wrote:
> Typically Windows applications (eg. MSVC compiler) use current console's
> codepage for output to pipes so we need to encode that to internally used
> encoding (KWSYS_ENCODING_DEFAULT_CODEPAGE).
Thanks. Applied with minor tweaks and merged to `next`
On 08/15/2016 02:24 PM, Alex Ciobanu wrote:
> Are there any plans in this direction?
Not currently, but one can look at the implementations of the currently
supported formats to add it.
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 08/15/2016 09:56 AM, Tobias Hunger wrote:
> here is a new update of the cmake -E capabilities patch.
Thanks. Applied with minor revisions and an additional test:
cmake: Add `cmake -E capabilities` mode
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=49ad7f9a
-Brad
--
Powered by
On 08/16/2016 07:11 AM, Titov Denis wrote:
> This patch introduces several options for the file(DOWNLOAD ...) command,
> which
> would be useful in case of dealing with big files or unstable network
> connections.
Nice, thanks. Good start. Here are a few minor comments.
> The added options
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 8bc1788a12d60261a957b98254694c4a776ce62a (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 bf26fa0d1e1eea567b656366e0510e9018b530cd (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 1b6398fea8e3606984decc76dc0d38092985fbd7 (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 074d098ffb001c6e6c03483746c7bb6e02ab4484 (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 447b142b6a5ae8ee1669cb1a424619af808f1c17 (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 cac8c6542a38c2a234e39af7a99e46e8ad5ab336 (commit)
via
On 16-Aug-16 17:04, Florent Castelli wrote:
On 16 Aug 2016, at 15:29, Ruslan Baratov > wrote:
On 16-Aug-16 13:52, Florent Castelli wrote:
For example, Boost is used by 5 platforms: Windows, OSX, Linux,
Android and iOS.
Each
On 16-Aug-16 13:52, Florent Castelli wrote:
For example, Boost is used by 5 platforms: Windows, OSX, Linux, Android and iOS.
Each platform has a different CPU target (or many 32/64bit, x86/ARM).
Each platform has many compilers.
Some platforms have instrumentation options (Debug / Release, ASan,
We have many smaller libraries and a few big ones like Boost.
It certainly takes a bit of time to setup, but it will save you a lot of time
later.
It will keep your build scripts clean too as the user won’t have to know about
its dependencies setup. Just use “target_link_libraries” on the modern
CMake builds for existing libraries are certainly an interesting and useful
thing, and deserve to be posted in a GitHub repo somewhere. They should
also serve as the basis of a campaign to get the library authors to
incorporate the CMake build directly in their repos.
But any approach that
CMake builds for existing libraries are certainly an interesting and useful
thing, and deserve to be posted in a GitHub repo somewhere. They should
also serve as the basis of a campaign to get the library authors to
incorporate the CMake build directly in their repos.
But any approach that
Very interesting discussion, we have the same issues here.
Florent Castelli, how many third parties libraries do you use ? I think a
super build can be a very good solution but I'm wondering how much third
party code you have to build. Here we use OpenCV, with, boost, and poco,
and other
Very interesting discussion, we have the same issues here.
Florent Castelli, how many third parties libraries do you use ? I think a
super build can be a very good solution but I'm wondering how much third
party code you have to build. Here we use OpenCV, with, boost, and poco,
and other
This patch introduces several options for the file(DOWNLOAD ...) command, which
would be useful in case of dealing with big files or unstable network
connections.
The added options are:
RETRY_COUNT -- sets maximal amount of download restarts, default value: 1
RETRY_DELAY -- sets delay before
At Spotify, we use CMake a lot for our large C++ library shared by all the
clients.
After trying to build libraries for each platform and variant, we basically
gave up and we now
use a super-build approach.
For example, Boost is used by 5 platforms: Windows, OSX, Linux, Android and iOS.
Each
On 08/16/2016 11:15 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
There is precedence in cmWIXFilesSourceWriter::EmitComponentFile() so I
think such an interface change would be fine.
Ok I'll do this. Should solve all issues and doubts hopefully.
Great. Thanks.
Adding FeatureRef to #PRODUCT
> -Original Message-
> From: Nils Gladitz [mailto:nilsglad...@gmail.com]
> Sent: Tuesday, August 16, 2016 10:54 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: Re: [cmake-developers] [Patch 5/5] Improved WIX support
>
> On 08/16/2016 10:15 AM, Stuermer, Michael
Yes, the behavior is documented in several places, the most prominent
being here:
https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#transitive-usage-requirements
On Mon, Aug 15, 2016 at 9:22 PM, Ivan Shapovalov wrote:
> On 2016-08-15 at 21:46 -0400,
Hi,
I was looking at tools that can do this kind of things myself (however I
was more looking at pre-built binaries redistribution than at a
super-build, since our build time is already quite long).
Does Conan (https://conan.io/) not fit your bill as well ?
Best
Le dim. 14 août 2016 à 02:33,
36 matches
Mail list logo