The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15308
==
Reported By:Xi Yang
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15309
==
Reported By:Robert Pollak
Assigned To:
On 12/14/2014 08:36 AM, Rolf Eike Beer wrote:
The idea behind this API in OpenBSD is: if you are looking for the pseudo
numbers you need to call srand_deterministic(), i.e. you must explicitely
state that you want the not really random random numbers. Everyone else will
get real random.
Brad King wrote:
On 12/14/2014 08:36 AM, Rolf Eike Beer wrote:
The idea behind this API in OpenBSD is: if you are looking for the pseudo
numbers you need to call srand_deterministic(), i.e. you must explicitely
state that you want the not really random random numbers. Everyone else
will
Looking at our own internal test suite usage of RANDOM_SEED leads to
the conclusion that we do not verify the sequences produced when
actually using RANDOM_SEED..
So, from our point of view, we don't really care about what effect
RANDOM_SEED has for our test suite. But I think we do still
Hi Dmitry,
I just tried to upgrade to 3.0r4 and it still defaults the Visual Project
setting of Language - C++ Language Standard to Default. I need to set it
to C++11 somehow, otherwise I get many errors that the C++11 code we are using
in our engine cannot compile. This will either need to
I have a project:
/Target A
- CMakeLists.txt
- /Target B
-- CMakeLists.txt
- /Target C
-- CMakeLists.txt
So, A is including B and C using add_subdirectory. However, A is
producing 2 targets, one of which is a library and I need to link B
and C against that library. How would I do that?
--
target_link_libraries( B A_product_name)
target_link_libraries( C A_product_name)
On Mon, Dec 15, 2014 at 12:34 AM, Petr Bena benap...@gmail.com wrote:
I have a project:
/Target A
- CMakeLists.txt
- /Target B
-- CMakeLists.txt
- /Target C
-- CMakeLists.txt
So, A is including B and C
Ok, one more question
How do I enforce run of ldconfig during `sudo make install` on linux?
The library doesn't load without it.
On Mon, Dec 15, 2014 at 9:37 AM, J Decker d3c...@gmail.com wrote:
target_link_libraries( B A_product_name)
target_link_libraries( C A_product_name)
On Mon, Dec
http://www.cmake.org/cmake/help/v3.0/command/add_custom_target.html
looks like all existing projects just do it by hand... it's safer if the
build script doesn't have it. (much like not making copying runtime
libraries easy)
On Mon, Dec 15, 2014 at 12:49 AM, Petr Bena benap...@gmail.com wrote:
Hello Robert,
I don't have a test-environment handy, but it seems like FindwxWidgets checks
for the vc_x64 library directory prefix, not for vc_amd64:
# /usr/share/cmake-3.0/Modules/FindwxWidgets.cmake:511:
if(MINGW)
set(WX_LIB_DIR_PREFIX gcc)
elseif(CMAKE_CL_64)
Hello,
I tried write_compiler_detection_header as in the example provided with VS2013
but i only get the following message: Unsupported compiler MSVC
Any suggestions?
Best Regards
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hello Johannes!
You wrote:
I don't have a test-environment handy, but it seems like FindwxWidgets checks
for the vc_x64 library directory prefix, not for vc_amd64:
# /usr/share/cmake-3.0/Modules/FindwxWidgets.cmake:511:
if(MINGW)
set(WX_LIB_DIR_PREFIX gcc)
[...] FindwxWidgets checks
for the vc_x64 library directory prefix, not for vc_amd64:
I have now filed http://www.cmake.org/Bug/view.php?id=15309 about this.
--Robert
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
I see that only GNU and Clang is currently supported (set(compilers GNU
Clang);)
Is that right and would MSVC be added to the final 3.1.0 version?
Thanks in advance
Best Regards
Am 15.12.2014 um 12:34 schrieb NoRulez noru...@me.com:
Hello,
I tried write_compiler_detection_header as in
On Mon, Dec 15, 2014 at 3:52 AM, Johannes Zarl johannes.z...@jku.at wrote:
Hello Robert,
I don't have a test-environment handy, but it seems like FindwxWidgets
checks
for the vc_x64 library directory prefix, not for vc_amd64:
# /usr/share/cmake-3.0/Modules/FindwxWidgets.cmake:511:
Hi,
Is it possible to set a compiler flags only if compiler is MinGW (that
means these flags wouldn't be set on MSVC).
if (WIN32) matches both compilers obviously. Thanks
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Very useful page for these types of questions:
http://www.cmake.org/Wiki/CMake_Useful_Variables
if (MINGW) should work.
Or if you want to go off the compiler id use: CMAKE_CXX_COMPILER_ID.
-Caleb
On Mon, Dec 15, 2014 at 11:16 AM, Petr Bena benap...@gmail.com wrote:
Hi,
Is it possible to
Hi,
Is it possible to set a compiler flags only if compiler is MinGW (that
means these flags wouldn't be set on MSVC).
to target specific compilers you can make use of CMAKE_CXX_COMPILER_ID.
In my projects I usually include compiler specific settings like this:
foreach(_base
This page from the documentation might help:
http://www.cmake.org/cmake/help/v3.1/manual/cmake-variables.7.html
One in particular that may be useful for you to test is
CMAKE_LANG_COMPILER_ID:
http://www.cmake.org/cmake/help/v3.1/variable/CMAKE_LANG_COMPILER_ID.html
Note that it does state
Why would we need specific support for each compiler? Couldn't the module use
check_cxx_source_compiles() etc. tests instead?
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of NoRulez [noru...@me.com]
Sent: Monday, December 15, 2014
On 12/15/2014 08:40 AM, NoRulez wrote:
I see that only GNU and Clang is currently supported
(set(compilers GNU Clang);)
Is that right and would MSVC be added to the final 3.1.0 version?
This was a mistake in the documentation that was updated here:
WCDH: Don't imply that MSVC is supported
On 12/15/2014 12:38 PM, Daniel Schepler wrote:
Why would we need specific support for each compiler?
One goal of the module is to avoid running dozens of compiler
introspection tests for every new build tree. Compiler vendors
document support for new language features in each release.
There is
Not supported in general or only in the rc/final 3.1.0?
Because it would be very helpful for Features which are supported for e.g. in
VS2010 to VS2014 and more.
Best Regards
Am 15.12.2014 um 18:49 schrieb Brad King brad.k...@kitware.com:
On 12/15/2014 08:40 AM, NoRulez wrote:
I see that
On 12/15/2014 04:07 PM, NoRulez wrote:
Not supported in general or only in the rc/final 3.1.0?
Support for MSVC was not included in the original contribution and
will not be included in the 3.1 release. We welcome contribution
of the MSVC support from anyone interested in providing it as new
I am a new bee in Cmake. I want to make a project with Cmake. The Project
lay out is given below.
deepak/
gales/
directory_1_of_header_files/
directory_2_of_header_files/
directory_3_of_header_files/
samples/
You can write the root cmake file in the samples directory then adding
project specific cmake file in the src directory.
You can also start by writing a single cmake file in the
src directory alone. Then move it to the samples directory, if the project
complexity increases
On Tue, Dec 16, 2014
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 b9e0babea92829e622eab9415ea64e43ec41bacf (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 526c34b240638bea90cce4162a95f0c8c7ea8a88 (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 ab09122717ff8138086cd46787f0badbba0f5669 (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 a815f790edb4e45aa4bc250bf0b4b89a945c470e (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 d033f0cc1e5fe673ef3a50e51712c1e7f8de07f0 (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 5c1b101320812d9c82025302215a753d50800678 (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 de3c9d8c5f3bdda60c0711e04238fd392c46a59f (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 c6aad8356f66067a17d7988bc039a86d37b12927 (commit)
via
35 matches
Mail list logo
