Editing/Rendering OOFEM documentation

You need to install a LaTeX editor to modify and update the OOFEM manual source files. Texmaker is one of the best editors for this purpose. Installing Texmaker and libraries that OOFEM documentation needs to compile. If you are here just to download the manuals I have compiled (April 2021) please scroll to the end

Correcting timeout values in CLion

 If you get timeout error during debugging; this can be due to your host machine hardware limitation. You may workaround this problem by increasing the timeout values for CLion: Go to the Help | Find Action > run “Registry” command Find “cidr.debugger.timeout” “cidr.debugger.timeout.evaluate” “cidr.debugger.timeout.load” Increase values (e.g. 120,000) This may cause you machine to freeze

Remove password prompt to access shared folder inside guest Ubuntu virtual machine

If you are using virtual box, you may need to easily transfer files with the host operating system. This can be done through shared folder in Virtual Box setting. However you may not have permissions inside Ubuntu machine to access this folder, you may get an error or be prompted for password. You can add

Running oofem “*.in” files from CLion

I always keep the input (*.in) files inside “run_dir” directory inside project directory (they will not be a part of the repository). If you want to do this, you have to change running (working) directory inside run configuration. Open drop-down menu next to the green hammer icon below menu bar. Inside program arguments you can

CLion debug: Skip C++ standard files in GDB debugger

You need to tell GDB debugger to skip standard file by making two .gdbinit files. One is inside the project folder and is a part of oorbs repository. The other one is inside you home directory and will address the other .gdbinit file. More info:https://stackoverflow.com/questions/5676241/tell-gdb-to-skip-standard-files/42985979#42985979https://www.jetbrains.com/help/clion/configuring-debugger-options.html#gdbinit-lldbinit  Add .gdbinit file in your home directory (if it didn’t

Building OOFEM clone in CLion and configuring Python interpreter

 A) Building the project CLion automatically detects CMakeLists.txt and loads the source files, the remaining process is easy: (This is for Linux, For MacOS skip this) First, install Doxygen and Python:sudo apt-get install doxygenFor the next part also install pythonsudo apt install python3-pip Below the menu from the drop-down select “oofem|Debug”. If you don’t see

Cloning the Repository using CLion

Before continuing, you may want to make sure that you have the proper compilers installed so that in case you are asked to setup toolchains you can select the desired compiler. Go to the Github website and star the targeted repository:— For original OOFEM: https://github.com/oofem/oofem— For RBSM (OORBS): https://github.com/oorbs/oofem Open CLion Start a new project

Installing Git

In order to clone the repository using CLion, you need to install Git. Simply open the terminal (ctrl+alt+t) and use these commands to install Git: Update apt:  sudo apt-get update  sudo apt-get upgrade   Install Git:sudo apt-get install git-all     You can verify if Git is installed:  git version

Setting up the development environment: Installing CLion under Ubuntu

For our project, we chose to use CLion as a development IDE under Ubuntu. CLion provides a much more suitable environment compared to other alternatives such as Eclipse and it can be installed both on Windows or Ubuntu machines. Since compiling OOFEM under windows is not continuously supported you have to set up an Ubuntu