| 1 |
This directory contains sample files that should be in pretty much every |
| 2 |
MATE application. |
| 3 |
|
| 4 |
----------------------------------------------------------------------------- |
| 5 |
|
| 6 |
To make this work both for MATE Applications inside and outside the |
| 7 |
MATE repository tree I did the following: |
| 8 |
|
| 9 |
* There is an `INSIDE_MATE_COMMON' automake conditional which is defined |
| 10 |
in two places: |
| 11 |
|
| 12 |
- macros/aclocal-includes.m4 defines this to always be false. |
| 13 |
|
| 14 |
- mate-common/configure.in does not include anything from macros and |
| 15 |
defines this to be true. |
| 16 |
|
| 17 |
* We use this automake conditional in the macros/Makefile.am to install |
| 18 |
$(MACROS), autogen.sh, mate-common.m4 and a newly created mate-macros.dep |
| 19 |
in `$(datadir)/aclocal/mate'. |
| 20 |
|
| 21 |
Since aclocal doesn't look in subdirectories we can safely install them |
| 22 |
there even when compiling from the repository. |
| 23 |
|
| 24 |
Also, there is no need to make any change to any existing application |
| 25 |
in the MATE repository tree - really fine... |
| 26 |
|
| 27 |
* When we're outside the MATE repository tree, we simply need to tell aclocal |
| 28 |
that it should also look in `$(datadir)/aclocal/mate' and it will find all |
| 29 |
the macros. |
| 30 |
|
| 31 |
There is a `mate-skel' module in the repository that can be used as a |
| 32 |
starting point when writing a new MATE application that should be used |
| 33 |
outside the repository. |
| 34 |
|
| 35 |
February 4, 1999, |
| 36 |
Martin Baulig <[email protected]> |