Changes between Version 10 and Version 11 of HaikuPorterForPM/BuildRecipes

Timestamp:

07/15/13 08:26:28 (2 years ago)

Author:

bonefish

Comment:

--

HaikuPorterForPM/BuildRecipes

@@ -32 +32 @@
  - '''$dataDir:''' The absolute directory for data.
  - '''$dataRootDir:''' The absolute base directory for data. On Haiku, this is the same as `$dataDir`.
+ - '''$debugInfoDir:''' The absolute path to the directory for debug info files.
  - '''$developDir:''' The absolute path to the directory underneath of which all development-related files should be put.
  - '''$developDocDir:''' The absolute base directory for development-related documentation specific to the port being built. Documentation in html- or pdf-format should be put here, manpages should be put into `$manDir`.
@@ -40 +41 @@
  - '''$haikuVersion:''' The version of Haiku for which the port is being built.
  - '''$includeDir:''' The absolute directory for header files
- - '''$infoDir:''' The absolute directory for documentation in `info`-format (which is frowned upon by Haiku ports)
+ - '''$infoDir:''' The absolute directory for documentation in `info`-format (which is frowned upon by Haiku ports).
+ - '''$installDestDir:''' An absolute path that shall be prepended to all absolute installation paths (when they are dereferenced, i.e. usually only in the 'INSTALL' function) and should be set as the 'DESTDIR' for 'make install'. This only needs to be done in the !HaikuPorts cross building repository.
  - '''$isCrossRepository:''' Is `true` if the ports tree being used is the one dealing with cross-building the bootstrap packages.
  - '''$jobArgs:''' If !HaikuPorter has been invoked with `--jobs=<num>`, this contains the job-number specification applicable to make (i.e. `-j<num>`)
@@ -66 +68 @@
  - '''$relativeDataDir:''' `$dataDir` as a relative directory (to `prefix`).
  - '''$relativeDataRootDir:''' `$dataRootDir` as a relative directory (to `prefix`).
+ - '''$relativDebugInfoDir:''' `$debugInfoDir` as a relative directory (to `prefix`).
  - '''$relativeDevelopDir:''' `$developDir` as a relative directory (to `prefix`).
  - '''$relativeDevelopDocDir:''' `$developDocDir` as a relative directory (to `prefix`).
@@ -118 +121 @@
  - '''appPath:''' The absolute path to the application executable.
  - '''entryName:''' The name of the application as it shall appear in the Deskbar. Can be omitted, in which case the file name of the application executable is used.
+
+==== defineDebugInfoPackage() ====
+
+ usage:: `defineDebugInfoPackage [ --directory <toDirectory> ] <basePackageName> <path> ...`
+ purpose:: Defines a debug info package for another package. Must be invoked at top level (i.e. not in one of the action functions). The specified base package contains the specified files from which debug infos shall be extracted. At the end of the installation phase (i.e. after 'INSTALL' returns) the debug infos are extracted into separate files and moved into a respective debug info package.
+ params::
+ - '''toDirectory:''' The path to the directory where the debug info files shall be placed. The default is '$debugInfoDir'.
+ - '''basePackageName:''' The name of the base package the files belong to. This also defines the name of the debug info package ('<basePackageName>_debuginfo') and its dependency.
+ - '''path:''' The path to a file from which the debug info shall be extracted. An arbitrary number of files can be specified.
+
+==== extractDebugInfo() ====
+
+ usage:: `extractDebugInfo <path> <debugInfoPath>`
+ purpose:: Extracts the debug info from a file into a debug info file.
+ params::
+ - '''path:''' The path to the file from which to extract the debug info.
+ - '''debugInfoPath:''' The path of the to-be-created debug info file. The containing directory (and all missing ancestor directories) are created, if necessary.
 
 ==== fixDevelopLibDirReferences() ====