Commit d716f36f authored by GILLES Sebastien's avatar GILLES Sebastien
Browse files

#859 README.md: replace a Markdown link by a html one to remove an issue with...

#859 README.md: replace a Markdown link by a html one to remove an issue with Doxygen, which couldn't interpret the Markdown link and therefore issued a warning. Also add some http:// prefix to disambiguate some links.
parent a2a7f41b
......@@ -115,7 +115,7 @@ The [ThirdPartyCompilationFactory](https://gitlab.inria.fr/MoReFEM/ThirdPartyCom
Four libraries are embedded in MoReFEM directly (and their compilation is already handled through MoReFEM different builds systems):
- [TClap](http://tclap.sourceforge.net), a header-only library to handle command line arguments.
- [Seldon](seldon.sourceforge.net), a linear algebra C++ library used to hande small matrices and vectors in MoReFEM. We foresee to benchmark this library against [Xtensor](https://github.com/QuantStack/xtensor) and [Eigen](eigen.tuxfamily.org).
- [Seldon](http://seldon.sourceforge.net), a linear algebra C++ library used to hande small matrices and vectors in MoReFEM. We foresee to benchmark this library against [Xtensor](https://github.com/QuantStack/xtensor) and [Eigen](http://eigen.tuxfamily.org).
- [Ops](https://gitlab.com/libops), a C++ library for reading configuration files.
- [Libmesh](http://pages.saclay.inria.fr/loic.marechal/libMeshb.html), a mesh utility.
......@@ -255,7 +255,7 @@ If an item begins with a user name in braces (e.g. {sgilles}), you do not need t
The other items are all related to the branch __develop__ of the main MoReFEM repository; this branch is the one onto which new mature modifications not yet pushed onto master are put.
See [the dedicated README](Documentation/ContinuousIntegration/README.md) to learn more about it (user and administrator alike).
See <a href="Documentation/ContinuousIntegration/README.md">the dedicated README</a> in Documentation/ContinuousIntegration directory to learn more about it (user and administrator alike).
It's highly likely that at some point in the future we switch to gitlab-ci: Jenkins is really cumbersome to maintain and the tools to interact with the outcome are not that great (they were the reason I tried Jenkins first). Furthermore, gitlab-ci would allow to follow in the repository the state of the configuration files (for Jenkins I rely on screenshots put in the Documentation folder...)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment