Difference between revisions of "lazbuild"

From Lazarus wiki
Jump to navigationJump to search
m (→‎USAGE: formatting)
Line 7: Line 7:
 
lazbuild  builds  a  Lazarus project or package. It compiles projects (.lpi) and packages (.lpk). It checks and automatically compiles required packages.
 
lazbuild  builds  a  Lazarus project or package. It compiles projects (.lpi) and packages (.lpk). It checks and automatically compiles required packages.
  
=USAGE=
+
==Usage==
      lazbuild is a command-line tool that builds Lazarus projects and packages. It checks recursively all  dependencies and
+
lazbuild is a command-line tool that builds Lazarus projects and packages. It checks recursively all  dependencies and compiles needed packages first. It uses the Free Pascal compiler (fpc) to compile.
      compiles needed packages first. It uses the Free Pascal compiler (fpc) to compile.
 
  
==OPTIONS==
+
==Options==
 
;-h or --help: write the list of options.
 
;-h or --help: write the list of options.
  
 
;-B or --build-all: build  all  files  of  project/package. Normally the compiler only compiles the main source and all sources with a newer date.
 
;-B or --build-all: build  all  files  of  project/package. Normally the compiler only compiles the main source and all sources with a newer date.
  
      -r or --recursive
+
;-r or --recursive: apply build flags (-B) to dependencies too.
              apply build flags (-B) to dependencies too.
 
  
      -d or --skip-dependencies
+
;-d or --skip-dependencies: do not compile dependencies
              do not compile dependencies
 
  
      -v or --version
+
;-v or --version: show version and exit
              show version and exit
 
  
      --primary-config-path=<path> or --pcp=<path>
+
;--primary-config-path=<path> or --pcp=<path>: primary config directory, where Lazarus stores its config files. Default is $HOME/.lazarus
              primary config directory, where Lazarus stores its config files. Default is $HOME/.lazarus
 
  
      --secondary-config-path=<path> or --scp=<path>
+
;--secondary-config-path=<path> or --scp=<path>: secondary config directory, where Lazarus searches for config template files. Default is /etc/lazarus
              secondary config directory, where Lazarus searches for config template files. Default is /etc/lazarus
 
  
      --operating-system=<operating-system> or --os=<operating-system>
+
;--operating-system=<operating-system> or --os=<operating-system>: override the project operating system. e.g. win32 or linux.
              override the project operating system. e.g. win32 or linux.
 
  
      --widgetset=<widgetset> or --ws=<widgetset>
+
;--widgetset=<widgetset> or --ws=<widgetset>: override the project widgetset. e.g. gtk, gtk2, qt, win32, or carbon.
              override the project widgetset. e.g. gtk, gtk2, qt, win32, or carbon.
 
  
      --cpu=<cpu>
+
;--cpu=<cpu>: override the project cpu. e.g. i386, x86_64, powerpc, powerpc_64 etc.
              override the project cpu. e.g. i386, x86_64, powerpc, powerpc_64 etc.
 
  
      --compiler=<ppcXXX>
+
;--compiler=<ppcXXX>: override the default compiler. e.g. ppc386, ppcx64, ppcppc etc.
              override the default compiler. e.g. ppc386, ppcx64, ppcppc etc.
 
  
      --language=
+
;--language=<language>: override language. For example --language=de. For possible values see files in the lazarus/languages directory.
              Override language. For example --language=de. For possible values see files in the lazarus/languages directory.
 
  
 
=.lpi and .lpk files=
 
=.lpi and .lpk files=
 
       The .lpi and .lpk files are best created and edited with the Lazarus IDE.  The files are in xml. There is  no  reason  to
 
       The .lpi and .lpk files are best created and edited with the Lazarus IDE.  The files are in xml. There is  no  reason  to
 
       edit them manually, except for very rare cases like renaming hundreds of files.
 
       edit them manually, except for very rare cases like renaming hundreds of files.

Revision as of 17:37, 17 September 2006

lazbuild is a command line utility to compile Lazarus projects and packages.

SYNOPSIS

lazbuild [options] filename...

DESCRIPTION

lazbuild builds a Lazarus project or package. It compiles projects (.lpi) and packages (.lpk). It checks and automatically compiles required packages.

Usage

lazbuild is a command-line tool that builds Lazarus projects and packages. It checks recursively all dependencies and compiles needed packages first. It uses the Free Pascal compiler (fpc) to compile.

Options

-h or --help
write the list of options.
-B or --build-all
build all files of project/package. Normally the compiler only compiles the main source and all sources with a newer date.
-r or --recursive
apply build flags (-B) to dependencies too.
-d or --skip-dependencies
do not compile dependencies
-v or --version
show version and exit
--primary-config-path=<path> or --pcp=<path>
primary config directory, where Lazarus stores its config files. Default is $HOME/.lazarus
--secondary-config-path=<path> or --scp=<path>
secondary config directory, where Lazarus searches for config template files. Default is /etc/lazarus
--operating-system=<operating-system> or --os=<operating-system>
override the project operating system. e.g. win32 or linux.
--widgetset=<widgetset> or --ws=<widgetset>
override the project widgetset. e.g. gtk, gtk2, qt, win32, or carbon.
--cpu=<cpu>
override the project cpu. e.g. i386, x86_64, powerpc, powerpc_64 etc.
--compiler=<ppcXXX>
override the default compiler. e.g. ppc386, ppcx64, ppcppc etc.
--language=<language>
override language. For example --language=de. For possible values see files in the lazarus/languages directory.

.lpi and .lpk files

      The .lpi and .lpk files are best created and edited with the Lazarus IDE.  The files are in xml. There is  no  reason  to
      edit them manually, except for very rare cases like renaming hundreds of files.