On Sat, Oct 26, 2019 at 9:11 AM Rich von Lehe wrote:
> I am using CMake 3.15.1. Having found out about some of the changes with
> 3.13, I've started to take advantage of using 'add_subdirectory()' in
> certain cases when a module is large and spans multiple source folders.
>
> For instance:
>
>
On Sat, Oct 26, 2019 at 10:39 AM Scott Bloom wrote:
> I’m looking for an equivalent to CMAKE_SKIP_INSTALL_ALL_DEPENDENCY for
> packages, so when I do a make package, it doesn’t build all first.
>
>
>
> Does one exist?
>
You can just invoke cpack directly instead of doing a make package.
--
Cra
I'm looking for an equivalent to CMAKE_SKIP_INSTALL_ALL_DEPENDENCY for
packages, so when I do a make package, it doesn't build all first.
Does one exist?
Scott
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
There are some things I'm trying to do in setting up a config file for
the FCGI2 library:
https://github.com/FastCGI-Archives/fcgi2.git
And in going from an autoconf configuration to a CMake configuration
there are some stumpers:
/* Define if the fpos_t typedef is in stdio.h */
/* #unde
I am using CMake 3.15.1. Having found out about some of the changes with
3.13, I've started to take advantage of using 'add_subdirectory()' in
certain cases when a module is large and spans multiple source folders.
For instance:
ModuleA/CMakeLists.txt:
add_li
Le jeu. 24 oct. 2019 à 22:32, Turner, Adrian Keith via CMake <
cmake@cmake.org> a écrit :
> Hi CMake Mailing List,
>
>
> I am using the CHECK_CXX_COMPILER_FLAG directive in a CMake file to
> detect whether the compiler uses the "-fsanitize=address" compiler flag.
> I'm using the g++ 7.3.0 compiler
This is the expected behaviour.
As you already discovered, it is possible to control the compilation and link
steps with variables as described in
https://cmake.org/cmake/help/latest/module/CheckCXXSourceCompiles.html#module:CheckCXXSourceCompiles.
To specify, in a more clean way, link options,
>you have a "case discrepancy" between:
>BOOST_INCLUDE_DIR
>and>Boost_LIBRARY_DIRS
Yes. Thank you
Boost_LIBRARY_DIRandBoost_INCLUDE_DIR
Are correct. The cmake is now fine.
Regards,
Mahmood
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www
Thank you. In addition to that, I have to write -DBoost_INCLUDE_DIR and not
-DBOOST_INCLUDE_DIR
It is not fine.
Regards,
Mahmood
On Friday, October 25, 2019, 11:54:43 AM GMT+3:30, Marcel Loose
wrote:
Hi Mahmood,
I think that "-DBoost_LIBRARY_DIRS" should be "-DBoost_LIBRARY_DIR".
On Fri, 25 Oct 2019 at 09:54, Mahmood Naderan wrote:
>
> Even with the latest 3.15.4, I get the same error
>
> Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem timer
> chrono) (Required is at least version "1.58")
You can try `-DBoost_DEBUG=ON that may give more clues what i
Hi Mahmood,
I think that "-DBoost_LIBRARY_DIRS" should be "-DBoost_LIBRARY_DIR".
Cheers,
Marcel Loose.
On 25/10/2019 09:54, Mahmood Naderan via CMake wrote:
> Even with the latest 3.15.4, I get the same error
>
>
> $ cmake --version
> cmake version 3.15.4
>
> CMake suite maintained and supported
Le ven. 25 oct. 2019 à 09:55, Mahmood Naderan via CMake a
écrit :
> Even with the latest 3.15.4, I get the same error
>
>
> $ cmake --version
> cmake version 3.15.4
>
> CMake suite maintained and supported by Kitware (kitware.com/cmake).
> $ cmake -DBoost_NO_SYSTEM_PATHS=ON
> -DBOOST_INCLUDE_DIR=
Even with the latest 3.15.4, I get the same error
$ cmake --version
cmake version 3.15.4
CMake suite maintained and supported by Kitware (kitware.com/cmake).
$ cmake -DBoost_NO_SYSTEM_PATHS=ON
-DBOOST_INCLUDE_DIR=/storage/users/mnaderan/boost_1_65_1/build/include/
-DBoost_LIBRARY_DIRS=/storage/
13 matches
Mail list logo