From: Igor Munkin <imun@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 2/4] test: adjust luajit-tap testing machinery Date: Wed, 8 Apr 2020 02:05:16 +0300 [thread overview] Message-ID: <20200407230516.GB5713@tarantool.org> (raw) In-Reply-To: <630f27a6-f0ac-5900-a3d6-11eb44326ee9@tarantool.org> Vlad, Thanks for your review! On 05.04.20, Vladislav Shpilevoy wrote: > Hi! Thanks for the patch! > > On 27/03/2020 14:23, Igor Munkin wrote: > > This changeset makes possible to run luajit-tap tests requiring > > libraries implemented in C: > > * symlink to luajit test is created on configuration phase instead of > > build one. > > What is the difference? Is it really necessary for anything? To be > able to see CMake files in there? Exactly. I hoisted symlink creation to add Cmake subdirectories in the further patches. > > > * introduced a CMake function for building shared libraries required for > > luajit tests. > > > > Signed-off-by: Igor Munkin <imun@tarantool.org> > > --- > > test/CMakeLists.txt | 15 +++++++++------ > > 1 file changed, 9 insertions(+), 6 deletions(-) > > > > diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt > > index 9b5df7dc5..00fce7270 100644 > > --- a/test/CMakeLists.txt > > +++ b/test/CMakeLists.txt > > @@ -13,6 +13,13 @@ function(build_module module files) > > endif(TARGET_OS_DARWIN) > > endfunction() > > > > +function(build_lualib lib sources) > > This function is introduced in tarantool, but required > for luajit. On the contrary, luajit is required for tarantool. > This is cyclic dependency, which makes impossible to run such > tests inside luajit. I think luajit tests should be kept self > sufficient. Otherwise it makes no sense to keep them in luajit > repository. If you anyway can't run them in there, and need to > create some test-wrappers from tarantool's side. > > Alternative is to move them completely to tarantool. But current > way is not right. It is half of one and half of other solution. We already moved them out from the tarantool repo in the scope of this issue[1]. However, as you can see, we moved them only partially. This fact also makes me frustrating and I'm going to rework LuaJIT test infrastructure in the scope of the separate ticket[2]. > > > + add_library(${lib} SHARED ${sources}) > > + set_target_properties(${lib} PROPERTIES PREFIX "") > > + if(TARGET_OS_DARWIN) > > + set_target_properties(${lib} PROPERTIES LINK_FLAGS "-undefined dynamic_lookup") > > + endif(TARGET_OS_DARWIN) > > +endfunction() [1]: https://github.com/tarantool/tarantool/issues/4478 [2]: https://github.com/tarantool/tarantool/issues/4862 -- Best regards, IM
next prev parent reply other threads:[~2020-04-07 23:12 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-27 13:23 [Tarantool-patches] [PATCH 0/4] Enable LuaJIT tests written in C Igor Munkin 2020-03-27 13:23 ` [Tarantool-patches] [PATCH 1/4] luajit: bump new version Igor Munkin 2020-03-27 13:23 ` [Tarantool-patches] [PATCH 2/4] test: adjust luajit-tap testing machinery Igor Munkin 2020-04-05 19:32 ` Vladislav Shpilevoy 2020-04-07 23:05 ` Igor Munkin [this message] 2020-03-27 13:23 ` [Tarantool-patches] [PATCH 3/4] test: enable luajit-tap:gh-4427-ffi-sandwich tests Igor Munkin 2020-03-30 18:53 ` Igor Munkin 2020-04-05 19:32 ` Vladislav Shpilevoy 2020-04-07 23:28 ` Igor Munkin 2020-04-09 22:05 ` Vladislav Shpilevoy 2020-04-15 0:46 ` Igor Munkin 2020-03-27 13:23 ` [Tarantool-patches] [PATCH 4/4] test: enable luajit-tap:lj-flush-on-trace tests Igor Munkin 2020-03-30 18:53 ` Igor Munkin 2020-04-05 19:32 ` Vladislav Shpilevoy 2020-04-07 23:33 ` Igor Munkin 2020-04-09 22:05 ` Vladislav Shpilevoy 2020-04-15 0:47 ` Igor Munkin 2020-03-27 13:32 ` [Tarantool-patches] [PATCH 0/4] Enable LuaJIT tests written in C Igor Munkin 2020-03-28 11:18 ` Igor Munkin 2020-03-30 18:55 ` Igor Munkin
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=20200407230516.GB5713@tarantool.org \ --to=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/4] test: adjust luajit-tap testing machinery' \ /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