Updates dockerlizard and cMake -- fixes #68 #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

The existing docker build and cmake build were not really using cmake to its fullest. This creates and builds
libsparselizard.soand has a Dockerfile that'll install it to a GNU-style directory tree in/usr/localYou can override where it finds libraries by changing the
CMAKE_PREFIX_PATH(orCMAKE_INCLUDE_PATH+CMAKE_LIBRARY_PATH) to wherever your custom libs and includes are.LD_LIBRARY_PATHorRPATHwould need to change for runtime loading.In addition, this makes it possible to cleanly build using system libs on both macOS and linux, which will make it much easier for
sparselizardto be packaged into distributions.The docker container that is built is barebones, but it is still good enough to allow for VS Code "remote container" style development. It's best used as a starting point for customization.
Effectively supersedes #50