scikit_build_example | An example combining scikit-build and pybind11 | Machine Learning library

by pybind C++ Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | scikit_build_example Summary

scikit_build_example is a C++ library typically used in Artificial Intelligence, Machine Learning applications. scikit_build_example has no bugs, it has no vulnerabilities and it has low support. However scikit_build_example has a Non-SPDX License. You can download it from GitHub.

An example combining scikit-build and pybind11

Support

Quality

Security

License

Reuse

Support

scikit_build_example has a low active ecosystem.

It has 50 star(s) with 22 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 4 have been closed. On average issues are closed in 207 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of scikit_build_example is current.

Quality

scikit_build_example has 0 bugs and 0 code smells.

Security

scikit_build_example has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

scikit_build_example code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

scikit_build_example has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

scikit_build_example releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of scikit_build_example

Get all kandi verified functions for this library.

scikit_build_example Key Features

No Key Features are available at this moment for scikit_build_example.

scikit_build_example Examples and Code Snippets

No Code Snippets are available at this moment for scikit_build_example.

Community Discussions

Trending Discussions on scikit_build_example

Running pip install twice to see changes ("developer mode") -- second install fails but first works

CMake C++ library includes toolchain name

Packaging executable, shared library, and Python bindings not finding library

QUESTION

Running pip install twice to see changes ("developer mode") -- second install fails but first works

Asked 2022-Mar-08 at 23:49

I am wondering how to use pip to develop a Python package which is going through many revisions rapidly. My work flow is to write C++ code, compile and install with pip install and test my code.

Then, I would like to change some underlying C++ code, recompile and reinstall with pip, test the new feature, change something else, go back etc. until my package is ready.

Why did pip install ./cmake_example work well the first time but when making changes to the code, reinstalling with recompiling produced an error? I just re-ran the command pip install ./cmake_example.

I changed a single line of C++ code in an innocuous way (adding +1 in the 'add' function just to see if I can change code and recompile) and the code compiled fine in my IDE without pip.

My basic idea was to use pip following this method to avoid having to hackishly insert my shared object into some python directory each time I make a change.

I used the cmake_example from pybind here and followed the steps and did pip install ./cmake_example and it worked very well. I ran the example fine in a Python console.

Then, I changed some code (just added +1 to the adding function), so nothing substantial and wanted to re-install the package.

I then got this error:

...

ANSWER

Answered 2022-Feb-18 at 23:14

I found that deleting the build directory inside the cmake_example directory resolved the problem and pip install ./cmake_example worked again as it did the first time. You can combine the two commands:

Source https://stackoverflow.com/questions/71179122

QUESTION

CMake C++ library includes toolchain name

Asked 2022-Feb-18 at 10:35

I am building a Python extension in C++ using pybind11 and scikit-build. I base on the example provided at https://github.com/pybind/scikit_build_example/blob/master/setup.py.

My CMakelists boils down to this:

...

ANSWER

Answered 2022-Feb-18 at 10:35

Conclusion: as Alex said this part of the name is necessary. See https://www.python.org/dev/peps/pep-3149/. Python will automatically figure out it can use _mylib.cpython-38-x86_64-linux-gnu.so if you import _mylib.

Source https://stackoverflow.com/questions/71162642

QUESTION

Packaging executable, shared library, and Python bindings not finding library

Asked 2021-Nov-30 at 00:52

I have a project, cloudgen, that I would like to add bindings for Python so I can access some of the underlying functions. I have stubbed out the initial work on a branch. Because the main executable is built with cmake, I decided to use scikit-build to manage the build and use pybind11 to deal with the binding (following this example repo).

When I run pip install . in a virtual environment, everything appears to work as expected. I find the executable is installed to /bin, the library goes into /lib, and the module goes into /lib/pythonX.Y/site-packages/cloudgen. In fact, if I run pip uninstall cloudgen, all of the correct files are uninstalled. However, my problems arise when I start to test the Python bindings. I find two separate but related problems.

If I installed into an Anaconda environment, the module is able to resolve the path to the shared library and pass the tests, but the executable does not resolve the path to the library.
On the other hand, if I installed into a virtual environment using python -m venv, both the module and the executable are unable to resolve the path to the shared library.

Searching around, I came across this question which notes I could manipulate LD_LIBRARY_PATH (or equivalently DYLD_LIBRARY_PATH on macOS or PATH on Windows), but that is normally frowned upon. That question references an open issue that refers to including additional build products (which as I said appears to not be my problem) but doesn't address the library path resolution. I also came across this question asking about distributing the build products using scikit-build and this question using setuptools directly. Neither of the questions or answers address the library path resolution.

My question is: What is the correct way to distribute a package that contains an executable, shared library, and Python binding module and have the path resolution Just Work™?

A minimal working example is a bit much, but I created a gist to demonstrate the behavior.

...

ANSWER

Answered 2021-Nov-30 at 00:52

After a bit more digging (and carefully reading the CMake documentation on RPATH), the correct answer appears to be explicitly setting RPATH on installation. The relevant change to the linked gist is to add the following to the CMakeLists.txt after creating the targets (adapted from the linked Wiki):

Source https://stackoverflow.com/questions/70044257

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install scikit_build_example

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: