[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-128-ga894397153

[Kitware Robot via Cmake-commits]

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  a8943971539aeb0df60b136d07e9c820c8be6f5e (commit)
  from  5c8d821ecabb0fba28719000182f241b16d86b44 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a8943971539aeb0df60b136d07e9c820c8be6f5e
commit a8943971539aeb0df60b136d07e9c820c8be6f5e
Author: Kitware Robot 
AuthorDate: Sat Oct 26 00:01:09 2019 -0400
Commit: Kitware Robot 
CommitDate: Sat Oct 26 00:01:09 2019 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 05137c83f6..dd57b09e56 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 16)
-set(CMake_VERSION_PATCH 20191025)
+set(CMake_VERSION_PATCH 20191026)
 #set(CMake_VERSION_RC 0)
 set(CMake_VERSION_IS_DIRTY 0)
 

---

Summary of changes:
 Source/CMakeVersion.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] graphviz missing dependencies when target spans multiple subfolders

[Craig Scott]

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:
>
> ModuleA/CMakeLists.txt:
> 
> add_library(moduleA STATIC "")
>
> add_subdirectory(sub1)
> add_subdirectory(sub2)
> --
>
> sub1/CMakeLists.txt
> --
> target_include_directories(moduleA PUBLIC .)
> target_sources(moduleA
>PRIVATE
> src1.cpp
> src2.cpp
> )
>
> target_link_libraries(moduleA
> PRIVATE
> Qt5::Widgets
> Qt5::Qml
> moduleB
> )
>
> sub2/CMakeLists.txt
> --
> target_include_directories(moduleA PUBLIC .)
> target_sources(moduleA
> PRIVATE
> src1.cpp
> src2.cpp
> )
>
> target_link_libraries(moduleA
> PRIVATE
> Qt5::Quick
> moduleC
> )
> ---
>
> I run cmake --graphviz=project.dot .
>
> From this, two of the files that comes out are project.dot.moduleA and
> project.dot.moduleA.dependers.
>
> The former is only this:
> digraph "GG" {
> node [
>   fontsize = "12"
> ];
> "node190" [ label="moduleA" shape="diamond"];
> }
>
> There is no mention of the Qt5 or other module dependencies.
>
>
> Other modules with dependencies but without the hierarchy introduced with
> add_subdirectory() seem to be just fine and include their respective
> dependencies in their project.dot.moduleX files.
>
> Is this a bug or am I misusing add_subdirectory() here?  With the
> exception of the graphviz output, everything builds and runs as expected
> with my setup.
>

The structure of your project looks fine, it's probably a bug in the
graphviz handling. There has been a bit of activity around improving that
recently, so it's possible that it has either been broken recently or has
been fixed on master already. Can you please try a few earlier CMake
versions and see if the problem has always been there? If it looks like a
recently introduced regression, please also try a nightly build of the
latest master (or build CMake from sources yourself if you're happy to do
that). If the bug is still there on master, I suggest you file a bug report.

-- 
Craig Scott
Melbourne, Australia
https://crascit.com

Get the hand-book for every CMake user: Professional CMake: A Practical
Guide 
Consulting services (CMake, C++, build/release processes):
https://crascit.com/services
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Is there a "package" equivalent for CMAKE_SKIP_INSTALL_ALL_DEPENDENCY

[Craig Scott]

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.

-- 
Craig Scott
Melbourne, Australia
https://crascit.com

Get the hand-book for every CMake user: Professional CMake: A Practical
Guide 
Consulting services (CMake, C++, build/release processes):
https://crascit.com/services
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Is there a "package" equivalent for CMAKE_SKIP_INSTALL_ALL_DEPENDENCY

[Scott Bloom]

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 offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] configuring FCGI2 -- check typedefs in include files?

[Kent Williams]

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 */
   /* #undef HAVE_FPOS */

This is definitely defined, but the closest module that's applicable is 
CheckTypeSize, and this doesn't seem to work:

    set(CMAKE_EXTRA_INCLUDE_FILES stdio.h)
    CHECK_TYPE_SIZE("fpos_t" HAVE_FPOS)
    set(CMAKE_EXTRA_INCLUDE_FILES)

And this one, I wouldn't be able to handle without writing a custom test.
    /* Define if va_arg(arg, long double) crashes the compiler */
    /* #undef HAVE_VA_ARG_LONG_DOUBLE_BUG */

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] graphviz missing dependencies when target spans multiple subfolders

[Rich von Lehe]

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_library(moduleA STATIC "")

add_subdirectory(sub1)
add_subdirectory(sub2)
--

sub1/CMakeLists.txt
--
target_include_directories(moduleA PUBLIC .)
target_sources(moduleA
   PRIVATE
src1.cpp
src2.cpp
)

target_link_libraries(moduleA
PRIVATE
Qt5::Widgets
Qt5::Qml
moduleB
)

sub2/CMakeLists.txt
--
target_include_directories(moduleA PUBLIC .)
target_sources(moduleA
PRIVATE
src1.cpp
src2.cpp
)

target_link_libraries(moduleA
PRIVATE
Qt5::Quick
moduleC
)
---

I run cmake --graphviz=project.dot .

>From this, two of the files that comes out are project.dot.moduleA and
project.dot.moduleA.dependers.

The former is only this:
digraph "GG" {
node [
  fontsize = "12"
];
"node190" [ label="moduleA" shape="diamond"];
}

There is no mention of the Qt5 or other module dependencies.


Other modules with dependencies but without the hierarchy introduced with
add_subdirectory() seem to be just fine and include their respective
dependencies in their project.dot.moduleX files.

Is this a bug or am I misusing add_subdirectory() here?  With the exception
of the graphviz output, everything builds and runs as expected with my
setup.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc2-127-g5c8d821eca

[Kitware Robot via Cmake-commits]

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  5c8d821ecabb0fba28719000182f241b16d86b44 (commit)
   via  f0005dacdeb04be2d335af938ff76d9e3ad5 (commit)
  from  5a3f539cd50621298d15df639c29a9c09aace443 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5c8d821ecabb0fba28719000182f241b16d86b44
commit 5c8d821ecabb0fba28719000182f241b16d86b44
Merge: 5a3f539cd5 f0005dacde
Author: Brad King 
AuthorDate: Fri Oct 25 13:37:39 2019 +
Commit: Kitware Robot 
CommitDate: Fri Oct 25 09:37:49 2019 -0400

Merge topic 'xcode-scheme-env'

f0005dacde Xcode: Add CMAKE_XCODE_SCHEME_ENVIRONMENT variable

Acked-by: Kitware Robot 
Merge-request: !3933


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f0005dacdeb04be2d335af938ff76d9e3ad5
commit f0005dacdeb04be2d335af938ff76d9e3ad5
Author: Felix Heidrich 
AuthorDate: Thu Oct 17 12:45:20 2019 +0200
Commit: Brad King 
CommitDate: Thu Oct 24 11:24:34 2019 -0400

Xcode: Add CMAKE_XCODE_SCHEME_ENVIRONMENT variable

Initialize the `XCODE_SCHEME_ENVIRONMENT` target property.

This was left out of commit 6b7f1e1db0 (Xcode: Add variables and
properties to configure schemes, 2018-07-29, v3.13.0-rc1~243^2).

