Bug 2656 - Don't compile an fst that is not needed
Summary: Don't compile an fst that is not needed
Status: NEW
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: newinfra (show other bugs)
Version: unspecified
Hardware: All All
: P4 - Within a month normal
Assignee: Sjur Nørstebø Moshagen
Depends on:
Blocks: 2655
  Show dependency treegraph
Reported: 2020-03-31 07:41 CEST by Sjur Nørstebø Moshagen
Modified: 2020-03-31 07:41 CEST (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Sjur Nørstebø Moshagen 2020-03-31 07:41:30 CEST
Example: there's no point in compiling both -desc and -norm if there are no +Err/* tags in the fst. This can be checked for during configure time, and thus easily be made to skip.

In the case of -desc vs -norm, there are four options at least:

- build only -desc
- build only -norm
- build one, and symlink the other to the first
- build a new one, e.g. analyser-gt-all.?fst

The symlink alternative is probably the best one, as all other operations can assume fixed filenames.

Other candidates:
- disamb (if no semantic tags)
- oahpa (if no dialects?)

There might be more, but most other fst's are built conditionally in any case, requiring explicit enabling at configure time.

Another thing is to look at the defaults: e.g. do we always need the area variants (when those are declared), or should the default be to not build them, requiring enabling at config time instead? The same goes for orthographical and writing system variants.