I found, the hard way, that at least boost::program_options
is dependent of the compiler configured structure member alignment.
If you build boost using default settings and link it with a project using 4 bytes alignment (/Zp4
) it will fail at runtime (made a minimal test with program_options). Boost will generate an assert indicating a possible bad calling convention but the real reason is the structure member alignment.
Is there any way to prevent this? If the alignment makes the code incompatible shouldn't this be included in library naming?
You need to ensure that your program and the libraries you link with have the same ABI.
The number of compiler switches that can alter the ABI of C++ classes and functions could be too large so it is clearly a problem to name more than 3000 combinations.
You could take a look here for a more detailed rationale.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With