Guillaume

Unfortunately we do not yet provide binary plugins to add easily to your binary SOFA. It’s still a work in progress.

To add plugins to your binary SOFA, you will have to build those plugins yourself. Depending on how the plugin has been programmed, you may need to build it with SOFA sources (which will make a complete SOFA build and thus make…[Read more]

Hi Ehab,

Binary version has nearly the same features as your own build version if you did not enable plugins. You can find the precise configuration of the binary version in https://github.com/sofa-framework/sofa/blob/master/package.cmake

As you can see, binary version does not contain tests, tutorials and Modeler application.

The big…[Read more]

Since you are on Windows, when you installed SOFA with the binaries it created a SOFA entry in “All Programs”. runSofa is in this SOFA entry.

If you want to be able to launch runSofa in your console, you will have to add its location to your system PATH. By default on Windows, runSofa is located in C:UsersYOUR_USERNAMESOFA_v...bin.

Guillaume.

Hi Fatima,

First, about the build issue: try running CMake from “VS2017 x64 Native Build Tools Command Prompt”. It is a classic console where all your Visual Studio tools will be accessible.
To do it: Start > type “native command prompt” > Run the x64 one > Run cmake-gui in it

Then, if you just want to discover SOFA and run simulations (the…[Read more]

Hi rubab,

Boost libs are copied to bin directory since v18.06.
If you cloned an older version of SOFA, you will have to do it yourself: go to the folder containing the boost libs you used to compile SOFA (their path should be visible in CMake GUI) and copy them where runSofa.exe has been created (build/your_branch/bin).

Hope that helps,
Guillaume.

I just update the documentation to make it clear. You have to clone SOFA only ONE TIME. The build folder is for the build. Nothing should be cloned there.

Read carefully the steps: https://www.sofa-framework.org/community/doc/getting-started/build/linux/

Hi rubab,

Here is the arrangement we advise:
sofa
build
master
v18.06
my_branch
src
<sofa sources here>

Thus in CMake, to build master branch, set source to “sofa/src” and build to “sofa/build/master”.

Hope that helps,
Guillaume.

Hi,

Are you trying to build SOFA on Windows RT (tablet)?
If no, I think you installed the wrong Qt version. Open your Qt MaintenanceTool and install the libs for “MSVC2015 x64” instead of “WinRT MSVC2015 x64” 😉

Guillaume.

Indeed the Archive Manager seems to hide the symlinks.
What happens if you Right Click > Extract Here the archive?

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.

Here you go: https://github.com/sofa-framework/sofa/releases/tag/v17.12.02

Hi,

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.

Hi,

No, never encountered this error before.
This thread may help.
Perhaps @jnbrunet could help, he knows Fedora well 🙂

Hi,

Did you install all SOFA dependencies? Unfortunately, our documentation is Ubuntu oriented but equivalences can be found easily.
I’d go for the Fedora equivalent of build-essential: dnf install @development-tools

source: https://unix.stackexchange.com/questions/1338/what-is-the-fedora-equivalent-of-the-debian-build-essential-package

Hope…[Read more]

Hi,

Sorry for the late answer.
It seems that your Visual Studio installation is a bit messed up. Did you manage to solve your issue?

Guillaume.

Hi jaume,

Sorry for the very late answer. sofa::helper::parse has indeed been replaced by ArgumentParser in #513.
See usage example in runSofa/Main.cpp.

Hope that helps,
Guillaume.

Hey, I just merged your new topic to this one, no need to separate both.

Thanks for the summary but I’m still unsure of which plugin you want to be the parent plugin and which one to be the child plugin.

Anyway, here are my advices rephrased with “parent plugin” and “child plugin”.

– The parent plugin must be findable so it has to contain a…[Read more]

Hi Eleonora,

I don’t have this freeze issue on my Mac but the double clicking problem is known (and not fixed yet unfortunately).
Did you investigate more on both issues? Any clue would help me to fix them.

Thank you,
Guillaume.

Hi,

I never tried to create a circular dependency between plugins and I don’t think it is a good idea actually.
Are you sure your design is OK?

Guillaume.

Hi,

Could you check you did set BOOST_ROOT=D:/boost_1_66_0?
It seems there is a D:/boost/boost_1_66_0 value somewhere missing the configuration.

Please copy/paste your CMakeCache.txt here 🙂

Guillaume.