mirror of
https://github.com/qmlnet/qmlnet.git
synced 2026-05-16 14:15:57 -06:00
[GH-ISSUE #158] Undefined Symbol error when using self-compiled libQmlNet.so #98
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#98
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 @hnrhn on GitHub (Aug 14, 2019).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/158
I have been attempting to compile my own libQmlNet.so so that I can include
QT += widgetsin the QmlNet.pro file (trying to solve the same problem as https://github.com/qmlnet/qmlnet/issues/149).However, when trying to run a program using my .so file instead of the one downloaded from NuGet, I get the following error:
The .so file that comes from NuGet is 2.0MiB, but the one generated by running build.sh myself comes out at 2.3MiB -- regardless of whether I include the
QT += widgetsline or not, so I assume this is coming in the qmake step, or Qt itself.I'm using a fresh install of Qt5.12.4 (installed directly using Qt's web installer, not a package manager), running on Manjaro. Am I doing something wrong, or is there some other setup step I'm missing?
@pauldotknopf commented on GitHub (Aug 15, 2019):
What is your output of
nm -D libQmlNet.so?@hnrhn commented on GitHub (Aug 15, 2019):
nmOutput.txt
I ran a diff against the same output for the .so from NuGet and the symbol values are different for practically everything (though I don't know enough about this topic to know whether that matters), a few chunks of extra lines in my version, and a few extra lines in the NuGet version.
@pauldotknopf commented on GitHub (Aug 15, 2019):
I see the issue.
You are compiling the latest native libs, using older .NET lib (probably from NuGet).
You have to make sure the native libs and .NET dll matches.
The
type_info_setPrefVariantTypeexported method has been removed, but your .NET libs are trying to use it.@hnrhn commented on GitHub (Aug 15, 2019):
Yep, that'll do it alright. I thought I'd covered all my bases, but I guess I didn't spot that "develop" is the default branch.
Thanks for the help!