On Tue, Jul 12, 2016 at 10:48 PM, Chaos Zhang wrote:
> Thanks for your reply Raymond, by 'If you got 96% both times, then I would
> say there's a problem.', did you mean if make performed like this, it means
> this project can't use make -jN?
If "make -j1" and "make -j8" ran
On Tue, Jul 12, 2016 at 7:54 PM, Chaos Zhang wrote:
> Hi, all,
>
> I was trying to compile my project using CMake, after CMake generated
> Makefile.
> I used `/usr/bin/time -v make` to make the Makefile, got the result:
> 'Percent of CPU this job got: 96%'.
> Then i used
_VERSION_MINOR 6)
-set(CMake_VERSION_PATCH 20160712)
+set(CMake_VERSION_PATCH 20160713)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Thanks for your reply Raymond, by 'If you got 96% both times, then I would
say there's a problem.', did you mean if make performed like this, it means
this project can't use make -jN? BTW, does CMake support some options to
turn on hardware acceleration?
Raymond Wan-2 wrote
> Hi Chao,
>
>
> On
A fix for https://gitlab.kitware.com/cmake/cmake/issues/16196
This is my first attempt at doing anything with CMake, so I'd appreciate
any feedback on my patch! In particular, the pairs of file()/string()
commands seem a bit convoluted for extracting strings out of the header
file - is there
Hi Chao,
On Wed, Jul 13, 2016 at 10:54 AM, Chaos Zhang wrote:
> I was trying to compile my project using CMake, after CMake generated
> Makefile.
> I used `/usr/bin/time -v make` to make the Makefile, got the result:
> 'Percent of CPU this job got: 96%'.
> Then i used
Hi, all,
I was trying to compile my project using CMake, after CMake generated
Makefile.
I used `/usr/bin/time -v make` to make the Makefile, got the result:
'Percent of CPU this job got: 96%'.
Then i used `/usr/bin/time -v make -j8` to make the Makefile, the result of
CPU used is 'Percent of
std::basic_filebuf::open(const wchar_t *) isn't part of C++ standard
and it's only present for MSVC but it isn't present in libstdc++ (MinGW)
so we implement this functionality using GNU libstdc++ stdio_filebuf
extension and _wfopen function.
---
CMakeLists.txt | 14 +++
Hello Brad,
please apply my changes.
--
Regards,
Konstantin Podsvirov
From 56137a0f7096bae99eeb45ca83567a5ee87d4cee Mon Sep 17 00:00:00 2001
From: Konstantin Podsvirov
Date: Wed, 13 Jul 2016 00:10:28 +0300
Subject: [PATCH 1/3] CMake: install COMPONENT cmcldeps
Added
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 f4053736f27e15046f0f130d8559414c3bee0c9d (commit)
via
On 7/12/2016 2:11 PM, Dan Ibanez wrote:
Other projects have a whole system atop CMake that manages this.
I'm trying to get a sense of what the "best" setup looks like using pure
CMake.
See Usage Requirements:
https://cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#id10
Hello,
I've used CMake for a while but only recently
discovered several features for better installing a package, and am
trying to update the way I use CMake.
My question as to do with projects which contain
several modules/components/libraries, each of which is in a subdirectory.
Each library
Hello all,
What is the current best practice for code signing OSX .apps and binaries? I am
using:
1. MAC_OSX_BUNDLE for my .app targets.
2. unix style executables
3. dylibs
4. A prefpane (which I haven't got working yet) using something like the below:
add_library(prefpane MODULE
Hi Breannan,
You can track the status of the fix at
https://gitlab.kitware.com/cmake/cmake/merge_requests/34
On Mon, Jul 11, 2016 at 8:52 AM, Robert Maynard
wrote:
> Hi Breannan,
>
> I am able to reproduce this and will start digging into why this is occurring.
>
>
Hi Brad,
A simple version, which covers the main test case is shown here. The %files
list in the auto spec file shows "%dist.txt" when I think it should show
"%%dist.txt". Even when I manually changed it to %% it didn't work for me
though. Maybe someone who knows RPM better would be able to
On Tuesday, July 12, 2016 10:43:52 AM CEST Daniel Pfeifer wrote:
> Hi,
>
> CMake currently puts messages like "Generating moc source" into the
> buildlog. This conflicts with the convention "no output == all good".
+1
> The messages blend nicely in the colorful output of Unix Makefiles,
> but
Hi,
CMake currently puts messages like "Generating moc source" into the
buildlog. This conflicts with the convention "no output == all good".
The messages blend nicely in the colorful output of Unix Makefiles,
but when using the Ninja generator, they create quite some noise.
How can this be
Hello,
I am new to Cmake and I have a pretty strange behaviour: I set my c+++
project to work with a single CMakefile.txt, and now I am trying to have
a more proper version with a .txt for each subdirectory
Pretty normal stuff, my source tree is:
--Lib(my sources)
18 matches
Mail list logo