aboutsummaryrefslogtreecommitdiff
path: root/doc/packaging.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2024-04-16 16:35:30 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2024-04-16 16:35:30 +0200
commit8325af5e86091acb036077e1873daf9e9e862348 (patch)
tree3095e2df4fa77305d54b1553df18bf4f60efc5fd /doc/packaging.cli
parentf20e95cb70b0a421691c50a6d7efe3e04a38f66e (diff)
Fix typo in packaging guide
Diffstat (limited to 'doc/packaging.cli')
-rw-r--r--doc/packaging.cli2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/packaging.cli b/doc/packaging.cli
index 3fbfe40..d861457 100644
--- a/doc/packaging.cli
+++ b/doc/packaging.cli
@@ -1110,7 +1110,7 @@ libfoo/
Once the overall layout looks right, the next step is to take a closer look at
the generated \c{buildfiles} to make sure that overall they match the upstream
build. Of particular interest are the header and source directory
-\c{buildfiles} (\c{libfoo/include/foo/buildifle} and \c{libfoo/src/buildifle}
+\c{buildfiles} (\c{libfoo/include/foo/buildfile} and \c{libfoo/src/buildfile}
in the above listing) which define how the library is built and installed.
Here we are focusing on the macro-level differences that are easier to change