View Single Post
  #11 (permalink)  
Old 04-04-2007, 06:56 PM
schettj's Avatar
schettj
morsus mihi
Offline
Location: Not from around these parts
 
Join Date: Oct 2006
Posts: 3,017
Reputation: 3616
schettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIP
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
I think if you want to get commercial apps in your rom, you should be building it yourself...

Re: the other question of building the rom off the kitchen based on user web interaction. Yeah. Not trivial.

The only rom tools I know of are windows based, although they used to be linux based tools maybe. If they were linux based, building a kitchen as part of a cgi script (ie, based on filling out a form and clicking the BUILD button) wouldn't be too bad, except for the huge load it will put on the machine and the slight hairy issue of dealing with multiple requests at the same time.

If we're stuck with the windows tools we have now, then
* someone has to run a windows-based web server or provide network APIs to drive the tools,
** some of which need to have buttons clicked to proceed,
** none of which have great error reporting if the user selects too many OEMs and the ROM is garbage because it has too much in it,
* you can forget processing multiple build requests at the same time (so, we would need to batch them up, build in series, and maybe email the user a URL to fetch the ROM once its done?)

Icky.