-
Notifications
You must be signed in to change notification settings - Fork 81
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
[2.1] - Multi-architecture installation not possible anymore #10
Comments
As you might have guessed, since this is still open, this is a tricky issue. I do not currently have a proper solution, though adding a cached path for library installation might work. Is there a document somewhere that indicates what should go where on Debian? |
Well, I think you don't have to look for a Debian specific solution. There
are CMake variables which are already defined by default for any platform.
In case of Debian packaging they are just overwritten by a prefix just
before it gets packaged.
It should be variables like DESTDIR, LIBDIR or BINDIR from autotools.
Hope it helps a little bit.
|
Hey, Regards |
Hardcoding install dirs is never a good idea; this effectively breaks your system's interoperability with automated build-systems downstream. |
@tomboy-64 I already made reverts on this change and made tests on it.
Currently it works on Ubuntu without hardcodes and the real problem was
caused while using ArchLinux. However you can read yourself the whole story
in the PR made for [master].
I guess they are really busy at the moment.
|
We're always busy ;) But yeah, releasing 2.1 did put a lot of pressure on the team (multiple delays & all). Things are a bit more relaxed now, but working at ultimaker is never calm or quiet ;) Another issue is that i know very little of build systems (Which is also why I'm damn happy that you guys pick these things up :D). Same goes for GhostKeeper, so most of these issues are left to awhiemstra and he doesn't check github as often as me & ghostkeeper do. |
Ah, OK. Well, I would prepare in your case chroots for every distribution
you are targeting. For example you take one folder for all the sources and
then share it between all the chroots.
I'm just to lazy at the moment to set this up and I actually won't need
this so often as you probably do.
Looks like Ultimaker needs a Linux hacker in their team 😁
|
So uh, looking for a job then? |
Yes and it sounds interesting to work for you. At least I would get paid for fixing problems in applications or their packaging 😉 I made this for years across different opensource projects and gave projects, like kivy (https://kivy.org/#aboutus), the possibility to be easier to setup and access. If you think I made a good job so far and I would fit into the team, I can write your supervisor about myself or, if you like, you can ask yourself if there is a free job for me 😃 |
There's always a job opening in our team! Our team is looking forward to meeting you ^^
|
Awesome! |
Because debian allows multiarch installation of libraries, it is needed to install to a specific path.
CMAKE_LIBRARY_PATH usually sets this path, but it doesn't work anymore on 15.10 branch.
The reason could be commit 6eeb674 here the */lib path has been hardcoded.
On master it is working with:
The text was updated successfully, but these errors were encountered: