|
1 | | -PocketSphinx 5.1.0rc1 |
| 1 | +PocketSphinx 5.1.0rc2 |
2 | 2 | ===================== |
3 | 3 |
|
4 | 4 | This is PocketSphinx, one of Carnegie Mellon University's open source large |
@@ -172,7 +172,56 @@ also read the [documentation for the Python |
172 | 172 | API](https://pocketsphinx.readthedocs.io) or [the C |
173 | 173 | API](https://cmusphinx.github.io/doc/pocketsphinx/) |
174 | 174 |
|
175 | | -Authors |
| 175 | +Development |
| 176 | +----------- |
| 177 | + |
| 178 | +There isn't quite enough information here for potential developers, |
| 179 | +but here's a start. The C API documentation is built with Doxygen, |
| 180 | +which will be auto-detected when running CMake. If you have it |
| 181 | +installed, you can build the docs with: |
| 182 | + |
| 183 | + cmake --build build --target docs |
| 184 | + |
| 185 | +There is a suite of regression and unit tests, run with: |
| 186 | + |
| 187 | + cmake --build build --target check |
| 188 | + |
| 189 | +You can run it somewhat faster with: |
| 190 | + |
| 191 | + cd build && ctest -j4 # or however many CPUs you want to use |
| 192 | + |
| 193 | +Somewhat confusingly (because readthedocs needs it, I think?), the |
| 194 | +Python API documentation is in the `docs` directory which has nothing |
| 195 | +to do with the abovementioned CMake target. These use some extra |
| 196 | +dependencies named in `docs/requirements.txt`. To build the |
| 197 | +documentation first set up a virtual environment, then run `make` in |
| 198 | +the `docs` directory, with one of its many targets (`html` here will |
| 199 | +make multi-page HTML documentation): |
| 200 | + |
| 201 | + python3 -m venv ~/ve_pocketsphinx |
| 202 | + . ~/ve_pocketsphinx/bin/activate |
| 203 | + pip install -r docs/requirements.txt |
| 204 | + make -C docs html |
| 205 | + |
| 206 | +There are also Python regression tests, of course, which for some |
| 207 | +reason require `memory_profiler`: |
| 208 | + |
| 209 | + python3 -m venv ~/ve_pocketsphinx |
| 210 | + . ~/ve_pocketsphinx/bin/activate |
| 211 | + pip install -e . |
| 212 | + pip install memory_profiler |
| 213 | + pytest |
| 214 | + |
| 215 | +Most, but not all of the release process is managed with GitHub |
| 216 | +Actions, namely the "Release" and "Update API Documentation" |
| 217 | +workflows. The notable exception here is updating the version, which |
| 218 | +is done with [Bump My |
| 219 | +Version](https://github.com/callowayproject/bump-my-version). |
| 220 | + |
| 221 | +Also, the [Read The Docs](https://pocketsphinx.readthedocs.io) pages |
| 222 | +must be updated manually, it seems (maybe this will be fixed soon). |
| 223 | + |
| 224 | +AUTHORS |
176 | 225 | ------- |
177 | 226 |
|
178 | 227 | PocketSphinx is ultimately based on `Sphinx-II` which in turn was |
|
0 commit comments