- Status Closed
- Percent Complete
- Task Type Patches
- Category Infrastructure → Build environment
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#8567 - Generate list of features to enable in manuals from features.txt
This patch parses the features.txt file to create a list of features to enable in the manuals similar to the features list used by genlang.
This eases the maintenance cost of keeping all manuals up to date with the latest code changes.
To actually use this, a bit of search&replace is needed in the manual since these new option commands are not named the same as the ones in the current platform file.
One possible problem that I would like input on is that now a “make manual” is needed to actually build a manual, just “make” will make a regular build (just like you have to use “make voice” to build a voicefile) I don’t know if this is a problem for anybody?
The reason for this change is that correct include paths are needed now to find all header files.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Remove debug echo
I don't think it would be an issue to require "make manual" to be run explicitly – IMO we could drop the configuration target "manual" completely and use the standard build configuration instead. The only drawback I see is that building the manual now requires gcc to be present. OTOH at least I wouldn't mind that dependency.