diff --git a/Help/manual/cmake-variables.7.rst 
b/Help/manual/cmake-variables.7.rst
index cad0df6daf..b5415b79dd 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -241,6 +241,7 @@ Variables that Change Behavior
/variable/CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER
/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS
/variable/CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE
+   /variable/CMAKE_XCODE_SCHEME_ENVIRONMENT
/variable/CMAKE_XCODE_SCHEME_GUARD_MALLOC
/variable/CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP
/variable/CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES
diff --git a/Help/release/dev/xcode-scheme-env.rst 
b/Help/release/dev/xcode-scheme-env.rst
new file mode 100644
index 00..238cb618fa
--- /dev/null
+++ b/Help/release/dev/xcode-scheme-env.rst
@@ -0,0 +1,5 @@
+xcode-scheme-env
+
+
+* The :variable:`CMAKE_XCODE_SCHEME_ENVIRONMENT` variable was added
+  to initialize the :prop_tgt:`XCODE_SCHEME_ENVIRONMENT` target property.
diff --git a/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst 
b/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst
new file mode 100644
index 00..4832659ce7
--- /dev/null
+++ b/Help/variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst
@@ -0,0 +1,15 @@
+CMAKE_XCODE_SCHEME_ENVIRONMENT
+--
+
+Specify environment variables that should be added to the Arguments
+section of the generated Xcode scheme.
+
+If set to a list of environment variables and values of the form
+``MYVAR=value`` those environment variables will be added to the
+scheme.
+
+This variable initializes the :prop_tgt:`XCODE_SCHEME_ENVIRONMENT`
+property on all targets.
+
+Please refer to the :prop_tgt:`XCODE_GENERATE_SCHEME` target property
+documentation to see all Xcode schema related properties.
diff --git a/Source/cmTarget.cxx b/Source/cmTarget.cxx
index 99c16f2374..472287f0e0 100644
--- a/Source/cmTarget.cxx
+++ b/Source/cmTarget.cxx
@@ -380,6 +380,7 @@ cmTarget::cmTarget(std::string const& name, 
cmStateEnums::TargetType type,
   initProp("XCODE_SCHEME_MALLOC_STACK");
   initProp("XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE");
   initProp("XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS");
+  initProp("XCODE_SCHEME_ENVIRONMENT");
 }
 #endif
   }

---

Summary of changes:
 Help/manual/cmake-variables.7.rst  | 1 +
 Help/release/dev/xcode-scheme-env.rst  | 5 +
 .../CMAKE_XCODE_SCHEME_ENVIRONMENT.rst}| 7 +--
 Source/cmTarget.cxx| 1 +
 4 files changed, 12 insertions(+), 2 deletions(-)
 create mode 100644 Help/release/dev/xcode-scheme-env.rst
 copy Help/{prop_tgt/XCODE_SCHEME_ENVIRONMENT.rst => 
variable/CMAKE_XCODE_SCHEME_ENVIRONMENT.rst} (70%)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

[Eric Noulard]

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 which supports this flag but the 
> CHECK_CXX_COMPILER_FLAG
> directive incorrectly determines that this flag is not supported.
>

You get appropriate answers to your initial question.

I'll add an alternative to your hand-crafted way to get sanitizers working.

I'm using: https://github.com/arsenm/sanitizers-cmake
and I find it easy to use and convenient when compiling with either clang
or gcc.


-- 
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CHECK_CXX_COMPILER_FLAG doesn't give correct result for -fsanitize=address

[Marc CHEVRIER]

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, use preferably the variable 
CMAKE_REQUIRED_LINK_OPTIONS.

