# One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!

# One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!

+

__FORCETOC__

+

__TOC__

= Ubuntu 18.04 =

= Ubuntu 18.04 =

Line 133:

Line 135:

'''Discussion thread where you can ask questions about these steps''': {{Installation/NoThreadAskForum}}

'''Discussion thread where you can ask questions about these steps''': {{Installation/NoThreadAskForum}}

+

+

<br>

+

== Compiling the On-Screen Mesa drivers for ParaView ==

+

+

On virtual machines or when using older graphics cards and/or drivers, it's not possible to use ParaView 5.6 because it needs OpenGL2 support with version 3.3 or newer. Therefore, a workaround, is to build and deploy On-Screen Mesa drivers.

In addition, we need to turn on the sources list, because we need to install the additional dependencies needed for building Mesa from source code:

+

<bash>sed -i~orig -e 's/# deb-src/deb-src/' /etc/apt/sources.list

+

apt-get update

+

apt-get build-dep mesa

+

</bash>

+

And you're using a virtual machine, make sure you also install the toolkit provided by your virtualization software. For example, for VirtualBox you can use the following command to install the guest toolkit:

+

<bash>apt-get install virtualbox-guest-x11</bash>

+

</li>

+

</li>

+

+

{{Installation/Linux/ExitRoot}}

+

+

<li>Now for the process of building Mesa for the OpenGL software renderer, we need to run the following commands:

Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM-7 shell environment. In other words, whenever you start a new terminal, you should run:

In order to build ParaView 5.4.0, including with the ability to use Python and MPI, several steps are needed:

Make sure you're running in the ThirdParty folder and that the correct Qt version is used:

cd$WM_THIRD_PARTY_DIRexportQT_SELECT=qt5

For building ParaView with Python and MPI, it depends on whether you have installed the i686 or x86_64 architecture of Ubuntu. To check this, run:

uname -m

Now, accordingly:

For i686:

#this will take a while... somewhere between 30 minutes to 2 hours or more
./makeParaView -python -mpi -python-lib /usr/lib/i386-linux-gnu/libpython2.7.so.1.0 > log.makePV 2>&1

For x86_64:

#this will take a while... somewhere between 30 minutes to 2 hours or more
./makeParaView -python -mpi -python-lib /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 > log.makePV 2>&1

Once the makeParaView script is finished running, make sure to check the contents of the file log.makePV and check if there are any errors. If you have any problems building or using ParaView, please check the ParaView installation FAQ page.

Finally, update the shell environment:

wmRefresh

Now let's build OpenFOAM:

Go into OpenFOAM's main source folder and be certain that the correct Qt version is being used:

cd$WM_PROJECT_DIRexportQT_SELECT=qt5

This next command will take a while... somewhere between 30 minutes to 3-6 hours:

./Allwmake -j 4 > log.make 2>&1

Note: The "4" refers to the number of cores to be used for building in parallel. In addition, the amount of RAM needed for building scales with the number of cores used, something like 1GB of RAM per core; a minimum of 1.5GB is needed for linking the libraries, which is not done in parallel.

Run it a second time for getting a summary of the installation:

./Allwmake -j 4 > log.make 2>&1

Note: Technically, the build will stop as soon as the first error is found. Running a second time only makes it easier to sort through between what's already been built and where the crash occurred.

Note: And keep in mind that you need to be careful with the letter case of the command. It's icoFoam, not icoFOAM.

If the previous command failed to work properly, then edit the file log.make and check if there are any error messages. A few examples on how you can edit this file:

By using kwrite:

kwrite log.make

By using gedit:

gedit log.make

By using nano:

nano log.make

You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

Note: It's the first error message that matters.

If you don't understand the output, then please compress the log-file log.make and attach the compressed file to a post in the designated thread.
If you do not know how to create a compressed file, then try one of the following examples:

You can compress the file with gzip by running this command:

gzip < log.make > log.make.gz

Then attach the resulting package file named log.make.gz to a post in the designated thread.

Or you can compress one or more log-files into a tarball package file, by running this command:

tar -czf logs.tar.gz log.*

Then attach the resulting package file named logs.tar.gz to a post in the designated thread.

Now you can go read the User Guide, where you may have more than one choice:

Which you can find a local copy of the User Guide by running the following command:

ls -A1 $WM_PROJECT_DIR/doc/Guides*/*UserGuide*.pdf

You should see two available formats: A4 and US-Letter.

But if it instead tells you that there is No such file or directory, then the OpenFOAM environment is possibly not properly activated.

You can also find the more recent OpenFOAM Foundation User Guides online at the following page: official OpenFOAM User Guide - but be careful if you use the version that is too much ahead of the version you are currently using, given that some features have changed overtime.

Note: When you want to update your build, follow the instructions on section Steps for updating on the parent page.

Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM-7 shell environment. In other words, run the following command whenever you start a new terminal:

1.1 Compiling the On-Screen Mesa drivers for ParaView

On virtual machines or when using older graphics cards and/or drivers, it's not possible to use ParaView 5.6 because it needs OpenGL2 support with version 3.3 or newer. Therefore, a workaround, is to build and deploy On-Screen Mesa drivers.

Steps:

Switch to root mode (administrator), to install the necessary packages:

sudo -s

If the 'sudo' command tells you're not in the sudoers list, then run:

su -

Update the apt-get cache by running:

apt-get update

Install the necessary packages:

apt-get install mesa-utils libglu1-mesa-dev scons llvm-dev

In addition, we need to turn on the sources list, because we need to install the additional dependencies needed for building Mesa from source code:

And you're using a virtual machine, make sure you also install the toolkit provided by your virtualization software. For example, for VirtualBox you can use the following command to install the guest toolkit:

apt-get install virtualbox-guest-x11

Now exit from the root mode:

exit

Now for the process of building Mesa for the OpenGL software renderer, we need to run the following commands: