On 7/19/21 1:56 PM, Corbin Foucart wrote:
    
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdealii.org%2Fparticipate.html&data=04%7C01%7CWolfgang.Bangerth%40colostate.edu%7C96b24c1d9f0a4fbe746e08d94aef5069%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C637623213971258194%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NtX0aKBoVNC7XEJqVCSfSzLUlY4NU1j%2BIqje6JwMZ54%3D&reserved=0>


I'm ready to start working on this. I've read the participation FAQ, forked the repo, etc. This might be a basic question, but how should I go about re-compiling the library code once I've made changes to the source? Is there a makefile that makes and runs all the unit tests? I presume the new code that I use to test the functions should be added in dealii/tests/feinterface?

You build deal.II from a build directory and call
  cmake <SOURCE_DIR> && make
See here:
  https://dealii.org/readme.html

To run the test suite, you'd then do the following steps in your build 
directory:
  make setup_tests
  ctest
or, if you only want to run tests in debug mode, then
  ctest -R debug
That last step will take many hours on a single-processor machine. If you have enough cores, you can do
  ctest -j80 -R debug
and it will finish in about 30 minutes, but you really do need 80 cores for 
that.

Best
 W.


--
------------------------------------------------------------------------
Wolfgang Bangerth          email:                 [email protected]
                           www: http://www.math.colostate.edu/~bangerth/

--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dealii/1e6ce64a-8ed3-a854-f2d0-50a241f58b0b%40colostate.edu.

Reply via email to