In the current form, Crypto++ will compile the library with optimal settings for the current build machine. 

However in many cases (as mine) we need to compile a generic version of the library such that the resulting binary can be redistributed. 

If Crypto++ is build on a high end machine and then shipped to a client with old hardware, it is very likely that the application will crash with an instruction unknown. 

It would be very useful if a target (-march=target) platform could be defined somewhere that would define all instruction sets supported. In this case all hardware tests should be ignored. 
Crypto++ needs to support a fixed target
This is a GitHub Issue
repo:cryptopp
owner:weidai11
Title : Crypto++ needs to support a fixed target
Issue date:

--- start body ---
In the current form, Crypto++ will compile the library with optimal settings for the current build machine. 

However in many cases (as mine) we need to compile a generic version of the library such that the resulting binary can be redistributed. 

If Crypto++ is build on a high end machine and then shipped to a client with old hardware, it is very likely that the application will crash with an instruction unknown. 

It would be very useful if a target (-march=target) platform could be defined somewhere that would define all instruction sets supported. In this case all hardware tests should be ignored. 
--- end body ---
