Currently, building txn_box requires an installed ATS, OpenSSL, and possibly other dependencies.
This is difficult in my build system, because we want to build txn_box at the same time as ATS, and don't have an installed ATS to work with.
We also don't have network available at build time, so currently the txn_box build must be built at some point before our ATS build. This would be mitigated by https://github.com/SolidWallOfCode/txn_box/issues/84 .
But I'd really like to be able to build from dependency sources instead of installations. I believe txn_box just needs headers, not binaries, so this should theoretically be possible.
The build could either take flags for each particular dependency, including sub-dependencies like ATS's yamlcpp (which is in a different location than other headers in ATS source). Or alternatively, maybe the build could take a generic arg or set of args for any given dependency, as a "header include path." Then users could specify all their paths - ATS core, ATS yamlcpp, OpenSSL, etc. This would be made easier by #84 as well, which would let users easily see what dependencies they need to provide paths for.
Currently, building txn_box requires an installed ATS, OpenSSL, and possibly other dependencies.
This is difficult in my build system, because we want to build txn_box at the same time as ATS, and don't have an installed ATS to work with.
We also don't have network available at build time, so currently the txn_box build must be built at some point before our ATS build. This would be mitigated by https://github.com/SolidWallOfCode/txn_box/issues/84 .
But I'd really like to be able to build from dependency sources instead of installations. I believe txn_box just needs headers, not binaries, so this should theoretically be possible.
The build could either take flags for each particular dependency, including sub-dependencies like ATS's yamlcpp (which is in a different location than other headers in ATS source). Or alternatively, maybe the build could take a generic arg or set of args for any given dependency, as a "header include path." Then users could specify all their paths - ATS core, ATS yamlcpp, OpenSSL, etc. This would be made easier by #84 as well, which would let users easily see what dependencies they need to provide paths for.