20 May 2018 at 12 h 58 min #11068
I am more than glad that finally there is a binary release of SOFA. So I have started to update my QTetraMesher project ( https://qtm.dennis2society.de/ ) which is using some of your libraries to the current Qt and SOFA version. However upon linking there are at least two dependencies missing in the lib folder:
I am on Ubuntu 18.04 x64 and the locally installed version doesn’t match with your binaries, so I have to rely on the provided ones (local version is libicu60.2).
Is there a workaround to fix this? Or could someone add the matching shared objects to the archive to enable linking to your libs?23 May 2018 at 17 h 30 min #11082
That’s awesome to see such an advanced project based on SOFA! We are always glad to discover more achievements! Congratulations for your QTetramesher project!
Note that since it’s all open-source, we would be glad to add it on the SOFA Marketplace. Is this fine for you?
Regarding the linking problem, engineers are already on it! We should be able to get back to you soon.
Hugo23 May 2018 at 18 h 05 min #11088
Thank you for your feedback, libicui18n and libicuuc are indeed missing. The fix is already done in the pending pull request #635.
I will fix the v17.12 binaries tomorrow 😉
Guillaume.23 May 2018 at 19 h 40 min #11094
thanks for the update. Good to hear that I didn’t mess up but that it’s just the missing libraries. I will try to rebuild as soon as the new binary package is available.
Thanks for the feedback on my project. Good to hear someone appreciating it. 🙂
Actually it is released since 2013 when I posted it on the SOFA mailing list however it never got much attention. I just try to keep it updated with every new Ubuntu version and it got (almost) a lot easier since now that there are SOFA binaries available.
I just had a look at your Marketplace and it appears to be SOFA plugins only. My project is a standalone application. Not sure if it is eligible to be listed there. If it is I would be glad to see my project listed in a more prominent place than my private subdomain. 🙂
Please let me know if there are conditions to keep in mind.
Dennis23 May 2018 at 21 h 57 min #11095
That’s a pity that it was not promoted earlier in 2013 !! I am sure it can be useful to many people ! For sure it can fit the Marketplace.
Let us know about the update with Guillaume’s input. If it solves your issue and the rebuild is successful, then I immediately add this on the Marketplace. Does this suit you?
Your project has to benefit from a deserved visibility!
Hugo24 May 2018 at 14 h 27 min #1109824 May 2018 at 20 h 11 min #11103
Thanks a lot @guillaumeparan!
I can now build on Ubuntu (18.04 x64). But I had to rename some of the shared objects in the lib folder because the runtime would request a different minor version (last digit in the filename).
The following .so had to be renamed/symlinked:
libGLEW.so.1.13.0 -> libGLEW.so.1.13
libicudata.so.55.1 -> libicudata.so.55
libicui18n.so.55.1 -> libicui18n.so.55
libicuuc.so.55.1 -> libicuuc.so.55
Not sure if that’s just my build configuration (build and run from QtCreator) of if that’s something else someone would want to look into.
Maybe we should wait with the Marketplace thing until I also have the Windows build running.25 May 2018 at 9 h 40 min #11111
Correct, but as soon as you get it running, it would be our pleasure to advertise it for you!
Hugo25 May 2018 at 13 h 48 min #11113
But I had to rename some of the shared objects in the lib folder because the runtime would request a different minor version (last digit in the filename).
Strange, I just checked and all the symlinks are in the zip file.26 May 2018 at 0 h 09 min #11118
This is how it looks for me. Maybe it’s the Ubuntu “Archive Manager”.
28 May 2018 at 14 h 28 min #11120
Indeed the Archive Manager seems to hide the symlinks.
What happens if you Right Click > Extract Here the archive?28 May 2018 at 21 h 10 min #11131
Thanks for the “Extract Here” tip. This extracted even the symlinks. I have filed a bug report for Ubuntu’s file-roller package. Funnily the symlinks are shown and extracted when the archive is .tar.xz. I wonder how many archives were corrupted by file-roller’s behavior…
I had symlinked the libs manually to avoid adding the version numbers in my .pro file for QtCreator. And the other renaming I had to do was possibly because I was testing my app from within QtCreator. The standalone binary requested the correct version.
Good news! I have successfully made new binary releases. One for Win64_VS2015 and another one for Ubuntu 18.04_x64. I have successfully run the Ubuntu variant in a fresh VirtualBox VM and from this determined which global libs were required. The README.txt in the Ubuntu release tells which libraries must be installed via apt/package-manager.
You may now add it to your Gallery (or wherever it fits…). 🙂
QTetraMesher – Binary Releases on github
QTetraMesher – Project Page
Dennis28 May 2018 at 21 h 47 min #1113230 May 2018 at 19 h 54 min #1114631 May 2018 at 9 h 47 min #11151Damien MarchalParticipant
- CNRS/Defrost Team
On my side I also experience problems with the binary build of Sofa on an ubuntu 18.04.
The easiest way to fix it was to remove the file lib/libz.* you ships so that it fallback to the one installed on the system.
- You must be logged in to reply to this topic.