Hi,
I am trying to disable the warnings coming from an external dependency
we're referencing in our project. One of the warnings requires
specifying /ignore:4221 in the Project Properties - Librarian -
Command Line in order to suppress it.
I can't for the life of me figure out how to pass that
This is what happened:
- I couldn't just edit the wiki, I had to make an account.
- For making an account I had to fill up a 50 words bio .
- I had to retype the captcha 5 times because I wasn't sure if I arrived at
the 50 words or not.
- Then I have to confirm the email address.
- My account is
Well, sorry you found it tedious to go through those steps, but please
consider the flip side of the coin, too:
The wiki has actually been defaced/attacked by spammers in the past,
who have done some pretty silly things just to get the links to their
trash out there... So, the barriers to entry
Hello,
I am trying to add Boost library to my project using the CMakeLists.txt in
the follwing way:
set(BOOST_INCLUDEDIR C:/boost_1_57_0)set(BOOST_LIBRARYDIR
C:/boost_1_57_0/stage/lib)
find_package(Boost 1.57.0 COMPONENTS filesystem)
include_directories(${Boost_INCLUDE_DIRS})
Hi Daniel,
I had some trouble with this myself a while back. You may want to refer to the
Boost module documentation for some help:
http://www.cmake.org/cmake/help/v3.1/module/FindBoost.html
There are some additional flags you can set which will help CMake locate Boost
for you; I'm sorry I
Thank you Parag.
I realized that I was missing the following:
set(Boost_USE_STATIC_LIBS True)
And also I needed to set BOOST_ROOT instead of BOOST_INCLUDEDIR.
Regards,
Daniel
2015-02-20 17:20 GMT+00:00 Parag Chandra pa...@ionicsecurity.com:
Hi Daniel,
I had some trouble with this
Hi Clint,
I have another patch to tweak the error output a little bit. If codesign
fails it won't be possible to get the error message of codesign itself.
That is a little bit confusing because it just fails without an
understandable reason.
This patch will print the output of codesign if it
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 cf4630995c56e8a82110c142e81c2f352575cabe (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 b7351d8e14ea7cc05b0c5d45dae48a21aef298c1 (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 eebca92b95939f95b7e07c55c28f628344430a69 (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 c4c570f9cc7a7c5f22670793af887dfa5a6dd7de (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 4164c62dba16fc379e7a56e7a86c6ef21680144a (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15412
==
Reported By:Kiron
Assigned To:
On 02/19/2015 04:58 PM, Raffi Enficiaud wrote:
I just unset this variable before the call to the find_program,
and now it works good.
Yes, this is expected. If find_program sees that the variable is
already set then it assumes the value is correct. The idea is
that projects can prevent 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
via 67e9bacb4351e7526808d055348fbc5a85269f32 (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 37e53989fc45ec2f99bc987332c013bc910d6fb4 (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 fc716a5e14862935267dc71d70956a44a6954e1a (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 5195e57aaa313fe3d9f14143a6f212cdaea81ccd (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 051a565a7adf3c5a7e0dc02306a0f5368a74e212 (commit)
via
20150220)
+set(CMake_VERSION_PATCH 20150221)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
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 20f64bd2dadbfe740e76d627523adf2161a515f3 (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 244867369bcded571a9fe0b06ef2998a5728e368 (commit)
via
But I still get the CMake.GetPrerequisites test timing out.
I don't see that in:
https://open.cdash.org/buildSummary.php?buildid=3701966
You're right. For some reason it is not timing out. It just takes a really long
time. I wonder if my path is long. That test takes an order of magnitude
On Friday, February 20, 2015 12:07:55 PM A. Klitzing wrote:
Hi Clint,
I have another patch to tweak the error output a little bit. If codesign
fails it won't be possible to get the error message of codesign itself.
That is a little bit confusing because it just fails without an
On 02/19/2015 07:44 PM, Geoffrey Viola wrote:
The nightly build that I use does use the cmake_common.cmake script
to grab the latest code, build, test it, etc. Here's what my nightly
build results look like:
https://open.cdash.org/buildSummary.php?buildid=3701008.
Sorry, I mixed up your
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 3646f09c7144daafc0d75e96d35031b959b29300 (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 eb52b449c2006892e5d13a035ea3c9d31b1a602c (commit)
via
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15413
==
Reported By:Lekensteyn
Assigned To:
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 e69434fa257c42e39b96101c37c39e9178369573 (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 61f41f354b513b64040401a201fdeb834b38aa6e (commit)
via
30 matches
Mail list logo
