Frequently Asked Questions
Building and Compiling PALISADE
Issue: When I checkout a different branch I see the following:
Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: third-party/cereal (new commits) modified: third-party/google-benchmark (new commits) modified: third-party/google-test (new commits)
git submodule update --recursive
It makes the version in your directory match the version in the
.gitmodules file. Will trigger a re-build of some material, but not the GMP or NTL direcories.
Throwing exceptions within critical sections or Open MP threads.
Exceptions thrown inside of a critical region, or inside of an omp thread, must be caught in the same thread where thrown, or Bad Things Happen.
This can happen infrequently, but needs to be addressed. Two active issues #42 and #56 are tracking this. The plan is to implement a special exception handler to deal with this condition, slated for the 1.10 release.