• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category User Interface → Simulator
  • 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
Attached to Project: Rockbox
Opened by linusnielsen - 2007-08-07
Last edited by rasher - 2007-08-08

FS#7553 - No voice file configuration for simulator

It is currently not possible to build a correct voice file for the simulator, since tools/configure only lets us select either (S)imulator och (V)oice, but not both.

Closed by  rasher
2007-08-08 22:17
Reason for closing:  Fixed
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

It's now possible to select both voice and simulator build by going into the "advanced" configuration. Whether the voicefile is correctly adjusted to the sim, I'm not sure. Please open a new bugreport if not.

The solution to this is probably to move voice building under the “Advanced” part of configure. This should have a number of other benefits as well to make building more sensible.

Call me stupid (everyone else does) but what’s the difference between a voice file for the sim and it’s oorresponding device. e.g. An H300 voice file is an H300 voice file, whether sim or device, right?

Project Manager

The difference is that some strings are not present in the sim, for example LANG_REDUCE_TICKING, and there is at least one string that is only present in the simulator, LANG_USB.

For the low number of differences, is it worth differentiating? I’d rather see the sim get closer to the target.

Project Manager

It is worth differentiating as long as the lng files for the target and the sim are different. Otherwise the voice will not work.

The lng files will be different, since some features simply do not work in the simulator.

Regardless, voice file building should not be a main build option. If put into the “advanced” part of configure, you’d be able to do ../tools/configure && make && make voice && make manual && make zip (perhaps buildzip could be expanded to include the manual and voice file if present?)


Available keyboard shortcuts


Task Details

Task Editing