pybind / pybind/pybind11

[BUG] 2.6.2: no cmake test suite with PYBIND11_TEST:BOOL=ON

Open
#3,007 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
18k
Forks
2.3k
Avg merge
5d 17h
Merged PRs (30d)
10

Description

Looks like something is not finished.

+ cd pybind11-2.6.2
+ /usr/bin/make -O -j48 V=1 VERBOSE=1 -C x86_64-redhat-linux-gnu test ARGS=--output-on-failure
make: *** No rule to make target 'test'.  Stop.
[tkloczko@barrel x86_64-redhat-linux-gnu]$ cmake -L
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.


CMake Error: The source directory "/home/tkloczko/rpmbuild/BUILD/pybind11-2.6.2/x86_64-redhat-linux-gnu" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
-- Cache values
CATCH_INCLUDE_DIR:PATH=/usr/include/catch2
CMAKE_BUILD_TYPE:STRING=RelWithDebInfo
CMAKE_INSTALL_PREFIX:PATH=/usr
DOWNLOAD_EIGEN:BOOL=OFF
Eigen3_DIR:PATH=/usr/share/eigen3
PYBIND11_CMAKECONFIG_INSTALL_DIR:STRING=share/cmake/pybind11
PYBIND11_CUDA_TESTS:BOOL=OFF
PYBIND11_FINDPYTHON:BOOL=OFF
PYBIND11_INSTALL:BOOL=ON
PYBIND11_NOPYTHON:BOOL=OFF
PYBIND11_PYTHON_VERSION:STRING=
PYBIND11_TEST:BOOL=ON
PYBIND11_TEST_FILTER:STRING=
PYBIND11_TEST_OVERRIDE:STRING=
PYBIND11_TEST_PREFIX_COMMAND:STRING=
PYBIND11_WERROR:BOOL=OFF
USE_PYTHON_INCLUDE_DIR:BOOL=OFF

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's CMakeLists.txt and the configuration for PYBIND11_TEST=ON, then reproduce the reported build with CMake and make test. Done means the configured build provides a test target and the test command runs successfully with the shown options.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, python
Domain
build-system, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.