Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <estetus@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [v2][PATCH 2/5] build/ninja: create target with cli binary only once
Date: Wed, 15 Jun 2022 12:10:55 +0300	[thread overview]
Message-ID: <YqmiH7dkP8qTH9U/@root> (raw)
In-Reply-To: <f4132cb3d87e203c57049672e644757f5667dea1.1654175362.git.sergeyb@tarantool.org>

Hi, Sergey!

Thanks for the patch!

LGTM, except a few nits below.

On 02.06.22, Sergey Bronnikov via Tarantool-patches wrote:
> CMakeLists defines target for cli binary two times (for static and
> shared build type) with the same output names. CMake generates two
> targets with same names and it breaks Ninja:
> 
> ninja: Entering directory `build/'
> ninja: error: build.ninja:1656: multiple rules generate src/luajit [-w
> dupbuild=err]
> 
> Patch adds variables required for different build types and create

Typo? s/create/creates/

> target for cli binary only once to avoid conflict.
> ---
>  src/CMakeLists.txt | 40 ++++++++++++++++------------------------
>  1 file changed, 16 insertions(+), 24 deletions(-)
> 
> diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
> index 8b651c5a..104ce999 100644
> --- a/src/CMakeLists.txt
> +++ b/src/CMakeLists.txt
> @@ -313,40 +313,32 @@ target_link_libraries(libluajit_shared ${TARGET_LIBS})
>  
>  # Compiling and linking CLIs.
>  

<snipped>

>  if(NOT BUILDMODE STREQUAL "dynamic")
>    set(LIBLUAJIT_STATIC_DEPS libluajit_static)
>    set(LUAJIT_DEPS luajit_static)
> +  set(LUAJIT_BIN luajit_static)
> +  set(LUAJIT_LIB libluajit_static)
>  endif()
>  if(NOT BUILDMODE STREQUAL "static")
>    set(LIBLUAJIT_SHARED_DEPS libluajit_shared)
>    set(LUAJIT_DEPS luajit_shared)
> +  set(LUAJIT_BIN luajit_shared)
> +  set(LUAJIT_LIB libluajit_shared)
>  endif()
>  set(LIBLUAJIT_DEPS ${LIBLUAJIT_STATIC_DEPS} ${LIBLUAJIT_SHARED_DEPS})

Nit: Looks like the LUAJIT_DEPS variable duplicates work of
LUAJIT_BIN variable now.

>  
> +add_executable(${LUAJIT_BIN} EXCLUDE_FROM_ALL ${CLI_SOURCES})
> +set_target_properties(luajit_shared PROPERTIES
> +  OUTPUT_NAME "${LUAJIT_CLI_NAME}"
> +  COMPILE_FLAGS "${TARGET_C_FLAGS}"
> +  LINK_FLAGS "${TARGET_BIN_FLAGS}"
> +  RUNTIME_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
> +)
> +target_include_directories(${LUAJIT_BIN} PRIVATE
> +  ${CMAKE_CURRENT_BINARY_DIR}
> +)
> +target_link_libraries(${LUAJIT_BIN} ${LUAJIT_LIB} ${TARGET_LIBS})
> +
>  # XXX: The variable is used in testing, so PARENT_SCOPE option
>  # is obligatory.
>  set(LUAJIT_BINARY $<TARGET_FILE:${LUAJIT_DEPS}> PARENT_SCOPE)
> -- 
> 2.25.1
> 

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2022-06-15  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 13:22 [Tarantool-patches] [v2][PATCH 0/5] Support building with Ninja Sergey Bronnikov via Tarantool-patches
2022-06-02 13:22 ` [Tarantool-patches] [v2][PATCH 1/5] build/ninja: refactoring Sergey Bronnikov via Tarantool-patches
2022-06-15  8:56   ` Sergey Kaplun via Tarantool-patches
2022-06-02 13:22 ` [Tarantool-patches] [v2][PATCH 2/5] build/ninja: create target with cli binary only once Sergey Bronnikov via Tarantool-patches
2022-06-15  9:10   ` Sergey Kaplun via Tarantool-patches [this message]
2022-06-15 16:03     ` Sergey Bronnikov via Tarantool-patches
2022-06-02 13:22 ` [Tarantool-patches] [v2][PATCH 3/5] build/ninja: rename default target Sergey Bronnikov via Tarantool-patches
2022-06-15  9:11   ` Sergey Kaplun via Tarantool-patches
2022-06-02 13:22 ` [Tarantool-patches] [v2][PATCH 4/5] build/ninja: create file lists outside of cmake commands Sergey Bronnikov via Tarantool-patches
2022-06-15  8:48   ` Igor Munkin via Tarantool-patches
2022-06-15  9:19   ` Sergey Kaplun via Tarantool-patches
2022-06-15 14:31     ` Sergey Bronnikov via Tarantool-patches
2022-06-03 13:29 ` [Tarantool-patches] [v2][PATCH 0/5] Support building with Ninja Sergey Bronnikov via Tarantool-patches
2022-06-06 11:24 ` [Tarantool-patches] [v2][PATCH 5/5] ci: add job with build using Ninja on linux-x86_64 Sergey Bronnikov via Tarantool-patches
2022-06-15  8:48   ` Igor Munkin via Tarantool-patches
2022-06-15  9:27     ` Sergey Kaplun via Tarantool-patches
2022-06-15 14:09       ` Sergey Bronnikov via Tarantool-patches
2022-06-15 14:15     ` Sergey Bronnikov via Tarantool-patches
2022-06-15  8:47 ` [Tarantool-patches] [v2][PATCH 0/5] Support building with Ninja Igor Munkin via Tarantool-patches
2022-06-15 14:57   ` Sergey Bronnikov via Tarantool-patches
2022-06-20 12:48 ` Igor Munkin via Tarantool-patches
2022-06-20 13:04   ` Sergey Bronnikov via Tarantool-patches

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=YqmiH7dkP8qTH9U/@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=estetus@gmail.com \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [v2][PATCH 2/5] build/ninja: create target with cli binary only once' \
    /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