source: branches/kmk/README.DEV @ 295

Last change on this file since 295 was 295, checked in by dmik, 12 years ago

branches/kmk: Started moving the build system to kmk setup and made freetype2 and fontconfig built by it.

File size: 1.9 KB
Line 
1This file contains instructions on building Lucide.
2
3
4
5REQUIREMENTS
6
7In order to build Lucide, you will need the following tools:
8
9  - kBuild version 0.1.5 (r2206) or later. Get it with the following command:
10
11      svn co http://svn.netlabs.org/repos/kbuild/trunk/kBuild
12
13  - GCC compiler version 3.3.5 or 4.4.2 for OS/2 and the patched OpenWatcom
14    linker. The GCC compiler must be set up to use the OpenWatcom linker for
15    linking.
16
17    If you do not have a working GCC environment with the above requirements, it
18    is recommended to download a ready-to-use GCC 4.2.2 distribution from here:
19
20      ftp://ftp.netlabs.org/pub/qt4/gcc-4_4_2-complete-20091205.zip
21
22    Follow the installation instructions contained in the README file inside
23    this ZIP archive to set up the GCC environment.
24
25
26
27SETTING UP THE ENVIRONMENT
28
29Copy "LocalEnv.cmd.tpl" to "LocalEnv.cmd" and adjust the copy to match your
30environment. Each option in "LocalEnv.cmd.tpl" has a comment describing what it
31does.
32
33You may also want to adjust the configuration of the Lucide build according to
34your needs. To do so, copy "LocalConfig.kmk.tpl" to "LocalConfig.kmk" and adjust
35the copy to match your requirements. Each option in "LocalConfig.kmk.tpl" has a
36comment descriping what it does.
37
38Now, start "env.cmd" to setup the environment and type "kmk" in the root
39directory of the Lucide source tree to start kBuild and build the release
40version of Lucide and all plugins.
41
42If you are a developer, you may prefer to use the "pe.cmd" script instead of
43starting "env.cmd" in each new shell. This script will allow you to run "kmk"
44in the correct environment from any directory inside the Lucide source tree by
45simply typing "pe kmk" in that directory. This is especially handy if you use
46e.g. File Commander as your development IDE. The "pe.cmd" script is may be
47obtained at:
48
49  ftp://ftp.netlabs.org/pub/qt4/tools/pe10.zip
50
Note: See TracBrowser for help on using the repository browser.