Build System Analysis:build.pl versus makefile

From Apache OpenOffice Wiki
Revision as of 09:17, 18 October 2013 by JanIversen (Talk | contribs)

Jump to: navigation, search

Edit.png

Build Environment Effort

Quick Navigation

About this template


build.pl versus central makefile

In order to refactor our build system, the functionality of build.pl and how it can be translated into a central makefile have been analyzed.

The following table contains all build.pl options, with description (build --help), and the make (in main) equivalent

Option Description Makefile
--all build all projects from very beginning till current one "make" builds all modules

"make <module>" builds to and with <module>

--from build all projects dependent from the specified (including it) till current one not suported
--genPO extract en-US PO file(s), no build/deliver (usable for '-all' and '-from' keys) "make genPO" to extract from all modules

"<module>/make genPO" to extract from a single module

--exclude_branch_from exclude module(s) and its branch from the build not suported
--mode OOo build only projects needed for OpenOffice.org not suported
--prepare clear all projects for incompatible build from prj_name till current one [for platform] (cws version) "make clear" to clear all modules

"<module>/make clear" to clear a single module

--with_branches- the same as "--from" but with build all projects in neighbour branches not suported
--skip do not build certain module(s) not suported
--since build all projects beginning from the specified till current one (the same as "--all:prj_name", but skipping prj_name) "make <module>"
--checkmodules check if all required parent projects are availlable "make -q" dry-run for dependencies all modules

"make <module> -q" dry-run for dependencies of <module>

--show show what is going to be built "make -q" dry-run for dependencies all modules

"make <module> -q" dry-run for dependencies of <module> "<module>/make -q" dry-run for all files in <module>

--file generate command file file_name not suported
--deliver only deliver, no build (usable for '-all' and '-from' keys) "make deliver" delivers all modules

"<module>/make deliver" delivers a single module

-P start multiprocessing build, with number of processes passed "make -j<x>" where <x> is number of parallel processes
--server start build in server mode (clients required) not suported
--setenvstring (--server) string for configuration of the client environment not suported
--port (--server) set server port, default is 7890. You may pass several ports, the server will be started on the first available

otherwise the server will be started on first available port from the default range 7890-7894

not suported
--client_timeout (--server) time frame after which the client/job is considered to be lost. Default is 120 min not suported
--dlv_switch use deliver with the switch specified not suported
row 2, cell 1 row 2, cell 2 not suported
row 2, cell 1 row 2, cell 2 not suported


    - 
- 

--help - print help info

--ignore - force tool to ignore errors

--html - generate html page with build status

                      file named unxlngx6.pro.build.html will be generated in /share/opensource/aoo/branches/l10n40/main

--html_path - set html page path

--dontgraboutput - do not grab console output when generating html page

--genconf - generate/modify workspace configuration file

--add - add active module(s) to configuration file

--remove - removeactive modules(s) from configuration file

--removeall|--clear - remove all active modules(s) from configuration file

--stoponerror - stop build when error occurs (for mp builds)

--interactive - start interactive build process (process can be managed via html page)

  Custom jobs:

--job=job_string - execute custom job in (each) module. job_string is a shell script/command to be executed instead of regular dmake jobs

--pre_job=pre_job_string - execute preliminary job in (each) module. pre_job_string is a shell script/command to be executed before regular job in the module

--post_job=job_string - execute a postprocess job in (each) module. post_job_string is a shell script/command to be executed after regular job in the module

default: build current project

Personal tools