In any moment you can query for your version of the SDK installed in your workstation using the command:
# ./sdk_version
---------------------SDK VERSION INFO---------------------
Your SDK is currently at version 30
----------------------------------------------------------
# ./sdk_update
########### WARNING ###########
An update will revert the settings of the sdk to the defaults that we provide.
If you have made any changes, that you do not want to loose, make sure to create a backup
To store your current configuration use the acme_config tool.
An example of how to do this is shown below
./acme_config save --- where is a name defined by you
To restore those settings call ./acme_config without parameters
Do you want to continue with the update (y/N) ? (default n)
y
Getting newest update script
U .sdk_update
Updated to revision 15.
Running update
Please choose how you want to update :
1.) beta2 testing (stable)
2.) newest state (might not be stable)
3.) choose a revision (might not be stable)
If you want to be on the safe side, choose option 1. This is the latest state known to be stable
If you want new features that might not be thoroughly tested yet choose option 2
If you really know what you are doing :-) choose option 3
Enter your choice please :
2
U .sdk_update
Updated to revision 15.
---------------------SDK VERSION INFO---------------------
Your SDK is currently at version 15
----------------------------------------------------------
This command will compare your version with the newer one present on the Acme Systems Subversion repository and (if you answer yes) will update all the relevant files in your workstation up to obtain a synchronized release of all the files in your SDK copy to the most recent version.
You have a choice to update to the last stable release or to the very latest (bleeding edge) one that can be not so stable yet, but with the most recent additions.
Since the sdk_update is overwriting all the files that are part of the SDK it will overwrite also all modifications done in the make menuconfig, in the make kernelconfig and in the make busybox commands made, leaving you with a fresh updated installation. To be able to save your already modified options you can use the command acme_config to save them in a safe part of the SDK with a proper name, ready to be recalled just after the sdk_update. All the modification made by you on the SDK files will be lost instead if the new version in the subversion repository is updating/changing those files. In this case you have to backup your custom modified files that form part of the SDK.
A very useful script to store complete options and configurations for kernel, busybox applications and drivers desired for a particular specialized image is acme_config
It can be used both to save a set of custom options made with the SDK or to retrieve a desired set among a selection list.
To save the contents of the files:
that represent together the entire number of options that can be choosen in the SDK various configurations, invoke this command:
# ./acme_config save name_of_my_options
With mySpecialFoxOption we mean a particular name that can be of meaning for your particular set of options chosen.
To recall a particular set of options you just invoke:
# ./acme_config *** Setup a default configuration of the SDK *** ================================================ Select wich default configuration you would like to use. It is possible to add your own configuration by doing a acme_config save. Saved configurations: 1. bluetooth-2.6 2. fox-vhdl 3. fox-vhdl-nofb 4. linux-2.4-default 5. linux-2.6-default 6. php-2.4 7. webcam-2.4-B1 8. wifi-2.4-B1 9. wifi-2.4-C1 10. wifi-2.6-B1 11. wifi-2.6-C1 * Which configuration would you like to use ? :
We already arranged several set of options for the most common uses of the Fox software environment. You can use one of them as a starting point from where start to make your additions/variations and then save your work with another configuration name.
Choosing the desired option set and obtain the fimage relative to the option set chosen typing:
# ./configure ... # ./make ...
