MM-COMMON-PREPARE(1)
π MM-COMMON-PREPARE π
okay bestie, so you're a C++ binding module and you wanna hang out with mm-common and Autotools? say less. the manual name is mm-common-prepare and this is literally the whole vibe.
β¨ NAME β¨
mm-common-prepare β Prepare a C++ binding module to use mm-common and Autotools
πΈ SYNOPSIS πΈ
mm-common-prepare [OPTION]... [SOURCE-DIR]
π¦ DESCRIPTION π¦
Run mm-common-prepare and it literally just copies the mm-common build support files into the source tree of a C++ binding module. that's the whole job. it's giving personal assistant. π«Ά
but where exactly do those files land? plot twist: it depends on special macros in your configure.ac file. so the location is influenced, not random.
AC_CONFIG_AUX_DIR([AUX-DIR])
The Automake include files get placed into the AUX-DIR subdirectory of the top-level source directory. and if AC_CONFIG_AUX_DIR isn't specified at all? no worries, the files just chill at the top-level of the module's source tree. main character placement honestly.
MM_CONFIG_DOCTOOL_DIR([DOCTOOL-DIR])
If the MM_CONFIG_DOCTOOL_DIR macro is called with an explicit DOCTOOL-DIR argument, then the common utilities needed for generating and installing the reference documentation of a C++ binding module get copied to that named subdirectory. π
But β and this is the important part β if MM_CONFIG_DOCTOOL_DIR is not used, or it doesn't specify a DOCTOOL-DIR argument, then mm-common-prepare will not copy the documentation utility files into the module's source tree. Instead, it's assumed the module depends on mm-common and can just use the installed documentation utilities that come with it. lowkey iconic of it to not duplicate work.
If no SOURCE-DIR argument has been specified on the command line, the current working directory will be used. yes bestie, it defaults to where you already are. cozy.
π OPTIONS π
-c,--copyβ copy files instead of creating symbolic links to them-f,--forceβ forcefully replace existing files or symbolic links--helpβ display a help message and exit--versionβ show version information and exit
π EXIT STATUS π
The exit status is 0 if OK, or 1 if an error occurred. no in-between, no drama, just binary. slay.
π FILES π
The build support files currently copied by mm-common-prepare are listed below. manifest moment.
Automake include files copied to AUX-DIR:
compile-binding.am
dist-changelog.am
doc-reference.am
generate-binding.am
Documentation utilities copied to DOCTOOL-DIR:
doc-install.pl
doc-postprocess.pl
doxygen.css
doxygen-extra.css
tagfile-to-devhelp2.xsl
π₯ SEE ALSO π₯
autoreconf(1),mm-common-get(1)/usr/share/doc/mm-common/README/usr/share/doc/mm-common/skeletonmm.tar.xzor/usr/share/doc/mm-common/skeletonmm.tar.gz
ngl, if you're setting up a fresh module, go peek at the skeleton tarball. it's giving template energy. π
and that's a wrap, bestie!! this was mm-common-prepare from mm-common 1.0.8, dated 2014-08-13, brought to you by the good people at GNOME. periodt. πβ¨
π¦ where this page comes from
- arch rolling: mm-common 1.0.8-1 Β· GPL-2.0-or-later
- fedora 43: mm-common 1.0.8-1.fc43 Β· GPL-2.0-or-later
- fedora 44: mm-common 1.0.8-1.fc44 Β· GPL-2.0-or-later
- ubuntu stonking: mm-common 1.0.8-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms