defensivedepth
08/18/2022, 1:51 AM4.9
44mb ------> 5.0
196mb ?sharvil
08/18/2022, 1:57 AMseph
Stefano Bonicatti
08/18/2022, 9:34 AMeu-unstrip
.defensivedepth
08/18/2022, 11:41 AMStefano Bonicatti
08/18/2022, 1:10 PMseph
Mike Myers
08/18/2022, 5:11 PMosquery-codesign
and things tend to get bottlenecked thereseph
Stefano Bonicatti
08/18/2022, 6:21 PMMike Myers
08/18/2022, 6:31 PMosquery/osquery
can help, sounds like it can be done in a GitHub Actions workflowdefensivedepth
04/14/2023, 12:38 AMseph
Stefano Bonicatti
04/14/2023, 9:04 AMinstall
target) to install files in its own intermediate directory, to then run (some of) the native packaging tools.
Normally stripping would be controlled when installing, when you’re using CMake only and not creating a package. CPack takes control of that and by default is disabled, and lets the native tools deal with that, especially so they can split debug info out.osquery-packaging
, and instead we should simply add an option that decides if to strip or not when creating the TGZ. Which means that the CI will have to run cpack an additional time for a tgz without debug symbolsCPACK_STRIP_FILES
variable to set, which is documented in the link I gave aboveosquery-packaging
project and just act on the CI, passing CPACK_STRIP_FILES
via command line, after adding a second run for a TGZ package.osquery
CI workflowosquery
CI workflow run and upload it to the github releaseosquery-packaging
CMake, then we have to move this if
, from the CI workflow to the osquery-packaging
CMake logic.