mirror of
https://github.com/qmlnet/qmlnet.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #116] Not working on Linux #66
Labels
No labels
bug
enhancement
help wanted
help wanted
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/qmlnet#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ticky-Ticky on GitHub (Mar 26, 2019).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/116
Hello!
I have a problem with starting Qml.Net app on Linux (CentOs 7, x64).
App is crashing on start with error:
Both libQmlNet.so and libQt5QuickControls2.so.5 are exist in folder /home/myuser/myapp/
Can you help me?
Thanks in advance
@MaxMommersteeg commented on GitHub (Mar 26, 2019):
Could you share a link to your code, so I can reproduce it locally?
@Ticky-Ticky commented on GitHub (Mar 26, 2019):
I have this error with demo example: https://github.com/qmlnet/qmlnet-examples
@Ticky-Ticky commented on GitHub (Mar 27, 2019):
Problem appears when you build a self-contained application with .net core libs included.
As far as I see there are some troubles with publishing self-contained qml.net application: there are no sub-folders in publish directory, all files and libs lay in one directory without any structure.
Also I can show log with L_DEBUG=all, if it is needed
@norwynn commented on GitHub (Apr 6, 2019):
Somewhat new with .net core here. I got the same thing with the sample. Getting the error below:
Below is the output. Which folder should be copied over to linux (ubuntu 14.04 lts)?
I tried both. Publish with all the files, even the "missing" one in the error above. Am i missing something about the deployment of files?
@pauldotknopf commented on GitHub (Apr 6, 2019):
Yeah, publishing self-contained apps isn't currently supported, because of how NuGet flattens directories when publishing.
See this issue.
I have plans to make the Qt environment not deployed as a part of the NuGet packages, and instead, a zip that is downloaded from some network location. The
libQmlNet.sowill still be deployed as a part of the NuGet packages though.@norwynn commented on GitHub (Apr 6, 2019):
Hi,
These are the settings for the publish in VS, its now Framework dependent instead of self-contained.
Same as the screenshot from my previous comment above, which folder do I copy over to the target Linux environment? Publish or linux-x64?
@pauldotknopf commented on GitHub (Apr 10, 2019):
Now that I think about it, I think it will break in framework dependent mode too.
The solution would be to publish without the
Qml.Net.*Binariespackages, and manually extract theQml.Net.LinuxBinariescontents into the directory, preserving the directory structure.The directory structure is important, and it is what get's destroyed when
dotnetdoes it's publish.This is a top priority to fix.
@pauldotknopf commented on GitHub (Apr 10, 2019):
This will be resolved as a part of #87
@pauldotknopf commented on GitHub (Apr 13, 2019):
This has been resolved as of version
0.8.0. You can checkout the latest examples for verification.@Ticky-Ticky commented on GitHub (Apr 15, 2019):
Thanks, now it works on linux! :)
But...
After updating to 0.9.0, the first app start takes very long time (both on Windows and Linux). The second and further starts are fast, even after reboot.
Before updating all starts were fast.
@pauldotknopf commented on GitHub (Apr 15, 2019):
Yup. That is the time it takes to auto-download a usable Qt runtime into the users directory. See this for more info.
Documentation hasn't been written yet, but you can get around this by deliverying the Qt runtime with your application. Extract a *-runtime.tar-gz to where your executable lives. It will get discovered/used.