diff options
| author | Gergely Risko <gergely+context@risko.hu> | 2009-06-23 18:01:26 +0300 |
|---|---|---|
| committer | Gergely Risko <gergely+context@risko.hu> | 2009-06-23 18:01:26 +0300 |
| commit | 0d4919ec4de8dcc30135867828a202593883c161 (patch) | |
| tree | b4b57068c571db2c65b191eecb0da0a58e347c97 /HACKING | |
| parent | 51bce7d9de06d9daec5249f630ea095e398fb7af (diff) | |
Build cleanup continued.
The configure.ac is only about checking the configuration (build environment) now, not setting things up.
Every build setting is stored in Makefile.ams.
No coverage yet, but make check is supported.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 28 |
1 files changed, 24 insertions, 4 deletions
@@ -9,10 +9,8 @@ Build system ------------ We use the autotools in their 'foreign' strictness plus pkg-config. -We don't use qmake, even for Qt programs or libraries. Use pkg-config -when you use Qt libraries and write explicit rules for invocations of -tools like moc. See the ContextCommander for an elaborate example. -[Soon] +We don't use qmake, even for Qt programs or libraries. We have our +own solution for handling Qt things, documented in am/qt.am. Upstream and Packaging ---------------------- @@ -45,6 +43,17 @@ It's not yet totally clear how to cope with that: one approach is to have something like autotool's "missing", another might be to touch all 'interesting' files just before building. Let's see. +Anyway, you can disable generating of documentation by passing +--disable-doc to configure. + +Vala +---- + +Finding a good vala compiler is hard too, sometimes harder than +finding the documentation tools. So we distribute or vala generated C +sources too, the same timestamp issues applies, you can disable +compilation of .vala files with --disable-vala. + Environments ------------ @@ -200,6 +209,17 @@ Here is the general procedure: The "git-make-dist" script runs "make distdir" and creates a tag with the contents of the created directory. +Building a debian package +------------------------- + +After a git clone, you first have to build vala C sources and +documentation. If you have extracted a distribution tarball, then you +already have these files. Otherwise just do a ./configure, let's +double check that all of the documentation tools and the vala compiler +is found and make. After that you are ready to run +'dpkg-buildpackage -us -uc -rfakeroot -b' to get your shiny new debian +packages. + Making releases --------------- |