The qtargets.mk include file has the linking and installation rules.
You can inspect and/or set the following macros when you use
qtargets.mk:
- INSTALLDIR
- The subdirectory where the executable or library is to be installed.
Defaults to bin for executables, and lib/dll for DLLs.
If you set it to /dev/null, then no installation is done.
- USEFILE
- The file containing the usage message for the application.
Defaults to none for archives and shared objects and to
$(PROJECT_ROOT)/$(NAME).use for executables.
The application-specific makefile can set the macro to a null string,
in which case nothing is added to the executable.
- LINKS
- A space-separated list of symbolic link names that are aliases for the image being installed.
They're placed in the same directory as the image.
The default is none.
- PRE_TARGET, POST_TARGET
- Extra targets to add as dependencies to the all target before and after the main target.
- PRE_CLEAN, POST_CLEAN
- Extra commands to run before and after the clean target.
- PRE_ICLEAN, POST_ICLEAN
- Extra commands to run before and after the iclean target.
- PRE_HINSTALL, POST_HINSTALL
- Extra commands to run before and after the hinstall target.
- PRE_CINSTALL, POST_CINSTALL
- Extra commands to run before and after the cinstall target.
- PRE_INSTALL, POST_INSTALL
- Extra commands to run before and after the install target.
- PRE_BUILD, POST_BUILD
- Extra commands to run before and after building the image.
- SO_VERSION
- The SONAME version number to use when building a shared object (the default is 1).
- PINFO
- Information to go into the *.pinfo file.
For example, you can use the PINFO NAME option to
to keep a permanent record of the original filename of a binary.
If you use this option, the name that you specify appears in the
information from the use -i filename command.
Otherwise, the information from use -i contains the
NAME entry specified outside of the PINFO
define.
For more information about PINFO, see the
hook_pinfo()
function described below for the GNU configure command.