Prepare for updated toolchains

[chouquette]

This PR contains some preliminary work for DataDog/datadog-agent#28262

It fixes implicit linking with our libraries dependencies, and allows us to chose a different compiler that the default gcc/g++ without having to override the environment variable globally.

[spencergilbert]

🥜 nitpick: ‏ since this comment seems to apply to all the if statements, it should be moved to a more "global" place, or duplicated per.

[chouquette]

Good point, I took the opportunity to attempt another approach which will allow simpler additional variables if we need them

[datadog-datadog-prod-us1]

⚪ Code Quality Violation

Consider using symbols instead of string hash keys (...read more)

In Ruby, it is a best practice to use symbols instead of strings as hash keys. This rule emphasizes that it's more efficient and idiomatic to use symbols for this purpose. Symbols are immutable and unique, which makes them ideal for identifying things, whereas strings are mutable and can create multiple objects for the same sequence of characters.

The importance of this rule lies in the performance and memory usage of your Ruby application. Using symbols as hash keys reduces memory usage because they are stored in memory only once during a Ruby process. This can make a significant difference in the efficiency of your application, especially when dealing with large data sets.

To ensure you're following good coding practices, always use symbols for hash keys unless there's a specific reason to use a string. A simple refactoring from values = { 'foo' => 42, 'bar' => 99, 'baz' => 123 } to values = { foo: 42, bar: 99, baz: 123 } will make your code compliant with this rule. This not only improves your code's performance but also makes it more readable and consistent with Ruby's conventions.