[cmake-developers] Shared libraries

2018-08-09 Thread REIX, Tony 
Hi,


On AIX, when building MongoC 1.11, cmake 3.11.4 generates lib*.so files and 
lib*.a files which contain .o files.

On AIX, we should get libraries lib*.a containing the lib*.so file.

I've tried to use:

-DBUILD_SHARED_LIBS=ON  \
-DBUILD_STATIC_LIBS=OFF \
-DCMAKE_C_CREATE_SHARED_LIBRARY=ON  \
-DCMAKE_CXX_CREATE_SHARED_LIBRARY=ON
and I see that, for MariaDB, someone has tried with:

-DDISABLE_SHARED=OFF


None seems to work.


Which CMake variable should I use for asking CMAKE to generate shared libraries 
rather than static ones: lib*.a file containing .so files rather than .o files.


Thanks


Cordialement,

Tony Reix

tony.r...@atos.net

ATOS / Bull SAS
ATOS Expert
IBM Coop Architect & Technical Leader
Office : +33 (0) 4 76 29 72 67
1 rue de Provence - 38432 Échirolles - France
www.atos.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-developers

[cmake-developers] [ANNOUNCE] CMake 3.12.1 available for download

2018-08-09 Thread Robert Maynard 
We are pleased to announce that CMake 3.12.1 is now available for download.

Please use the latest release from our download page:
  https://cmake.org/download/

Thanks for your support!

-
Changes in 3.12.1 since 3.12.0:

Brad King (8):
  CSharp: Set CMAKE_CSharp_COMPILER_LOADED variable when language is enabled
  UseSWIG: Use CSharp language only if it is enabled
  Help: Add explicit _ROOT variable documentation
  Tests: Add case showing CMP0048 warning on injected project command
  project: Do not issue CMP0048 warnings on injected call
  CPack: Restore support for 0-valued version components
  FindCUDA/select_compute_arch: Restore two-component CUDA_VERSION
  CMake 3.12.1

Craig Scott (1):
  GoogleTest: Ensure policy settings allow use of IN_LIST

Dima Panov (1):
  FindTCL: Add support for version 8.7

Marc Chevrier (2):
  FindPython*: fix erroneous behavior on multiple 'find_package' calls
  UseSWIG: restore legacy behavior for SWIG_MODULE__EXTRA_FLAGS
-- 

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-developers

Re: [cmake-developers] Enabling SSL support by default when building CMake from source

2018-08-09 Thread Brad King 
On 08/09/2018 08:54 AM, Craig Scott wrote:
> or is it just that the logic hasn't been added to try to enable
> it by default if available?

Mostly that.

On Windows and macOS we already get SSL by default because curl
just uses the OS-provided APIs.  This issue occurs only when we
need to find OpenSSL.

Since commit v3.6.0-rc1~301^2 (Automatically use OpenSSL by default
on Linux and FreeBSD if available, 2016-02-26) we try to enable
SSL by default on Linux and FreeBSD.  Its commit message explains
why we didn't do that for other platforms (too easy to find an
OpenSSL library that is not compatible with the target compiler).
A sophisticated try_compile may be needed to determine whether
enabling it will compile and link properly.

-Brad
-- 

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-developers

Re: [cmake-developers] Enabling SSL support by default when building CMake from source

2018-08-09 Thread Nils Gladitz 
On Thu, Aug 9, 2018 at 2:54 PM Craig Scott  wrote:

> When building CMake from source with default options, you typically end up
> without SSL support, even if the necessary libraries (i.e. OpenSSL) are
> available. I've been bitten by that in my earlier days building CMake and
> I've seen others have a similar experience. Is there any reason why this is
> the default behavior, or is it just that the logic hasn't been added to try
> to enable it by default if available?
>

I remember this having changed to some degree here (~3.6):
https://gitlab.kitware.com/cmake/cmake/commit/190a5fdffd8104ad613854bdd563a0a11dd88f63

Nils
-- 

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-developers

[cmake-developers] Enabling SSL support by default when building CMake from source

2018-08-09 Thread Craig Scott 
When building CMake from source with default options, you typically end up
without SSL support, even if the necessary libraries (i.e. OpenSSL) are
available. I've been bitten by that in my earlier days building CMake and
I've seen others have a similar experience. Is there any reason why this is
the default behavior, or is it just that the logic hasn't been added to try
to enable it by default if available?

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

New book released: Professional CMake: A Practical Guide

-- 

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-developers