How to build - Revision history

AndrejKP: Installation instructions now direct the user to master branch

2025-07-19T16:59:20Z

Installation instructions now direct the user to master branch

Zigavaupotic at 14:19, 7 July 2023

2023-07-07T14:19:04Z

AndrejKP: Temporarily changed the branch in installation instructions to "dev", until we sort out the master branch again.

2023-06-13T11:16:47Z

Temporarily changed the branch in installation instructions to "dev", until we sort out the master branch again.

AndrejKP: Added the mention of the fix for "packages cannot be located" (at least it worked for me)

2022-06-16T12:52:28Z

Added the mention of the fix for "packages cannot be located" (at least it worked for me)

MihaR: Updated run script flags

2021-08-17T10:47:44Z

Updated run script flags

Jureslak: /* Linker errors */

2020-07-06T19:09:54Z

‎Linker errors

Jureslak at 19:09, 6 July 2020

2020-07-06T19:09:09Z

Jureslak at 18:56, 6 July 2020

2020-07-06T18:56:11Z

Jureslak at 13:03, 30 December 2019

2019-12-30T13:03:08Z

Mitjajancic: /* HDF5 */

2019-03-22T10:44:36Z

‎HDF5

@@ Line 3: / Line 3: @@
 <syntaxhighlight lang="bash">
 sudo apt-get install git g++ python3 cmake libhdf5-serial-dev doxygen graphviz
-git clone https://gitlab.com/e62Lab/medusa.git --branch dev --single-branch
+git clone https://gitlab.com/e62Lab/medusa.git --branch master --single-branch
 cd medusa
 ./run_tests.py -t

