mirror of the now-defunct rocklinux.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

283 lines
10 KiB

  1. # --- ROCK-COPYRIGHT-NOTE-BEGIN ---
  2. #
  3. # This copyright note is auto-generated by ./scripts/Create-CopyPatch.
  4. # Please add additional copyright information _after_ the line containing
  5. # the ROCK-COPYRIGHT-NOTE-END tag. Otherwise it might get removed by
  6. # the ./scripts/Create-CopyPatch script. Do not edit this copyright text!
  7. #
  8. # ROCK Linux: rock-src/scripts/config.hlp
  9. # ROCK Linux is Copyright (C) 1998 - 2004 Clifford Wolf
  10. #
  11. # This program is free software; you can redistribute it and/or modify
  12. # it under the terms of the GNU General Public License as published by
  13. # the Free Software Foundation; either version 2 of the License, or
  14. # (at your option) any later version. A copy of the GNU General Public
  15. # License can be found at Documentation/COPYING.
  16. #
  17. # Many people helped and are helping developing ROCK Linux. Please
  18. # have a look at http://www.rocklinux.org/ and the Documentation/TEAM
  19. # file for details.
  20. #
  21. # --- ROCK-COPYRIGHT-NOTE-END ---
  22. COMMENT_ARCHCPUOPT
  23. In this section you are able to select the architecture, the CPU and
  24. whether you are cross-building/porting to another architecture.
  25. COMMENT_TARGET
  26. In this section you can select which distribution target you would like
  27. to use.
  28. COMMENT_BUILD_SYS_CONF
  29. Here you can set some basic options for our beautiful distribution
  30. build system.
  31. ROCKCFG_ARCH
  32. This option controls the target architecture like alpha, ia64, mips,
  33. ppc, sparc or x86.
  34. ROCKCFG_CROSSBUILD
  35. This option needs to be selected to perform a cross-build to another
  36. architecture.
  37. ROCKCFG_DISABLE_BROKEN
  38. If you select this option packages that have not built in the last
  39. referency build will not be built.
  40. ROCKCFG_TARGET
  41. Please select the Target you want to build. Here's a short overview:
  42. - Boot-, Install- and Rescue-System:
  43. The boot-system. You need this if you want to install the system
  44. you built with CD or floppy-disk.
  45. - Desktop ROCK Linux:
  46. Intended for use on workstations / desktops.
  47. - Diet LibC based ROCK Linux:
  48. A distribution using Diet LibC instead of GLibC. DietLibC is
  49. a light-weight C-Library useful for embedded systems and other
  50. low-memory devices.
  51. - Epiam ROCK Linux:
  52. A distribution specially for VIA Epiam processors.
  53. - Generic ROCK Linux:
  54. A generic, all-purpose distribution that has simply everything.
  55. - ROCK Linux LiveCD:
  56. A system that can boot and run directly from CD without the need
  57. to install anything on a hard disk.
  58. - ROCK Linux Video Player (lvp):
  59. A distribution that works as a video player and boots from CD.
  60. - Minimal ROCK Linux:
  61. A basic system that has only minimally more than a LFS.
  62. - Reference-Build for creating *.cache files:
  63. This target is for internal use only. It's purpose is to create
  64. package/*/*/*.cache files which are used to validate a package
  65. and consolidate its various information.
  66. - ROCK Router Linux:
  67. This is a _very_ minimal system with only routing-capabilities.
  68. - ROCK Linux Server:
  69. This target is intended to build a not blown up server distribution
  70. to install web-, mail-, fileserver or similar.
  71. ROCKCFG_PARALLEL
  72. Select this option if you want to perform a parallel build on several
  73. machines or if you build on a multiprocessor machine.
  74. See Documentation/BUILD-CLUSTER for more details.
  75. ROCKCFG_PARALLEL_MAX
  76. This options controls the maximum number of simultaneous build jobs.
  77. ROCKCFG_PARALLEL_ADDJOB
  78. If you're using an external command scheduler, enter it here.
  79. See Documentation/BUILD-CLUSTER for more details.
  80. ROCKCFG_ABORT_ON_ERROR
  81. If selected the build will stop on each package build error.
  82. ROCKCFG_RETRY_BROKEN
  83. This options controls whether the Build-System should try to build a
  84. package that has not built flawlessly during the last build.
  85. ROCKCFG_DISABLE_BROKEN
  86. Please check here if you want to skip building packages which are marked
  87. as broken. Note that this differs from ROCKCFG_RETRY_BROKEN. The reason
  88. a package is deemed 'broken' can also be missing *.cache file or others.
  89. ROCKCFG_ALWAYS_CLEAN
  90. When a package built flawlessly then the temporary directory which was
  91. used for building is deleted. Select this options if you also want this
  92. cleanup for packages with build error. (This safes disk-space but makes
  93. debugging hard ...)
  94. ROCKCFG_XTRACE
  95. Please check here if you want additional (debug)-output in the build
  96. log-files.
  97. ROCKCFG_SRC_TMPFS
  98. Check here if you want package builds to use tmpfs instead of the regular
  99. filesystem on which ROCK resides.
  100. ROCKCFG_SRC_TMPFS_OPT
  101. Please enter the tmpfs mount options here. For example:
  102. size=800M,nr_inodes=100k
  103. will mount an 800 Megabyte tmp-filesystem with 100,000 inodes.
  104. size=4G,nr_inodes=500k
  105. will mount a 4 Gigabyte tmp-filesystem with 500,000 inodes.
  106. Please make sure that the filesystem is big enough to hold
  107. - package-sources (unpacked)
  108. - compile-time binaries
  109. - and the binary package
  110. The filesystem size also must not be so big as to hog all your RAM or
  111. else your system might crash or start swapping.
  112. ROCKCFG_SRC_TMPFS_LOG
  113. Please enter the path to the tmpfs logfile.
  114. ROCKCFG_EXPERT
  115. This button will enable a lot of additional configuration options.
  116. Some of these will make small changes to what the system will look
  117. like while others will have a huge impact on performance, stability
  118. and usability of the final system.
  119. Don't touch these if you don't know what you are doing.
  120. YOU HAVE BEEN WARNED!
  121. ROCKCFG_CREATE_TARBZ2
  122. If selected binary packages in .tar.bz2 format will be created.
  123. ROCKCFG_CREATE_GEM
  124. If selected binary packages in .gem format will be created.
  125. ROCKCFG_PKGFILE_VER
  126. If selected the package version number will be added to the binary
  127. package filenme.
  128. ROCKCFG_PKGSEL
  129. If selected you can modify the package list for the build.
  130. MENU_PKGSEL_RULES
  131. Here you can modify the package list for the build. You have the
  132. choice beween enable, disable or complete removal. A disabled
  133. package can still be reenabled by a target, while a removed one
  134. can not be selected by a target.
  135. Use "X <pattern>" to enable packages
  136. Use "O <pattern>" to disable packages
  137. Use "- <pattern>" to remove packages
  138. For example:
  139. "- gnome*"
  140. will not build Gnome at all.
  141. ROCKCFG_SHOW_PKGLIST
  142. This will display the complete, current package list.
  143. ROCKCFG_CONFOPT_FILE:0
  144. Here you can specify additional parameters passed to every ./configure
  145. script.
  146. Use "--with-option" to enable a feature
  147. Use "--without-option" to disable a feature
  148. Use "--option[=value]" to specify a custom option
  149. The Build-System will always check whether the configure script supports
  150. the options before the options is really passed as argument.
  151. COMMENT_FLIST
  152. Please see the help for the choice menu.
  153. ROCKCFG_FLIST
  154. This help is taken from Rolling ROCK Issue #2 2003
  155. The ROCK Linux build scripts auto-detect which files are created
  156. by a package build and use this information to create the package
  157. file list. There are three techniques which can be used to auto-detect
  158. this file list
  159. * flist-wrapper
  160. The flist-wrapper is the recommended way of doing it. It's an "elf
  161. preload library". This is a library which is loaded _before_ the
  162. c-library and so can overwrite functions of the c library. The
  163. flist-wrapper lib is overwriting all functions which can be used
  164. to create files and is writing the filenames to a log file before
  165. running the original c library function.
  166. This log file is used to create the package file list after the
  167. build has been completed. The problem with the flist-wrapper lib is
  168. that it doesn't work with statically built binaries or with non
  169. glibc c libraries. In such environments (e.g. when building a
  170. dietlibc based system), other techniques - such as those described
  171. below - must be used for creating the file list.
  172. * strace
  173. This one is rather easy: The whole build is running in a process-
  174. tree which is monitored by strace. The log file created by strace is
  175. later used to create the package file list. However: this does only
  176. work on architectures which do have an strace command - which is not
  177. the case for all architectures the Linux kernel and glibc have been
  178. ported to.
  179. * find
  180. This one is rather ugly (but sometimes the only alternative): When
  181. the build is started, a 'timestamp-file' is created. After the build
  182. has been completed, the find program is used to find all files which
  183. are newer than the 'timestamp-file'. This is really slow now and has
  184. the disadvantage that nothing else than the build process may create
  185. or modify files while the build is running. This should only be used
  186. if no other system for creating the file list can be used.
  187. ROCKCFG_USE_CROSSCC
  188. This option controls whether to use a pseudo-cross compiler even
  189. for native (non-cross) builds. This is needed when the host and
  190. target gcc or glibc differ in the ABI.
  191. THIS IS STRONGLY RECOMMENDED!
  192. ROCKCFG_DO_REBUILD_STAGE
  193. This options controls whether to rebuild all packages in the final
  194. rebuild stage.
  195. Each and every package is rebuilt in stage 9 once more and only then
  196. are the binary packages created. This has the advantage that
  197. circular dependencies are resolved, but it also almost doubles the
  198. build time.
  199. In former times this was recommended - but nowadays this is only a
  200. paranoia thing.
  201. ROCKCFG_DO_CHECK
  202. This options enables to run a make check / test target for packages
  203. with support for this. This can be used as extended quality assurance
  204. to make sure the resulting binaries work correct.
  205. ROCKCFG_OPT
  206. With this option, the type of optimisation can be selected.
  207. ROCKCFG_DEBUG
  208. Enable this option if you want to have debug symbols in your binaries.
  209. ROCKCFG_LIMITCXX
  210. Check here if you want to disable the C++ exceptions run-time type
  211. identification. This can make the C++ binaries about 25% smaller,
  212. but any C++ sources using exceptions or rtti, for example QT/KDE,
  213. will fail to compile. If you don't know, don't touch.
  214. ROCKCFG_MULTILIB
  215. Enable installing several versions of the same library.
  216. ROCKCFG_DISABLE_NLS
  217. Please check here if you do not want to use Native Language Support.
  218. ROCKCFG_CREATE_CACHE
  219. Please check here if you want to create *.cache files after a build
  220. has completed. This is the same as a reference build.
  221. ROCKCFG_PARANOIA_CHECK
  222. Please check here if you want to run sanity checks before building.
  223. THIS IS STRONGLY RECOMMENDED!
  224. ROCKCFG_IDCKSUM
  225. Please check here if you want to use a checksum instead of the long
  226. explanatory ROCKCFG-ID.