Change concept of ULINUX (for universal SSL build, always build ULINUX) #4
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.
Significant changes to how SCXCore agent deals with ULINUX. In the past,
--enable-ulinux meant two things: Build universal binaries (that can run
anywhere based on Linux features and not based on platform #ifdefs), and
build for universal SSL installations (link against both versions of SSL).
Now --enable-ulinux only builds for universal SSL installations. We will
always build universal binaries. This eliminates Redhat/SuSE-specific kits.
Other changes along the way:
lots of superflous stuff isn't copied on every system build to our
build archives.
universal binary is a universal binary, regardless of DPKG vs. RPM
packaging. This squashes the universal_r/universal_d naming convention.
option, making it easier for packages that need this to specify it.
Currently, this qualifier also disables "mega-bundles". The assumption
is that, if you want a lightweight agent without the listener, you
likely want to handle mega-bundles (bundles with other components)
yourself, rather than to assume SCXCore behavior.
abort the build if a bundle build problem was encountered.
In the past, many unit tests would fail on CentOS platforms.
@MSFTOSSMgmt/omsdevs