|
|
How to Automate Plugin Screenshots1. Modify RockboxYou want Rockbox to start, run your plugin, save a screenshot, and exit. There is a patch in gerrit that demonstrates this for the 2048 plugin: http://gerrit.rockbox.org/r/#/c/1338/ You should be able to modify it so that it runs your plugin instead of 2048. A list of changes you'll need to make is outlined below:
2. Modify your pluginYou need to make the following changes to your plugin:
3. Gut RockboxSince you don't care about other plugins or codecs, you can edit apps/plugins/SOURCES and apps/plugins/SUBDIRS so that only your plugin is built. Also, if you don't need codecs, you can edit the SOURCES files under lib/rbcodec/[codecs,dsp]4. Build and run all targetsNow that your Rockbox has been configured to start your plugin, screen dump, and exit, you need to repeat this process for every target. AmauryPouly was kind enough to provide a script that automates this:cat ../www/buildserver/builds | grep sim | awk 'BEGIN { FS=":"; } { system("rm -rf build && mkdir build && cd build && "$7 " -j9 && make install && xvfb-run ./rockboxui && cp simdisk/*.bmp ../screenshots/ && cd .. && rm -rf build"); }'You will need to edit this to suit your needs. 5. Convert to PNGYou will now have a collection of screenshots for various targets in the screenshots/ directory. You need to make sure they are in the format ss-yourplugin-WxHxD.bmp, and then copy them to the manual/plugins/images directory Here you must convert the BMP images to PNG to ensure that LaTeX recognizes them. NOTE: the default pnmtopng utility produces very poor output. The author used ffmpeg to convert the images. -- FranklinWei - 05 Jun 2016r2 - 02 Apr 2021 - 20:46:06 - UnknownUser
Copyright © by the contributing authors.
|