• 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
Attached to Project: Rockbox
Opened by asettico - 2008-09-14
Last edited by kugel. - 2009-08-09

FS#9400 - tools/configure more improvements

This patch extends the improvements supplied by #8842 to all the values read from stdin.
The command line options added are:


ATYPE can be a string containing one or more letters, as showed in advanced build menu.

Closed by  kugel.
2009-08-09 19:03
Reason for closing:  Accepted
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

Committed in r22228. Thanks a lot!

Sync’d against today’s daily build (r20089).

Would it be possible to remove –atype, and fuse it with –type? You can’t have both at the same time, so –type could be replaced if “a” is given or something.

I’ sync-ed it with current build to fix some line number offsets and fuzz factor. I just have to upload the new file.
I can think to reorganize the added arguments. I’m not sure, but maybe I added the option atype since due to an overload between normal and advanced options, so it’s possible to use the same letters as indicated by the output in the intercative execution. But I need to check them.
Stay tuned! :-)

I’m thinking if –type starts with “a” then it can’t be a normal build anymore, so overloading sounds possible to me.

Here it is the updated patch, sync’d against build r21259.
It supports following command line arguments (some of them belong to  FS#8842 ):

  1. -target=TARGET
  2. -ram=RAM
  3. -type=TYPE
  4. -language=LANG
  5. -tts=ENGINE
  6. -voice=VOICE
  7. -ttsopts=OPTS
  8. -encopts=OPTS
  9. -rbdir=DIR
  10. -ccache
  11. -no-ccache
  12. -help

Now –type accepts a string to select multiple options.
So, if I want to build voice, I will do:

  ../tools/configure --type=av ...

For the bootloader, I will do:

  ../tools/configure --type=b ...

For the backlight option (when allowed), I will do:

  ../tools/configure --type=ab ...

(According with my naming rule for the patch files, last number before the extension indicates the value to be used in patch -p. HTH)

Great, gonna check this out

Sync’ed against current build (r21388).

Seems to work well! I’m all for committing (I think I’ll do it soonish).

Alright, I have had a look.

Nothing against the patch itself, but we’re getting short on args. The current implementation is badly limited to 10 arguments. This will make adapting make reconf quite hard (it passes all arguments at once). Do you have some plans regarding that?

Also, I was having problems with voice builds. Well, I don’t have any voice engine installed, but maybe you can take another look at it?

Actually, I already saw that fancy use of the command line arguments. Maybe a simple “$@” can fix the problem, but I need to investigate.
Probably a clearer way to manage the arguments should be implemented. I will try to rewrite it without change the script logic.
Thanks for the warning.

That rewrite should probably done before this patch, what do you say?

It would be awesome if you volunteer for that. It’s obvious I fail at this thing :)

Absolutely yes.
The major problem is that I’m thinking to completely rewrite the script, but I don’t know the use of the different compiler options, so a slight mistake on reproducing the same use of them could lead to a big headaches. ;-) Anyway I will try.

Completely rewriting seems a bit exaggerated. Is there any need to?

Ok, “completely” is really exaggerated. I will concentrate just on the arguments.

Sync’ed against current build (r21475).
No changes introduced yet about command line arguments as discussed earlier.

This patch, applied after “build-9400configure-args_v5.0.patch” of the previous comment, normalize the script indentation ( vim: :set shiftwidth=4 tabstop=4 expandtab).

Any progress?

PS: We don’t want the indentation changes I think.

I’m sorry, Thomas, I started working hard again, so my spare time is reduced!
I hope to complete the arguments management soon.
OK, for the indentation, I did it just because I found it a little bit fuzzy! ;-)

Here it is the “final” patch.
I’m not sure about the use of the options –ccache and –no-ccache, but I think to be maintained the original behaviour.
Note: some options work together (i.e. –type=av –encopts=’-c 10 -q 10’). If you want to leave an option value empty, set it to a blank, like –type=av –ttsopts=’ '

I’ll have a look!


Available keyboard shortcuts


Task Details

Task Editing