Le 24 oct. 2019 à 22:42 +0200, Michael Ellery , a écrit :
> I’ve dealt with that using something like this:
>
> set (_saved_CRL ${CMAKE_REQUIRED_LIBRARIES})
> set (CMAKE_REQUIRED_LIBRARIES “-fsanitize=address;asan")
> check_cxx_compiler_flag (-fsanitize=address COMPILER_SUPPORTS_SAN)
> set (CMAKE_REQUIRED_LIBRARIES ${_saved_CRL})
>
> the second item in CMAKE_REQUIRED_LIBRARIES is only needed when using gcc 
> which also requires a -lasan when linking (clang does not need this)
>
> > On Oct 24, 2019, at 12:47 PM, Turner, Adrian Keith via CMake 
> >  wrote:
> >
> > 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 which supports this flag but the 
> > CHECK_CXX_COMPILER_FLAG directive incorrectly determines that this flag is 
> > not supported.
> >
> > To test this I tried compiling the following program:
> > int main() {};
> >
> > This compiled with the following commands:
> > > g++ -fsanitize=address -c test.cpp
> > > g++ -fsanitize=address test.o -o test.exe
> >
> > And fails with the same error message as CHECK_CXX_COMPILER_FLAG when I 
> > compile with:
> > > g++ -fsanitize=address -c test.cpp
> > > g++ test.o -o test.exe
> >
> > producing the following message:
> > Undefined symbols for architecture x86_64:
> > "___asan_init", referenced from:
> > __GLOBAL__sub_I_00099_0_test.cpp in test.o
> > "___asan_version_mismatch_check_v8", referenced from:
> > __GLOBAL__sub_I_00099_0_test.cpp in test.o
> > ld: symbol(s) not found for architecture x86_64
> > collect2: error: ld returned 1 exit status
> >
> > It seems that CHECK_CXX_COMPILER_FLAG doesn't add the flag to the linking 
> > command when it tests compilation. Is this a bug with 
> > CHECK_CXX_COMPILER_FLAG or is there something I'm missing?
> >
> > Many thanks
> > Adrian Turner
> >
> >
> > --
> >
> > Powered by www.kitware.com
> >
> > Please keep messages on-topic and check the CMake FAQ at: 
> > http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Kitware offers various services to support the CMake community. For more 
> > information on each offering, please visit:
> >
> > CMake Support: http://cmake.org/cmake/help/support.html
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html
> > CMake Training Courses: http://cmake.org/cmake/help/training.html
> >
> > Visit other Kitware open-source projects at 
> > http://www.kitware.com/opensource/opensource.html
> >
> > Follow this link to subscribe/unsubscribe:
> > https://cmake.org/mailman/listinfo/cmake
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Alternative locations for boost in cmake

[Mahmood Naderan via CMake]

>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.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] [DKIM: Failed] Re: Alternative locations for boost in cmake

[Mahmood Naderan via CMake]

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".
 
Cheers,
 Marcel Loose.
 

  -- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Alternative locations for boost in cmake

[Mateusz Loskot]

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 is happening

In some situations (environment, toolset, Boost build layout, etc.)
FindBoost.cmake,
which by the way is a **guesser** not a rock solid configuration file
like pkg-config that never fails,
may need some extra hints.
Here is copy of suggestions from project I maintain
https://github.com/boostorg/gil/blob/develop/CONTRIBUTING.md#using-cmake

```
TIP: If CMake is failing to find Boost libraries, especially built
with --layout=versioned, you can try a few hacks:

-DBoost_ARCHITECTURE=-x64 to help CMake find Boost 1.66 and above add
an architecture tag to the library file names in versioned build The
option added in CMake 3.13.0.

-DBoost_COMPILER=-gcc5 or -DBoost_COMPILER=-vc141 to help CMake
earlier than 3.13 match your compiler with toolset used in the Boost
library file names (i.e. libboost_unit_test_framework-gcc5-mt-x64-1_69
and not -gcc55-). Fixed in CMake 3.13.0.

if CMake is still failing to find Boost, you may try -DBoost_DEBUG=ON
to get detailed diagnostics output from FindBoost.cmake module.
```

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] [DKIM: Failed] Re: Alternative locations for boost in cmake

[Marcel Loose]

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 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/users/mnaderan/boost_1_65_1/build/lib/
> -DBoost_ADDITIONAL_VERSIONS=1.65.1 ..
> -- The C compiler identification is GNU 4.8.5
> -- The CXX compiler identification is GNU 4.8.5
> -- Check for working C compiler: /bin/cc
> -- Check for working C compiler: /bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /bin/c++
> -- Check for working CXX compiler: /bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE
> -- Found CUDA: /usr/local/cuda-10.0 (found suitable version "10.0",
> minimum required is "7.5")
> -- Could NOT find Boost
> CMake Error at
> /storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137
> (message):
>   Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem timer
>   chrono) (Required is at least version "1.58")
> Call Stack (most recent call first):
>  
> /storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378
> (_FPHSA_FAILURE_MESSAGE)
>  
> /storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindBoost.cmake:2161
> (find_package_handle_standard_args)
>   cmake/FindBoost.cmake:6 (FIND_PACKAGE)
>   CMakeLists.txt:47 (include)
>
>
> -- Configuring incomplete, errors occurred!
>
>
>
> Regards,
> Mahmood
>
>
> On Thursday, October 24, 2019, 10:52:37 PM GMT+3:30, Mateusz Loskot
>  wrote:
>
>
> You are using very old CMake 3.9 which has no idea about Boost 1.65
> https://github.com/Kitware/CMake/blob/v3.9.0/Modules/FindBoost.cmake#L769
>
> Rule #1: Use latest version of CMake, ALWAYS!
>
> There is absolutely no reason or excuse to not to use the latest as
> there are
> - deb packages available https://apt.kitware.com/
> - generic installer for any Linux and Windows
>
> Updating CMake is easy-peasy for us lazy programmers with a bit of
> scripting:
> https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.sh
> https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.ps1
>
>
>
> Best regards,
> -- 
> Mateusz Loskot, http://mateusz.loskot.net
> -- 
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For
> more information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>
<>-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Alternative locations for boost in cmake

[Eric Noulard]

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=/storage/users/mnaderan/boost_1_65_1/build/include/
> -DBoost_LIBRARY_DIRS=/storage/users/mnaderan/boost_1_65_1/build/lib/
> -DBoost_ADDITIONAL_VERSIONS=1.65.1 ..
>


could you try:
$ cmake -DBoost_NO_SYSTEM_PATHS=ON
-DBOOST_ROOT=/storage/users/mnaderan/boost_1_65_1
-DBoost_ADDITIONAL_VERSIONS=1.65.1

you have a "case discrepancy" between:
BOOST_INCLUDE_DIR
and
Boost_LIBRARY_DIRS

and the error says:

"missing: Boost_INCLUDE_DIR"

FindBoost should be case tolerant for backward compat' issue but may be
this does not work when specifying hint var in mixed case (wild guess).

-- 
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] Alternative locations for boost in cmake

[Mahmood Naderan via CMake]

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/users/mnaderan/boost_1_65_1/build/lib/ 
-DBoost_ADDITIONAL_VERSIONS=1.65.1 ..
-- The C compiler identification is GNU 4.8.5
-- The CXX compiler identification is GNU 4.8.5
-- Check for working C compiler: /bin/cc
-- Check for working C compiler: /bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /bin/c++
-- Check for working CXX compiler: /bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found CUDA: /usr/local/cuda-10.0 (found suitable version "10.0", minimum 
required is "7.5")
-- Could NOT find Boost
CMake Error at 
/storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137
 (message):
  Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem timer
  chrono) (Required is at least version "1.58")
Call Stack (most recent call first):
  
/storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378
 (_FPHSA_FAILURE_MESSAGE)
  
/storage/users/mnaderan/tools/cmake-3.15.4/share/cmake-3.15/Modules/FindBoost.cmake:2161
 (find_package_handle_standard_args)
  cmake/FindBoost.cmake:6 (FIND_PACKAGE)
  CMakeLists.txt:47 (include)


-- Configuring incomplete, errors occurred!



Regards,
Mahmood 

On Thursday, October 24, 2019, 10:52:37 PM GMT+3:30, Mateusz Loskot 
 wrote:  
 
 You are using very old CMake 3.9 which has no idea about Boost 1.65
https://github.com/Kitware/CMake/blob/v3.9.0/Modules/FindBoost.cmake#L769

Rule #1: Use latest version of CMake, ALWAYS!

There is absolutely no reason or excuse to not to use the latest as there are
- deb packages available https://apt.kitware.com/
- generic installer for any Linux and Windows

Updating CMake is easy-peasy for us lazy programmers with a bit of scripting:
https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.sh
https://github.com/mloskot/wsl-config/blob/master/scripts/install-cmake-latest.ps1

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake
  -- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake