Changes

  sweets sdk/sugar:emulator

  sweets sdk/sugar:emulator

 

 

 

 

 

 

 

During the first launch, sources will be auto-built and kept in internal storage. To make sweets useful for the code you are developing, register sources ([[Platform Team/Recipe Specification|sweets.recipe]] should exist in sources):

During the first launch, sources will be auto-built and kept in internal storage. To make sweets useful for development, checkout developing project sources in sweets:

  sweets checkout [''path-to-sources'']

  sweets checkout [''path-to-sources'']

After that, sources might be launched via sweets by mentioning its ''sweet'' value.

The only thing that is required from sources is having [[Platform Team/Recipe Specification|sweets.recipe]] spec file for non-activity projects or {{Code|activity/activity.info}} (that conforms the same spec) for activities.

sweets ''your-sweet''

After being checked out, this sources might be launched using {{Code|http://sweets.sugarlabs.org/''sweet-value-from-sweets.recipe''}} or just {{Code|''sweet-value-from-sweets.recipe''}}:

Registered projects will be built according to {{Code|[Build]}} section commands in recipe files. In general, for autotools-based projects, there is no further need for the {{Code|sweets}} command, just run {{Code|make install}} to build current sources and copy them to the directory that was specified by {{Code|sweets}} in the configure stage.

sweets ''sweet''

For glucose projects, there is no need even in calling the {{Code|make}} command, python code will be reused from its original place (see {{Code|binding}} options in [[Platform Team/Recipe Specification|sweets.recipe]] files), change the code and restart sugar.

For glucose projects you can find ready-to-use and all time rebased to upstream, projects in [http://git.sugarlabs.org/sdk SDK] http://git.sugarlabs.org project. For now there are two branches: {{Code|master}} for recent trunk and {{Code|master-0.88}} for 0.88 code based on Dextrose-2 patches.

For activities, follow regular activity developing procedure - clone them to {{Code|~/Activities}} directory and run from sugar shell.

Checked out projects will be built according to the {{Code|[Build]}} section commands in {{Code|sweets.recipe}} files. In general, for autotools-based projects, there is no further need for the {{Code|sweets}} command, just run {{Code|make install}} to build current sources and {{Code|make install them}} them to the directory that was specified by {{Code|sweets}} in the configure stage. For glucose projects, there is no need even in calling the {{Code|make}} command, python code will be reused from its original place (see {{Code|binding}} options in [[Platform Team/Recipe Specification|sweets.recipe]] files), change the code and restart sugar.

=== Run sweets from X session ===

=== Run sweets from X session ===