_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20170129)
+set(CMake_VERSION_PATCH 20170130)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
On 2017 M01 26, Thu 18:23:05 CET Gonzalo Garramuño wrote:
> I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my
> work.I distribute a binary image viewer. However, recently one of
> my users tried to run the viewer on a CentOS 7 distro and found out that
> that distro libc
Oh ok, I see how it works, it makes sense, but I'm somehow disappointed : in
order to use it, I'm going to have to change my own project while I originally
thought it was going to be a kind of FindXXX on steroid...
I'll give it a try though, tx for pointing it out.
David
Le 26 janvier 2017
Hello,
Yes, main reason is I had to hack FindProtobuf.cmake to make our existing
project compile.
Also since I need to make it "installable", I had to add some stuff to have the
binaries and header installed automatically when referenced.
The latter reason led me to experiment with
> What's weirder (and I forgot to mention) is that if I just build the project
> normally outside of my regression testing script (ie. "make -j5"), I don't
> get the jobserver warning.
The reason for this error message from make is given at [1].
I've seen something like this before when my build
On 29.01.2017 13:29, Dave Flogeras wrote:
I tried with "make -j5 VERBOSE=1 NightlyBuild" but didn't see anything
indicative on the console, or in the cmake output files that shed any
light for me.
What's weirder (and I forgot to mention) is that if I just build the
project normally outside
Hey Paul
On Sat, Jan 28, 2017 at 10:43 AM, Paul Smith wrote:
> My suspicion is that somehow the recursion is invoking an older version
> of make. In GNU make 4.2 the jobserver interface was stabilized and
> published, so that other build tools could take advantage of it
Am Montag, 9. Januar 2017, 10:59:13 schrieb Rolf Eike Beer:
> I need for several projects the ability to set CMAKE_C_STANDARD on older
> compilers, at least gcc 4.2, but preferably also down to gcc 3.4. I have
> them available, so testing is not the issue. But there are some problems
> besides