Quick question regarding make apk
and abuild -r
?
make apk
target, I will see what that does and get back to you, if you happen to know please let me know.
and abuild -r
is an alpine specific tool? what does it require?
So, after the additions for packaging, i hope this will be an easy transition:
Configure as
cmake -S . -B build-alpine -DCMAKE_INSTALL_PREFIX=/usr -DVERBOSE=off -DBUILD_DOC=OFF --fresh -DEXCLUDE_MODULES="db_oracle dnssec jwt microhttpd nats nsq ruxc secsipid_proc stirshaken tls_wolfssl app_lua" -DCMAKE_BUILD_TYPE="Release" -DMODULE_GROUP_NAME="ALL_PACKAGED" -DINCLUDE_MODULES=""
BUILD_DOC=OFF
, no documentation/man will be built
CMAKE_BUILD_TYPE=Release
built release type, you can change to DEBUG
, if you want debugging symbols.
MODULE_GROUP_NAME="ALL_PACKAGED"
will built all groups defined in groups.cmake
and when packaging it will create a separate deb for each. (these probably don't apply to alpine.) You can use KSTANDARD
and KMINI
as well every K{group_name}
if you want a specific group.
Then for building and installing:
Build:
cmake --build build-alpine -j8
--
If you want to install for staging then you can use:
DESTDIR=/tmp/alpine-pkg cmake --install build-alpine
Here you will find all installed files.
No extra files should be installed if you have not build manually the man/dbschema. Regarding docs, since we are installing the ones provided from src code directly, and not building them, you can exclude the docs folder created I guess.
If these are not enough to get you started, ping me again until I can see the apk
target.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.