Difference between revisions of "Writing Makefiles"
(→Modes) |
(→Modes) |
||
| Line 4: | Line 4: | ||
If you have <code>apertium</code> revision 51184 or higher, you can do this to simplify dealing with [[Modes]] files / modes.xml: |
If you have <code>apertium</code> revision 51184 or higher, you can do this to simplify dealing with [[Modes]] files / modes.xml: |
||
In <code>configure.ac</code>, add this: |
|||
<pre>AP_MKINCLUDE</pre> |
|||
In <code>Makefile.am</code>, add this: |
|||
<pre> |
<pre> |
||
# Only include one mode file here, the rest will be built along with it (listing several leads to problems with parallell make): |
# Only include one mode file here, the rest will be built along with it (listing several leads to problems with parallell make): |
||
| Line 13: | Line 14: | ||
@ap_include@ |
@ap_include@ |
||
# Most language pairs don't need to specify anything else for install-data-local: |
|||
install-data-local: install-modes |
install-data-local: install-modes |
||
EXTRA_DIST: |
EXTRA_DIST: |
||
modes.xml \ |
modes.xml \ |
||
# other |
# here you'll typically also have other things, like .dix and .t1x |
||
# files that are to be included when you make a release |
|||
</pre> |
</pre> |
||
''Nowhere else should modes be mentioned in the <code>Makefile.am</code>.'' |
''Nowhere else should modes be mentioned in the <code>Makefile.am</code>.'' |
||
If you follow this system, the modes with install="yes" in modes.xml will be installed, and you won't end up with root-owned modes files, and make -j4 will work fine. |
|||
==Use .deps/.d to say that the .deps directory must be created== |
==Use .deps/.d to say that the .deps directory must be created== |
||
Revision as of 18:28, 24 March 2014
Some tips for writing clean Makefile.am's in Apertium:
Modes
If you have apertium revision 51184 or higher, you can do this to simplify dealing with Modes files / modes.xml:
In configure.ac, add this:
AP_MKINCLUDE
In Makefile.am, add this:
# Only include one mode file here, the rest will be built along with it (listing several leads to problems with parallell make):
noinst_DATA=modes/$(PREFIX1).mode
@ap_include@
# Most language pairs don't need to specify anything else for install-data-local:
install-data-local: install-modes
EXTRA_DIST:
modes.xml \
# here you'll typically also have other things, like .dix and .t1x
# files that are to be included when you make a release
Nowhere else should modes be mentioned in the Makefile.am.
If you follow this system, the modes with install="yes" in modes.xml will be installed, and you won't end up with root-owned modes files, and make -j4 will work fine.
Use .deps/.d to say that the .deps directory must be created
Say you have several goals that put temporary files in .deps/, e.g.
.deps/apertium-wat-lol.lol.dix: apertium-wat-lol.lol.dix test -d .deps || mkdir .deps xsltproc lexchoicebil.xsl $< >$@
and so on. The .deps directory has to be created for the file in .deps to be created. If you put mkdir .deps in each such goal, you can get a race condition where two goals try to make .deps at the same time.
The solution is this: if a goal needs the .deps directory to be created, let it depend on the file .deps/.d. First put this in Makefile.am:
.deps/.d: test -d .deps || mkdir .deps touch $@ .PRECIOUS: .deps/.d
And then, instead of creating the dir in each goal, just depend on .deps/.d for those goals:
.deps/apertium-wat-lol.lol.dix: apertium-wat-lol.lol.dix .deps/.d xsltproc lexchoicebil.xsl $< >$@
(The PRECIOUS line prevents the .d file from being cleaned up and removed automatically.)
Removing directories on make clean
Say you want to remove .deps and modes on "make clean". Don't do CLEANFILES=-rf .deps modes file1 file2 …, it doesn't work everywhere.
A more portable solution is this:
CLEANFILES = $(TARGETS_COMMON) clean-local: -rm -rf .deps modes
