-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganisation of feelpp repo #1734
Comments
prudhomm
added a commit
that referenced
this issue
Nov 23, 2021
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
- moved pyfeelpp* to python component - adapted the CMakeLists.txt
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
adapted the CMake files to the python component
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
new presets - feelpp-python - feelpp-python-dbg removed pyfeelpp-all
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
fix build process update buildkite/docker add python component in buildkite/docker
5 tasks
prudhomm
added a commit
that referenced
this issue
Mar 14, 2022
fix component name use FEELPP_PYTHON
prudhomm
added a commit
that referenced
this issue
Mar 18, 2022
- enable ctest - update packaging feelpp and its component: fix package name - embed spdlog and taskflow as sumbodule to avoid fetching in deb buildong (forbidden)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
feelpp is organized in components:
feelpp
toolboxes
mor
python [pyfeelpp,pyfeelpp-toolboxes,pyfeelpp-mor]
examples
benchmarks
More components may appear in the future
feelpp is built component-wise and component may depend on other components, eg toolboxes depend on feelpp, mor depends on toolboxes, python depends on feelpp, toolboxes and mor.
Each component should have a
tests
directory with a testsuite to be run. C++ based components may use boost.testsuite The python component should usepytest
to define the testsuiteExample include quickstart and doc/manual codes
testsuite should be split between feelpp and mor
feelpp crb/eim/pbdw headers should be moved to mor
toolboxes should be organized component wise
core toolbox should be created with modelcore and modelmesh
deb and docker packages should be created component wise
Some explanations are in the pdf file attached .
The text was updated successfully, but these errors were encountered: