-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build improvements: Dynamic builds #963
Comments
Here's the action plan in form of the dependencies we have. Dates in the
Appendix
|
For future documentation purposes, to build, Falco also requires the openssl binary to be available in the system when using the new dynamic configuration. |
We might want to check out the AUR as well once this is simplified |
Another dependency we need to have is the |
What would you like to be added:
At the moment, the main Falco
CMakeLists.txt
and its children have hard-coded compilation flags to always compile falco as a static binary.While has its advantages (no extra dependencies), using static binaries as a packaging medium can be cause of any sort of issues, like:
Of course, one might say: "Yes but packaging becomes more difficult"
I would argue with that, we have three main distribution mediums:
For the rpm and deb package we can easily declare their dependencies in them instead.
For the container image we can install the needed dependencies directly in the container.
This does not affect the kernel module and the bpf probe. FTR I'm trying to refactor the bpf probe in a "compile once and run everywhere" fashion in issue #942 .
Why is this needed:
Because we all deserve better builds.
The text was updated successfully, but these errors were encountered: