-
Notifications
You must be signed in to change notification settings - Fork 22
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
Absolut paths? #65
Comments
Hi. Try using the autotools definitions, which remain the full-featured build system for libti*, gfm & tilp. |
Thanks, I will try that. |
That said, you should be able to just override the paths with the standard cmake (gnu dirs?) variables when invoking it. |
I didn't check just now, but using a %cmake_install directive in the rpm spec file, this should be added. This is what I have used for tilp2. |
Well the CMake stuff is also available in the tilibs repo. So if you build and install those, then tilp2 will be able to be installed.
Technically all this works fine on both my machine and CI machines so it must not be that broken :p However, it's done in an unorthodox way that I haven't fixed yet, which is basically installing the libs while building.
|
I have added the -DCMAKE_INSTALL_PREFIX=%{_buildroot} for the cmake install, but this is not better. Indeed, I see that after building libiconv, the process try to install it, I presume for building the remaining parts.
on the line |
Well, I never set those paths myself, though ^^' Which is part of what I said above about my "unorthodox" way of doing things (building things with deps by first installing the previously built ones). Also, in the But I clearly wasn't a CMake expert when I did all that, and I'm still not one today despite a bit more experience ... any idea what should be changed? |
Hello,
I'm trying to package a snapshot of these libraries in Mageia using a rpm package.
I use the sequence:
cmake
cmake build
cmake install
I use a chrooted environment for the package build (mock).
The process ends badly with:
It seems that the process try to write a file at a hardcoded place, this one not been allowed.
Do I miss something?
The text was updated successfully, but these errors were encountered: