Thanks for your help. I've managed to get past the original problem by
editing FindBoost so that it checks for version 1.62. But I'm done yet!
Now I'm getting
compiler is AppleClang
compiler is AppleClang
[
/Applications/CMake.app/Contents/share/cmake-3.6/Modules/FindBoost.cmake:960
]
_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20161101)
+set(CMake_VERSION_PATCH 20161102)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
I have got many compliant that cmake support is not work with even the new
Android Studio, but it is really works for me.
I try ldd on cmake which Android SDK provided, all the so is resolved
correct, which break before.
So, I can imagine that maybe something related to my host environment , I
I have got many compliant that cmake support is not work with even the new
Android Studio, but it is really works for me.
I try ldd on cmake which Android SDK provided, all the so is resolved
correct, which break before.
So, I can imagine that maybe something related to my host environment , I
I have a project that I am configuring with Visual Studio 12 2013 Win64 and
Intel Fortran v16/v17. I have executables where there is both a .cpp file
and a .f90 file.
The .f90 file is not compiled when I compile the solution. If I use NMake
Makefiles everything compiles, links and executes just
I am running into an error
"Cannot generate a sage runtime search path for target because files
in some directories may conflict with libraries in implicit directories."
I understand from the error message why this is happening, but I'm not
certain how to get around it. In my CMakeLists.txt
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 713424ad207aa0f5e01f8c16b2ee1c442a91893a (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 64f718b310bbf299959b5b91949ade424e68ee1b (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 23378e88aca447aacce995fb6433cb25ba958c9a (commit)
via
It's my experience which maybe help.
I love Android Studio for its jetbrains style coding experience, but
with some bad style I don't like, like so frequency update and so many
experiment feature which sometimes is a good part like CMake support!
I just love coding and focus my project, but the
It's my experience which maybe help.
I love Android Studio for its jetbrains style coding experience, but
with some bad style I don't like, like so frequency update and so many
experiment feature which sometimes is a good part like CMake support!
I just love coding and focus my project, but the
My Android Studio Version Info:
Android Studio 2.2.1
Build #AI-145.3330264, built on October 6, 2016
May be the more import part is cmake version, I have two which all works:
~/Android/Sdk/cmake/3.6.3155560
~/Android/Sdk/cmake/3.6.3133135
hope this will be help:)
2016-10-31 22:13 GMT+08:00
My Android Studio Version Info:
Android Studio 2.2.1
Build #AI-145.3330264, built on October 6, 2016
May be the more import part is cmake version, I have two which all works:
~/Android/Sdk/cmake/3.6.3155560
~/Android/Sdk/cmake/3.6.3133135
hope this will be help:)
2016-10-31 22:13 GMT+08:00
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 e0af67b4fc05970cea3007f0ae4b97d5e3f512d4 (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 2fb83cc8710898e1fc802b68c9d55c456913719a (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 c88a078d690f72caea53b0723e8393b83f1b0b6f (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 ee0ce4c1dc907edd93716ff21b631c544680dca2 (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 bbfdde3378281d2764025aef0ee965b1806397ae (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 2b40bc240e51585f5184d057146d2e4da2fbed84 (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 97599787929fd197241dc3e4adcbf852bdf9f76d (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 3a0b88c121e39bf66e55c5e0e5f126fd0290ab4f (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 15da528a4f90e497d8ecd3592e0c19e6aed4307f (commit)
via
Florent, I had the same thoughts. It seems that the CMake generate +
build step happen silently as a prerequisite step when doing the
'gradle build' command somewhere. It makes it appear as if CMake is
not running at all, but instead the Java piece of the build is just
taking forever.
Really I
Florent, I had the same thoughts. It seems that the CMake generate +
build step happen silently as a prerequisite step when doing the
'gradle build' command somewhere. It makes it appear as if CMake is
not running at all, but instead the Java piece of the build is just
taking forever.
Really I
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 95f5bf3a71a6fdb1e516e1a6e5a0cadf968337f3 (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 77413bc5db8884f36fe7c6e162507ca5a0fa8fee (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 4c7de5d3940cdf7b648d89642968c95168949182 (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 1d3c41f925db306c60c390be89e32ddcfc81d62b (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 b8c5258b005f5dd677dc324164dbda1be4e403db (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 9c6cf7fcac1f4f23ec21aeb322026d4f422760cc (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 01567fd74f1426ebab2499e5e08d33eff5435f99 (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 fa4b2e7dc3293510427fa9f9fd96c98209ebfea5 (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 ba28e0405e4a41158395323ace1dd0075934233e (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 505f56dc91a94446b907620881f9156c9a9dfc92 (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 e27716bd420679e2958602f43a21be26eb94ffcb (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 357305953600b0de49f0373888c8fe5eb1e7eef4 (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 9ceef25ee2ebf6315e4c13dfc7102850c2807228 (commit)
via
On 10/31/2016 02:26 PM, Gregor Jasny via cmake-developers wrote:
> I wonder what's the recommended workflow for CMake developers with
> commit access to stage? I'd like to use feature branches in gitlab but
> wonder how those are best merged into 'next'?
We can review in GitLab first and once
On 10/30/2016 12:01 AM, Craig Scott wrote:
> Looking at the latest CMake docs for the LINK_FLAGS and STATIC_LIBRARY_FLAGS
> target properties, neither mentions support for generator expressions.
> Is it just a case of the linker properties haven't had their documentation
> updated or do they not
39 matches
Mail list logo
