-
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
Feature/header #240
Feature/header #240
Conversation
…#226) - create one file per public feature - split gmsh.hpp, functionspace.hpp - move options to feel/options.cpp - remove some .cpp files that were dealing with program_options
use TSBase as base class update issue #237
Conflicts: feel/feeldiscr/functionspace.hpp
Merge branch 'feature/header' of https://github.com/feelpp/feelpp into feature/header # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
Conflicts: feel/feeldiscr/functionspace.hpp feel/feeldiscr/projector.hpp
added more precision
- introduce bdf->priorTimes() to initialize bdf, see testsuite/feeldiscr/test_bdf2 for an example - change behavior of order change, use directly bdf order but requires initialization of priorTimes()
…ailures by half) see #88
Feel++ Consortium » feelpp #135 FAILURE |
it compiles now, it needs however to be tested
Note that at this stage doc, testsuite and benchmarks are compiling 100%. |
Feel++ Consortium » feelpp #138 FAILURE |
@StephaneVeys at this stage applications/crb compiles (and should run too). The changes were minor. At some point the call to the deprecated constructor of |
Conflicts: feel/feeldiscr/createsubmesh.hpp
Feel++ Consortium » feelpp #141 FAILURE |
Feel++ Consortium » feelpp #142 FAILURE |
Conflicts: feel/feelmesh/elements.hpp
we could eventually define a variable FEELPP_MAX_NPROCS so that the user/dev can set it
added headers for backward compatibility
Feel++ Consortium » feelpp #175 FAILURE |
This branch reorganizes some of the header and split them. We would need now to avoid including
which brings the full library in the user scope but rather select only the necessary headers. This requires documentation and in particular an update of the tutorial and the quick reference which would both state properly the needed header file for each feature.
For example ;
Pch<N>(mesh)
then we need to include#include <feel/feeldiscr/pch.hpp>
loadmesh()
then we need to include#include <feel/feelfilters/loadmesh.hpp>