Brad,
I want to confirm that your patch below fixed the issue that I reported.
Thank you!
-kt
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Friday, February 05, 2016 7:32 AM
To: Thompson, KT
Cc: cmake@cmake.org; Stephen Kelly
Petr,
Thanks for the info. I'm working on getting the builds to work exactly like I
want for both native *nix and cross-compile Windows builds, so it's a learning
process. I do appreciate your info.
vadtecvad...@vadtec.net
On Thu, 04 Feb 2016 01:49:12 -0600 Petr Kmoch
If I specify an empty value for filename, I get the behavior of relative
path, and var turns into CMAKE_CURRENT_SOURCE_DIR. It seems like if I put
an empty file I should get back an empty output.
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
I have been successfully using CMake's GTEST_ADD_TESTS to run GTest
TEST and TEST_F blocks defined in a source file. However, I now need
to pass some arguments (filenames that I want CMake to produce
including things like ${CMAKE_SOURCE_DIR}) to the GTests, and it seems
like the way to do this is
Dear all,
do you know a best practice on how to specify compiler flags without knowing in
advance which compiler will be used?
Its about Fortran projects, where I e.g. want to explicitly enable the
preprocessor, or make all default real values 8 byte wide. This could be done
as such:
On 02/04/2016 04:00 PM, Thompson, KT wrote:
> If I run ‘make VERBOSE=1’ with CMake-3.4.3, I see the following command:
>
> cmake -E cmake_copy_f90_mod src/dir1/dir2/myf90file
> src/dir1/dir2/CMakeFiles/Lib_FC_f90sub.dir/myf90file.mod.stamp Intel
>
> but with CMake-3.5.0-rc1, I have this command
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 ea896482b563918c9d839577adab1ee926893bcd (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 ee1a481cf097d78e547e4af821767b3347c443d8 (commit)
via
Hi Brad,
Thanks for the quick response! :)
The changes to remove “refType” are quite safe. I see no big problems there.
The same for “buildSettings” as this attribute is empty for the “PBXProject”
section.
About “buildStyles”, as I see on the cmake code, it is used only to set
Ok, I've installed all options from the SDK
(https://dev.windows.com/en-us/downloads/windows-10-sdk)
but it doesn't solve the issue.
Is there something other to install?
What things does CMake require?
Best Regards
Roman
> Am 05.02.2016 um 14:54 schrieb Roman Wüger :
>
>
Hi,
tl;dr: I have problems generating .pbxproj files with cmake, related to
deprecated attributes on .pbxproj.
We are using cmake to generate and build Xcode projects. We need to generate
the schemes programatically, and to do so we are using
https://github.com/CocoaPods/Xcodeproj to generate
On 02/05/2016 09:23 AM, Arnau Quintana wrote:
> The problem is that the .pbxproj contains some attributes that seem to be
> deprecated. Specifically:
>
> * “refType" for the “PBXFileReference" isa
> * “buildSettings” and “buildStyles” for “PBXProject" isa
>
> Xcode is nice enough to open
On 02/05/2016 09:10 AM, Bartosz Kosiorek wrote:
> Finally I was able to finalize git bisect.
> Generally without regression time was: real3m44.070s
> first bad commit: [0c97d32f7a592a768d614c19b3fd48eab245a2c4]
> cmGlobalGenerator: Remove direct storage of target
> time increased to real
On 02/05/2016 11:35 AM, Arnau Quintana wrote:
> I do not know if these are related. Any thoughts?
Unfortunately I'm not familiar enough with Xcode to answer.
Hopefully someone else can answer.
> I am curious about what tests are you running. Could you
> please point me to the relevant tests?
Hello all,
I am a cmake newbie. Now I have two compiler that target MyTarget. The
first one is a modified cl.exe, and the other one is the clang-cl.exe.
Because they don't target x86/x64, both headers/libraries are supposed not
to be included/linked. Instead I just want to include/link
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 42416ba1798a81bd3d0e9aeb9919dc3e3de3c603 (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 b11b9d05dd1d9e77ac76f6b9b72c4f1face53418 (commit)
via
On 2/4/16, Brad King wrote:
> On 01/29/2016 03:16 PM, Eric Wing wrote:
>> I need more guidance here. I'm not connecting the dots.
>> My problem seems to be that the execute_process() in
>> CMakeDetermineCompilerId.cmake is trying to invoke the command:
>> 'swift
Hi Roman,
I can help with this. You should be good with VS 2015 and the Windows 10 SDK.
After you installed the SDK, did you get the same error message or a different
one?
From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of
Roman Wüger
Sent: Friday, February 5,
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 b3df88b4bb4c77291040e27ece6d384e3e58b55c (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 3748be6afa12f0f0d7d3b51ee44d7908e86a19bd (commit)
via
Hello,
Ive Installed Windows 10 Professional with VS2015 Update 1 and CMake 3.4.3.
When I run configure:
cmake -G "Visual Studio 14 Win64" -DCMAKE_SYSTEM_NAME:STRING=WindowsStore
-DCMAKE_SYSTEM_VERSION:STRING=10.0 ..\source
Then I became the following error message:
CMake Error
Hi.
Finally I was able to finalize git bisect.
Generally without regression time was: real 3m44.070s
first bad commit: [0c97d32f7a592a768d614c19b3fd48eab245a2c4]
cmGlobalGenerator: Remove direct storage of target
time increased to real6m36.929s (second clean run real6m12.635s)
On 02/04/2016 05:57 PM, Bartosz Kosiorek wrote:
> Unfortunately after building locally, the times are totally different (worse).
Check CMAKE_BUILD_TYPE in the CMakeCache.txt file of your CMake build
and make sure it is "Release". If not, just change it and run "make"
again to rebuild.
Thanks,
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 599f02d90301a61a10a9ef9273f0f6c1332242d3 (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 09bc2bc7260d7fcc1767da7de6e7b063628e03c3 (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 405dcbb37c9a442a92d5df52f6f6ecf387cd7cb7 (commit)
via
_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160205)
+set(CMake_VERSION_PATCH 20160206)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
28 matches
Mail list logo