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 at
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/
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
de
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 :
>
>> On 12/15/2014 08:40 AM, NoRulez wrote:
>> I see that only GNU and Cla
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
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 suppo
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 5:
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__COMPILER_ID:
http://www.cmake.org/cmake/help/v3.1/variable/CMAKE_LANG_COMPILER_ID.html
Note that it does state it¹s no
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
${CMAKE_CXX_
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 wrote:
>
> Hi,
>
> Is it possible to set a compiler
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:
http://www.cmake.org/Wiki/CMake_FA
On Mon, Dec 15, 2014 at 3:52 AM, Johannes Zarl 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)
>
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 :
>
> Hello,
>
> I tried write_compiler_detection_header as in the exa
> [...] 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:
http://www.cmake.org/Wiki/CMake_
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)
> elseif(CMAK
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:
http://www.cmake.org/
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)
set(WX_LIB_D
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 wrote:
>
> Ok, one more qu
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 wrote:
> target_link_libraries( B A_product_name)
> target_link_libraries( C A_product_name)
>
>
> On Mon, Dec 15, 2014 at 12
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 wrote:
>
> 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
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?
--
Power
21 matches
Mail list logo