How to get regular stuff working: Difference between revisions
| Line 9: | Line 9: | ||
Compiling in Alpine may be more challenging because it uses [http://www.musl-libc.org/ musl-libc] instead of glibc. Please review [http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc 'The functional differences with glibc' ] if you think of porting packages or just for the sake of knowing, of course. | Compiling in Alpine may be more challenging because it uses [http://www.musl-libc.org/ musl-libc] instead of glibc. Please review [http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc 'The functional differences with glibc' ] if you think of porting packages or just for the sake of knowing, of course. | ||
==== (unvalidated) apk packages to install so one can start building software ==== | ==== (unvalidated) apk packages to install so one can start building software ==== | ||
| Line 17: | Line 16: | ||
apk add cmake cmake-doc extra-cmake-modules extra-cmake-modules-doc | apk add cmake cmake-doc extra-cmake-modules extra-cmake-modules-doc | ||
==== ccache is also available ==== | |||
apk add ccache ccache-doc | |||
Revision as of 19:23, 31 January 2016
Man pages
Not all man-pages are in Alpine, those who are are not readily available after installing man and man-pages, you also need to install mdocml-pages to have man pages built at install time. Below is the quick and easy commandline:
apk add man man-pages mdocml-pages
a few notes and a reminder on Compiling
Compiling in Alpine may be more challenging because it uses musl-libc instead of glibc. Please review 'The functional differences with glibc' if you think of porting packages or just for the sake of knowing, of course.
(unvalidated) apk packages to install so one can start building software
apk add build-base gcc abuild
a complete install for cmake looks like
apk add cmake cmake-doc extra-cmake-modules extra-cmake-modules-doc
ccache is also available
apk add ccache ccache-doc