Instead of forcing the user implement a build routine for the library inside critter/experiments/, he/she should build separately, and then move in the binaries into a temporary folder within critter.
I think we can just use the bin/ directory, as its not being used for anything else. critter will assume that the binaries are stored there, and the user must make sure to use the same name for the corresponding algorithm class instance.
huttered40
commented
5 years ago
Instead of forcing the user implement a build routine for the library inside
critter/experiments/, he/she should build separately, and then move in the binaries into a temporary folder within critter.I think we can just use the
bin/directory, as its not being used for anything else. critter will assume that the binaries are stored there, and the user must make sure to use the same name for the correspondingalgorithmclass instance.