-
Notifications
You must be signed in to change notification settings - Fork 39
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
Troubles compiling visualino in Fedora 26 #41
Comments
Try this: sudo mkdir /usr/share/visualino/ && cp -r roboblocks/html/ /usr/share/visualino/ I just took a look and it works in Fedora 27. |
Well, I'm sure you are fully aware a local software install outside /usr/local/, /opt/, /srv or $HOME is not a systems good practice, neither help to build, for example, an RPM package. :-) |
The question is, does it work or not? Do you now see the blocks? The code
has Linux packaging in mind, and that's why it searches in
/usr/share/visualino/ by default.
|
Thankyou. |
@itubal confirmed. I can't check because I all my systems are production and can't afford to mesh the filesystem.
For RPM packaging this is unsuitable. RPM building doesn't use chroot enviroments for %install step and file installations paths should be constructed adding specific macros as in:
both qmake and make are expected to work this way but I can't figure out why can't work in our case:
There is not install error messages neither. Note that /home/olea/visualino-app path was a parameter when qmake was invoked. Without modification it can't be packaged in RPM. Would need to check if it can work in Flatpak. |
Hi:
Here using visualino from master branch and trying to compile visualino. We indeed compile it but the make install step doesn't work. I'm not used to the qt framework practices so maybe I'm missing something obvious. All binary dependencies seem to be correct as the binary is generated and runs.
Here is the log of the building process: https://asciinema.org/a/uzsKy2dRgFRf8uZvNsW2ma0ig
Any advise, please?
The text was updated successfully, but these errors were encountered: