babashka

Author	SHA1	Message	Date
Thiago Kenji Okada	14e053e0a3	Add BABASHKA_MUSL build variable (#834 ) This allows building a Babashka binary using musl C libraries instead, instead of hardcoding this accordingly to the CPU arch.	2021-05-11 00:10:11 +02:00
Michiel Borkent	3800245849	musl	2021-05-10 23:03:46 +02:00
Michiel Borkent	34bbea0204	Move setup-musl to .circleci scripts (#833 )	2021-05-10 22:46:32 +02:00
Thiago Kenji Okada	ddc900a656	Build BABASHKA_STATIC with musl C library (#828 ) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.	2021-05-09 23:30:27 +02:00