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 d96d971ac048acc8fa266b2e1320cc7f0470aeae (commit)
from
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
discards e6cd443763d90583d1664403619979b4bce44393 (commit)
discards
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, nightly-master has been updated
via e7e939058d568a7aac9952386057fc869c240a9e (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, nightly has been updated
via e6cd443763d90583d1664403619979b4bce44393 (commit)
via
On 2017-03-03 16:14+0100 Bernhard Seckinger wrote:
My advice for putting together that bug report is to create the
simplest standalone example of the problem that is possible (e.g.,
consiting of a CMakeLists.txt file that builds and installs a "hello,
world" D application + D language source
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 e6cd443763d90583d1664403619979b4bce44393 (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 fddee0f94de26cd9540becfca7ad81716023f767 (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 e7e939058d568a7aac9952386057fc869c240a9e (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 e7e939058d568a7aac9952386057fc869c240a9e (commit)
via
On 03/02/2017 03:55 PM, Brad King wrote:
> Once we have actually made the final transition I'll merge the new
> instructions and post a link here to their final URL.
The transition is complete! Documentation of the review process is
now rendered directly on the gitlab repo page [1]. 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
discards 5f769885a006aff41f31b544aa4c0e020a77a809 (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 75da91ab952ad770c2d1fe9a96aa630a4d02738e (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 5f769885a006aff41f31b544aa4c0e020a77a809 (commit)
via
> On Mar 3, 2017, at 9:23 AM, Miroslav Drahos wrote:
>
> Hi,
> I am getting errors emanating from GenerateExportHeader.cmake and hope
> someone has any pointers on this. The error:
>
> CMake Error at /usr/share/cmake-3.5/Modules/GenerateExportHeader.cmake:362
>
Hi,
I am getting errors emanating from GenerateExportHeader.cmake and hope someone
has any pointers on this. The error:
CMake Error at /usr/share/cmake-3.5/Modules/GenerateExportHeader.cmake:362
(configure_file):
configure_file Problem configuring file
Call Stack (most recent call first):
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, nightly has been updated
discards 51581b7074637074499ee9246428b787b6406096 (commit)
discards
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
discards 51581b7074637074499ee9246428b787b6406096 (commit)
discards
I am proud to announce the second CMake 3.8 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.8
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.8/release/3.8.html
Some of the more significant
I am proud to announce the second CMake 3.8 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.8
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.8/release/3.8.html
Some of the more significant
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 annotated tag, v3.8.0-rc2 has been created
at 3e8a1a2821c247ffe4b1ee297593b7fd9c7be0c3 (tag)
tagging
> My advice for putting together that bug report is to create the
> simplest standalone example of the problem that is possible (e.g.,
> consiting of a CMakeLists.txt file that builds and installs a "hello,
> world" D application + D language source code for that application.
After one mornings
Hi again,
Problem solved by rebooting Windows and the samba share.
Thank you anyway!
Le 03/03/2017 à 15:43, Louis-Paul CORDIER a écrit :
Does not solve the issue here...
I'm using the latest cmake release 3.7.2
Your Z is a mapped network drive, am I right?
This behaviour is causing
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 51581b7074637074499ee9246428b787b6406096 (commit)
via
Does not solve the issue here...
I'm using the latest cmake release 3.7.2
Your Z is a mapped network drive, am I right?
This behaviour is causing find_package to fail as well.
Le 03/03/2017 à 15:23, Nils Gladitz a écrit :
On 03/03/2017 02:28 PM, Louis-Paul CORDIER wrote:
When I try to do a
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 4e8ffb952c41e19a5a4b24cdcbc504dba3f03f11 (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 e1adec32b8325fb731da084e99acd6070f5e39bf (commit)
from
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 b6030828f327802cc551995d3f4524b247bac2ca (commit)
via
On 03/03/2017 02:28 PM, Louis-Paul CORDIER wrote:
When I try to do a if(EXISTS "Z:\"), it never jump into the if statement.
Try if(EXISTS "Z:\\") or if(EXISTS "Z:/").
Either works for me.
if(EXISTS "Z:\") looks like it should have been a syntax error since the
backslash starts an escape
Hi,
I'm trying to use the cmake 'if' statement with the EXISTS parameter,
used for checking folder/file existence.
In my project, I have a library stored on a network samba folder. On my
Windows dev platform, I mapped a network drive (Windows 7 -> Computer ->
Map network drive) on this
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 c18462d8c53725c98268b3a91fda7c025cb67eaf (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 2b52c6cde5933d7e46b2d85788ba67b20069ab86 (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 305ef6a006de0fa6ae86752a3a1c96d2570a99f2 (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 ffba33ff51b6c0acfe3d16e5632d927d87c5d24b (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 2ccf879ab4efca38bb2918bfb4ba5946328f8bb1 (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 3e06cdc19bc6670e19dd3697f257f0b89e5cd3f7 (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 907a6e85862d9edb37232015994df48bc3d80c8d (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 79b017f23cb012d361c5e4478dcfa7bcc829 (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 24c0e229efd92392a877ba5c7c52d74fb9fdf689 (commit)
via
38 matches
Mail list logo