[PROF-10241] Extract libdatadog crashtracker telemetry into separate extension #3824
Commits on Aug 2, 2024
-
Bootstrap libdatadog_api native extension
This extension will be used to call libdatadog APIs without needing to go through profiling.
-
Setup libdatadog_api linking based on profiling stuff
There's a lot of copy-pasta and I'm not entirely happy. Let's go with it for now, to get it moving.
-
Successful experimental extraction of crashtracker to new module
The specs still pass! :)
-
Introduce new
datadog_ruby_common.h/.cfor common bits between exte……nsions This cleans up the wad of copy-pasted code I did for my first attempt.
-
Adopt new
datadog_ruby_common.h/.cfor profiling native extensionThese new files just moved things around from where they were in the profiler, and other than minimal cleanups, they are the same stuff.
-
-
We need to use these features in extconf, so let's tell rubocop to stop annoying us about it.
-
Extract
libdatadog_folder_*into helper that can be shared between ……extensions Let's reduce the copy-pasta!
-
Extract
pkg_config_missing?tolibdatadog_extconf_helpersThis also included adding a `skip_building_extension!` to `libdatadog_api/extconf.rb` so we can properly handle pkg-config failures like the profiler extension does.
-
Extract
try_loading_libdatadogtolibdatadog_extconf_helpersThis was the last bit that had been copy-pasta'd from the profiler native extension into the `libdatadog_api/extconf_helpers` and thus we are now sharing most of the extconf helpers.
-
Tag extension builds with only major.minor, skipping Ruby patch version
This makes it easy to use the same prebuilt extension across multiple Ruby patch versions.
-
Inline
Init_libdatadog_apiintocrashtracker.cOne less file, and we can always extract it again later.
-
-
-
