You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sergeyb@pony:~/sources/MRG/tuple-keydef/build$ cmake ..
-- The C compiler identification is GNU 9.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Warning (dev) at /home/sergeyb/.local/lib/python3.8/site-packages/cmake/data/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message):
The package name passed to `find_package_handle_standard_args` (TARANTOOL)
does not match the name of the calling package (Tarantool). This can lead
to problems in calling code that expects `find_package` result variables
(e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
cmake/FindTarantool.cmake:27 (find_package_handle_standard_args)
CMakeLists.txt:16 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Found TARANTOOL: /usr/include (found version "2.8.2-16-g88458ba1c")
-- Tarantool LUADIR is share/tarantool
-- Tarantool LIBDIR is lib/tarantool
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sergeyb/sources/MRG/tuple-keydef/build
Commit f7f84f0 ('cmake: fix warning')
causes a little regression: if there is no tarantool/module.h header, we
should fail at the cmake stage. After the fix of the warning we'll fail
only at the building stage (when `make` is called). Here I return the
old behaviour (fail on the `cmake` stage) back.
Follows up #18
Commit f7f84f0 ('cmake: fix warning')
causes a little regression: if there is no tarantool/module.h header, we
should fail at the cmake stage. After the fix of the warning we'll fail
only at the building stage (when `make` is called). Here I return the
old behaviour (fail on the `cmake` stage) back.
Follows up #18
Git hash: 109c913
The text was updated successfully, but these errors were encountered: