rockboxui - simulator executable

[mikeage]

Quick question:

when building the simulator, do I need to keep taking the new rockboxui build, or can I stick to the same executable for a while (until I see an SVN change referring to the simulator itself) and only update the archos/.rockbox directory?

Thanks

[safetydan]

Not quite sure what you're asking about here. The simulator isn't all that much different from the targets. Any changes (unless they're hardware specific) will affect the simulator.

[mikeage]

When building the simulator, it builds a full .rockbox directory, just like a regular target. Running "make zip" creates a normal .zip, as well.

It also creates an executable file called rockboxui. This file is not included in the zip, and I'm wondering if that's because, like the fonts, it changes quite infrequently.

Basically, I'm setting up a script to automatically build the simulator many times, so that I can test changes to a plugin I'm writing. The build is done on a remote machine; I'm wondering if I can just transfer the zip file (well, for testing, if I don't do an SVN update, I usually just transfer the .rock itself), or if it's safer and necessary to transfer the executable as well.

[Llorean]

The rockboxui file plays the exact same job on your PC as the rockbox.ipod does on an ipod, or the rockbox.iriver does on an H100 etc.

Basically, it needs to be updated any time you were updating a build. You can't test anything compiled for a player on a PC anyway, as no emulation is done.

[mikeage]

Thanks