Command Line Options and Environment Variables
Prev
Next

Chapter 5. Command Line Options and Environment Variables

This script does not use environment variables. If you need to set environment variables for the build or install process, please see the set-env option.

The script accepts the following command-line options:

--async

Enables the asynchronous mode to update and build at the same time. This is the default, this option only needs specified if you have disabled it in the configuration.

--help

Only display simple help on this script.

--version

Display the program version.

--author

Display contact information for the author.

--color

Enable colorful output.

--nice=value

Sets the niceness value to value for the duration of this run. value should be between 0 and 20.

--no-async

Disables the asynchronous mode of updating. Instead the update will be performed in its entirety before the build starts. This option will slow down the overall process, but if you encounter IPC errors while running Kdesvn-build try using this option, and submitting a bug report.

--no-color

Disable colorful output.

--pretend (or -p)

Do not actually do anything, but act like you did.

--quiet (or -q)

Do not be as noisy with the output. With this switch only the basics are output.

--really-quiet

Only output warnings and errors.

--verbose

Be very descriptive about what is going on, and what Kdesvn-build is doing.

--svn-only

Only perform the source update.

--build-only

Only perform the build process.

--ignore-modules

Do not include the modules passed on the rest of the command line in the update/build process.

--no-svn

Skip contacting the Subversion server.

--no-build

Skip the build process.

--no-install

Do not automatically install packages after they are built.

--debug

Enables debug mode for the script. Currently this means that all output will be dumped to the standard output in addition to being logged in the log directory like normal. Also, many functions are much more verbose about what they are doing in debugging mode.

--no-rebuild-on-fail

Do not try to rebuild modules that have failed building from scratch. Kdesvn-build will never try to do this to a module that already was tried to be built from scratch.

--refresh-build

Recreate the build system and make from scratch.

--reconfigure

Run the configure script again without cleaning the build directory.

--recreate-configure

Run make -f Makefile.cvs again to create the configure script, and continue building as normal. This option implies --reconfigure.

--resume-from

This option is used to resume the build starting from the given module, which should be the next option on the command line. This option implies --no-svn. You should not specify other module names on the command line.

--rc-file

which interprets the next command line parameter as the file to read the configuration options from. The default value for this parameter is ~/.kdesvn-buildrc.

--run

This option interprets the next item on the command line as a program to run, and Kdesvn-build will then finish reading the configuration file, update the environment as normal, and then execute the given program.

This will not work to start a shell with the Kdesvn-build environment in most cases however, since interactive shells typically reset at least part of the environment variables (such as PATH and KDEDIRS) in the startup sequence.

--prefix=</path/to/kde>

This allows you to change the directory that KDE will be installed to from the command line. This option implies --reconfigure.

--build-system-only

Stop after running make -f Makefile.cvs. The configure script will still need to be run, which Kdesvn-build will do next time. This lets you prepare all the configure scripts at once so you can view the ./configure --help for each module, and edit your configure-flags accordingly.

--install

If this is the only command-line option, it tries to install all of the modules contained in successfully-built, except for qt-copy, which does not need installation. If command-line options are specified after --install, they are all assumed to be modules to install.

--<option-name>=

You can use this option to override an option in your configuration file for every module. For instance, to override the log-dir option, you would do: --log-dir=/path/to/dir.

--<module-name>,<option-name>=

You can use this option to override an option in your configuration file for a specific module. For instance, to override the use-unsermake option for kdemultimedia, you would do: --kdemultimedia,use-unsermake=false.

Any other command-line options are assumed to be modules to update and build. Please, do not mix building with installing.

Prev
Next
Contents


Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team