@@ Line 117: / Line 117: @@
 <syntaxhighlight lang="bash">
 sudo ln -s /usr/lib/x86_64-linux-gnu/hdf5/serial/* /usr/lib
 </syntaxhighlight>

@@ Line 3: / Line 3: @@
 <syntaxhighlight lang="bash">
 sudo apt-get install git g++ python3 cmake libhdf5-serial-dev doxygen graphviz
-git clone https://gitlab.com/e62Lab/medusa.git --branch master --single-branch
+git clone https://gitlab.com/e62Lab/medusa.git --branch dev --single-branch
 cd medusa
 ./run_tests.py -t

@@ Line 11: / Line 11: @@
 works, you are ready to go! Otherwise install any missing packages and if it
 still fails, raise an issue!
 For instructions on how to use this library in you project, see

@@ Line 5: / Line 5: @@
 git clone https://gitlab.com/e62Lab/medusa.git --branch master --single-branch
 cd medusa
-./run_tests.py
+./run_tests.py -t
 </syntaxhighlight>
 which installs dependencies, clones the repository, goes into the root folder of
@@ Line 72: / Line 72: @@
 cmake ..
 cd ..
-python3 run_tests.py
+python3 run_tests.py -t
 </syntaxhighlight>

@@ Line 49: / Line 49: @@
 This is expected and is the result of some optimizations of compilation time. The medusa library can actually be included in two ways: as
-<code>#include <medusa/Medusa_fwd.hpp></code> or <code>#include <medusa/Medusa.hpp></code>. The first version contains the declarations of all symbols, but not all the definitions. Some of the more commonly used template instantiations are included, but by far not all. Using a template instantiation that is not precompiled will cause your program to compile fine, but will fail to link, due to the missing definitions. In this case you have a few options: include the <i>full</i> Medusa library (without <code>_fwd</code> and it should just work, but you will have to wait a bit longer for it to compile. Include only the missing header (in the case above <code>medusa/bits/domains/FindBalancedSupport.hpp</code>) and pay for whay you use. Or, add your instantiation among the already precompiled instantiations (located in <code>.cpp</code> files, such as e.g. [https://gitlab.com/e62Lab/medusa/-/blob/dev/src/domains/DomainDiscretization.cpp this one]).
+<code>#include <medusa/Medusa_fwd.hpp></code> or <code>#include <medusa/Medusa.hpp></code>. The first version contains the declarations of all symbols, but not all the definitions. Some of the more commonly used template instantiations are included, but by far not all. Using a template instantiation that is not precompiled will cause your program to compile fine, but will fail to link, due to the missing definitions. In this case you have a few options: include the <i>full</i> Medusa library (the header without the <code>_fwd</code>) and it should just work, but you will have to wait a bit longer for it to compile. Include only the missing header (in the case above <code>medusa/bits/domains/FindBalancedSupport.hpp</code>) and pay for whay you use. Or, add your instantiation among the already precompiled instantiations (located in <code>.cpp</code> files, such as e.g. [https://gitlab.com/e62Lab/medusa/-/blob/dev/src/domains/DomainDiscretization.cpp this one]).
 == Building on macOS ==

← Older revision		Revision as of 19:09, 6 July 2020
Line 36:		Line 36:

	== Linker errors ==		== Linker errors ==
		+
		+	When trying out different classes, you might come along linker errors such as
		+
		+	<code>
		+	Scanning dependencies of target cantilever_beam
		+	[100%] Building CXX object examples/linear_elasticity/CMakeFiles/cantilever_beam.dir/cantilever_beam.cpp.o
		+	[100%] Linking CXX executable ../../../examples/linear_elasticity/cantilever_beam
		+	/usr/bin/ld: CMakeFiles/cantilever_beam.dir/cantilever_beam.cpp.o: in function `main':
		+	cantilever_beam.cpp:(.text.startup+0x162): undefined reference to `void mm::FindBalancedSupport::operator()<mm::DomainDiscretization<Eigen::Matrix<double, 2, 1, 0, 2, 1> > >(mm::DomainDiscretization<Eigen::Matrix<double, 2, 1, 0, 2, 1> >&) const'
		+	collect2: error: ld returned 1 exit status
		+	</code>
		+
		+	This is expected and is the result of some optimizations of compilation time. The medusa library can actually be included in two ways: as
		+	<code>#include <medusa/Medusa_fwd.hpp></code> or <code>#include <medusa/Medusa.hpp></code>. The first version contains the declarations of all symbols, but not all the definitions. Some of the more commonly used template instantiations are included, but by far not all. Using a template instantiation that is not precompiled will cause your program to compile fine, but will fail to link, due to the missing definitions. In this case you have a few options: include the <i>full</i> Medusa library (without <code>_fwd</code> and it should just work, but you will have to wait a bit longer for it to compile. Include only the missing header (in the case above <code>medusa/bits/domains/FindBalancedSupport.hpp</code>) and pay for whay you use. Or, add your instantiation among the already precompiled instantiations (located in <code>.cpp</code> files, such as e.g. [https://gitlab.com/e62Lab/medusa/-/blob/dev/src/domains/DomainDiscretization.cpp this one]).

	== Building on macOS ==		== Building on macOS ==

@@ Line 34: / Line 34: @@
 Binaries are placed into <code>bin/</code> folder. Tests can be run all at once via <code>make medusa_run_tests</code>
 or individually via e. g. <code>make operators_run_tests</code>.
 == Building on macOS ==

@@ Line 85: / Line 85: @@
 by typing
 <syntaxhighlight lang="bash">
-sudo ln -s /usr/include/hdf5/serial/ /usr/include
+sudo ln -s /usr/include/hdf5/serial/* /usr/include
 </syntaxhighlight>
 After this, there should be no compile time errors. If there are, please raise an issue.
@@ Line 99: / Line 99: @@
 or fix the problem permanently by soft-linking
 <syntaxhighlight lang="bash">
-sudo ln -s /usr/lib/x86_64-linux-gnu/hdf5/serial/ /usr/lib
+sudo ln -s /usr/lib/x86_64-linux-gnu/hdf5/serial/* /usr/lib
 </syntaxhighlight>