Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Georgy Kirichenko <georgy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v4] Tarantool static build ability
Date: Wed, 29 Aug 2018 14:22:21 +0300	[thread overview]
Message-ID: <20180829112221.j7oehfqgwgmal74e@tkn_work_nb> (raw)
In-Reply-To: <61ed63cef516d36d6a18b02d476bdd680e8cf516.1535522175.git.georgy@tarantool.org>

Travis CI catched the following error:

-- Performing Test CURL_SUPPORTS_SSL
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
Z_LIBRARY
    linked by target "cmTC_a3bb9" in directory /tarantool/CMakeFiles/CMakeTmp
CMake Error: Internal CMake error, TryCompile configure of cmake failed
-- Performing Test CURL_SUPPORTS_SSL - Failed

https://travis-ci.org/tarantool/tarantool/jobs/422002672#L1008

On Wed, Aug 29, 2018 at 09:08:07AM +0300, Georgy Kirichenko wrote:
> A possibility to build tarantool with included library dependencies.
> Use the flag -DBUILD_STATIC=ON to build statically against curl, readline,
> ncurses, icu and z.
> Use the flag -DOPENSSL_USE_STATIC_LIBS=ON to build with static
> openssl
>
> Changes:
>   * Add FindOpenSSL.cmake because some distributions do not support the use of
>   openssl static libraries.
>   * Find libssl before curl because of build dependency.
>   * Catch all bundled libraries API and export then it in case of static
>   build.
>   * Rename crc32 internal functions to avoid a name clash with linked libraries.
>
> Notes:
>   * Bundled libyaml is not properly exported, use the system one.
>   * Dockerfile to build static with docker is included
>
> Fixes #3445
> ---
> Changes in v4:
>   - Add Z library to an openssl libraries list because of dependencies
>   - Update FinxOpenSSL module
>   - Minor fixes as per review by Alexander Turenko
>
> Changes in v3:
>   - Fixed comments as per review by Alexander Turenko
>
> Changes in v2:
>   - Fixed comments as per review by Alexander Turenko

  parent reply	other threads:[~2018-08-29 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  6:08 [tarantool-patches] " Georgy Kirichenko
2018-08-29 11:19 ` [tarantool-patches] " Alexander Turenko
2018-08-29 11:22 ` Alexander Turenko [this message]
2018-09-06 17:59 ` Kirill Yukhin
2018-09-07  7:30   ` [tarantool-patches] [PATCH] Fix libgomp linking for static build Kirill Yukhin
2018-09-07  9:06     ` [tarantool-patches] " Kirill Yukhin
2018-09-07  9:17   ` [tarantool-patches] " Kirill Yukhin
2018-09-07 17:10     ` [tarantool-patches] " Alexander Turenko
2018-09-10  7:05     ` Kirill Yukhin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180829112221.j7oehfqgwgmal74e@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v4] Tarantool static build ability' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox