Guillaume

Hi Asma,

The SofaPython plugin is relying on Python 2.7 (this will change during the next 6 months with a brand new SofaPython3 plugin).
You must install Python 2.7 and choose between :
add Python 2.7 install directory to your system PATH
or
set PYTHON_LIBRARIES and PYTHON_INCLUDE_DIRS manually in CMake GUI

Cheers,
Guillaume.

Ok I think it’s fixed. Could you be my beta tester for this binaries please?

Thanks,
Guillaume.

Hi Gaetan,

Indeed, this lib is missing in v19.06 🙁
I am currently working on fixing that. In the meantime, you can try to install it on your system with apt-get install libicu55 (or whatever Fedora equivalent).

Please tell me if it fixes the problem.
Guillaume.

Hi @eyadshak,

At every new Boost version, it takes some (long) time for CMake devs to update how to handle the dependencies within Boost. Because of this, latest Boost versions always cause detection problems with CMake.

My recommendation to avoid this problem:
1. Go on CMake releases page and note the release date of the latest stable CMake…[Read more]

Hello @nicklj,

Let me try to connect all the pieces together…

Your environment is:
– SOFA source dir = /home/liuj/github/sofa/master
– plugins source dir = /home/liuj/github/sofa/master/plugins
– SOFA build dir = /home/liuj/github/sofa/master/build
– SOFA install dir = /home/liuj/opt/SOFA/master

You have 2 problems:
1. SofaPython does not…[Read more]

Hi guys,

I’ll try to answer some of your questions.

The WinDepPack has to be unzipped in the sources of SOFA. It ADDS “include”, “lib” and “licenses” folders (they do not exist before).

On my machine, the only variable I need to find Boost is BOOST_ROOT. I don’t have any Boost in my PATH, I don’t have any Qt in my PATH. Thus, I don’t understand…[Read more]

Hum, I doubt that moving SofaPython.dll was the real fix to your problem. Something else might have changed…

If you have more info on what happened do not hesitate to post it here!
In the meantime, I guess this topic is solved.

Guillaume.

Hi,

A failing SofaPython loading almost always means a problem in Python+Numpy installation.

1. Did you install Python correctly?
You must have Python 2.7.x 64-bit.
To verify, open a CMD console and type python -c "import sys;print("%x" % sys.maxsize, sys.maxsize > 2**32)"
It must return exactly ('7fffffffffffffff', True)

2. Did you install…[Read more]

Hi wowsofa,

Thank you for the bug report, I will investigate here. Looks like CMake 3.13 does not like including CPack generators.

Could you tell me if commenting out this line fixes the problem?

Thanks,
Guillaume.

Hi @guntisl,

It seems that runSofa falled back on the batch GUI because it didn’t have any Qt GUI available.
Make sure you compiled the Qt GUI:
– you should have QGLViewer.so and SofaGuiQt.so in lib/
– when you run cmake, you should see “QGLViewer: Using Qt5” and “SofaGUIQt: Using Qt5”

Hope that helps,
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.