Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python binding is installed into a wrong place, into the build directory #178

Closed
yurivict opened this issue Nov 16, 2019 · 3 comments
Closed
Assignees
Labels

Comments

@yurivict
Copy link

It installs the file into /usr/ports/math/clingo/work/.local/lib/python3.7/site-packages/clingo.so, when /usr/ports/math/clingo/work was the build path. So it will be installed into the build location, when the correct location is lib/python3.7/site-packages/clingo.so.

@rkaminsk
Copy link
Member

There are options to configure where the module is installed. You can set PYCLINGO_USER_INSTALL=Off to not install in the user's site directory. There are also more options. You can have a look at app/pyclingo/CMakeLists.txt how they are used.

@yurivict
Copy link
Author

By default you should install tyhem into a standard directory, like all other python packages.

@rkaminsk
Copy link
Member

By default cmake installs in /usr/local. Also there are a lot of users without root access. In any case it is hard to provide good defaults where to install the python module.

On another note, it looks like the cmake developers are working on improving support for building python modules. Maybe this will also lead to cmake specific options to install python modules + defaults for them, which clingo can then just use.

For now users should read the installation instructions that ship with clingo. 😉

https://github.com/potassco/clingo/blob/master/INSTALL.md

@rkaminsk rkaminsk self-assigned this Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants