From e967e50805e50decd809236da314127cd425ef0b Mon Sep 17 00:00:00 2001 From: Mitch Curtis Date: Tue, 31 Jan 2017 10:52:34 +0100 Subject: Doc: provide an example of how 3rdparty/hunspell should look MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It can be difficult to get the directory structure right, so having this example will make it easy for the user to check if they’ve copied in the Hunspell sources correctly. Change-Id: I15dbafff37f44c2ea24d24077d8387898dd49ca3 Reviewed-by: Jarkko Koivikko Reviewed-by: Mitch Curtis --- src/virtualkeyboard/doc/src/build.qdoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/src/virtualkeyboard/doc/src/build.qdoc b/src/virtualkeyboard/doc/src/build.qdoc index add2738b..3d9d9eac 100644 --- a/src/virtualkeyboard/doc/src/build.qdoc +++ b/src/virtualkeyboard/doc/src/build.qdoc @@ -264,6 +264,23 @@ then the dictionary files must also be copied into the \e src/virtualkeyboard/3rdparty/hunspell/data directory. Furthermore, if Hunspell sources are used, \e hunspell.pro will be used for all targets. +An example of how the directory structure should look after copying in the +Hunspell sources and dictionary files is listed below: + +\badcode +3rdparty +└── hunspell + ├── data + │ ├── en_GB.aff + │ └── en_GB.dic + ├── hunspell.pro + └── src + └── hunspell + ├── affentry.cxx + ├── affentry.hxx + (etc.) +\endcode + \section2 Static builds The virtual keyboard can be built and linked statically against the application. -- cgit v1.2.3