| 26 | | </para> |
|---|
| | 26 | </para> |
|---|
| | 27 | <refsect2> |
|---|
| | 28 | <title>Building with waf</title> |
|---|
| | 29 | <para> |
|---|
| | 30 | GtkImageView can also be built using the build tool <ulink src |
|---|
| | 31 | = "http://code.google.com/p/waf/">waf</ulink>. The waf binary |
|---|
| | 32 | is distributed with GtkImageView, so the only prerequisite to |
|---|
| | 33 | using it is that <ulink src = |
|---|
| | 34 | "http://www.python.org/">Python</ulink> 2.4 or later is |
|---|
| | 35 | installed. Waf is the offically preferred way to build |
|---|
| | 36 | GtkImageView with, so please try it out. Autotools still works |
|---|
| | 37 | ofcourse. |
|---|
| | 38 | </para> |
|---|
| | 39 | <para> |
|---|
| | 40 | These commands builds and installs GtkImageView with waf: |
|---|
| | 41 | <literallayout> |
|---|
| | 42 | <userinput>$ ./waf configure # Add --enable-gtk-doc to build the documentation</userinput> |
|---|
| | 43 | <userinput>$ ./waf build</userinput> |
|---|
| | 44 | <userinput>$ ./waf install</userinput> |
|---|
| | 45 | </literallayout> |
|---|
| | 46 | The test programs and demos are built by specifying specific |
|---|
| | 47 | build targets to <command>waf build</command>: |
|---|
| | 48 | <literallayout> |
|---|
| | 49 | <userinput>$ ./waf build demos # Builds demos</userinput> |
|---|
| | 50 | <userinput>$ ./waf build tests # Builds tests</userinput> |
|---|
| | 51 | </literallayout> |
|---|
| | 52 | All the binaries are, by default, placed in |
|---|
| | 53 | the <filename>build/default/tests</filename>. |
|---|
| | 54 | </para> |
|---|
| | 55 | </refsect2> |
|---|
