-
-
Notifications
You must be signed in to change notification settings - Fork 332
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
ArmorLab build & run issues #1664
Comments
I had the same issue, but what worked for me was linking the library into /usr/lib |
How did you do that ? Did you just create a symbolic link to the file ? |
Yeah, I just used |
Creating a symbolic link works for me (Ubuntu 22.09 amd64) |
Since my issue was closed and then linked here, I was curious if there was a temporary workaround for the building portion of the program so we can test new builds on platforms. Especially since this seems to date back to December and we're now in April. Just to be clear, I'm not complaining, simply asking if there's any recommendation from the devs currently or if we're supposed to standby for now and if so, is there a current ETA or roadmap to this issue getting fixed. |
Sorry it's taking so long, hopefully fixed in the coming days. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
ArmorLab version:
ArmorLab #23dcc34
OS/device including version:
` .',;::::;,'. crystalyne@hortonator
.';:cccccccccccc:;,. ---------------------
.;cccccccccccccccccccccc;. OS: Fedora Linux 39 (Workstation Editi
.:cccccccccccccccccccccccccc:. Kernel: 6.6.7-200.fc39.x86_64
.;ccccccccccccc;.:dddl:.;ccccccc;. Uptime: 2 hours, 4 mins
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Packages: 2574 (rpm), 72 (flatpak)
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Shell: bash 5.2.21
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Resolution: 3840x2160
:cccccccccccccc;MMM.;cccccccccccccccc: DE: GNOME 45.2
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: WM: Mutter
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; WM Theme: Adwaita
ccccc:XM0';cccc;MMM.;cccccccccccccccc' Theme: ZorinGreen-Dark [GTK2/3]
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Icons: Adwaita [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Terminal: gnome-terminal
cccccc;dNMWXXXWM0::cccccccccccccc:, CPU: AMD Ryzen 7 5800X3D (16) @ 3.400G
cccccccc;.:odl:.;cccccccccccccc:,. GPU: AMD ATI Radeon RX 6800/6800 XT /
:cccccccccccccccccccccccccccc:'. Memory: 15291MiB / 31995MiB
.:cccccccccccccccccccccc:;,..
'::cccccccccccccc::;,.
Issue description:
Attempting to run ArmorLab fails due to failure to link to included library
./ArmorLab: error while loading shared libraries: libonnxruntime.so.1.14.1: cannot open shared object file: No such file or directory
File is present in
~/armortools/armorlab/onnx/linux
Steps to reproduce:
Follow build instructions on main GitHub page. Attempting to run the program using
./ArmorLab ../../armorlab/build/krom
will error out.The text was updated successfully, but these errors were encountered: