Platform Team/Guide/Sweets Usage: Difference between revisions
| Line 51: | Line 51: | ||
== Develop == | == Develop == | ||
Cloned projects will be built according to {{Code|[Build]}} section commands in recipe files. In general, for autotools based projects, there is no further need in {{Code|sweets}} command, just run {{Code|make install}} to build current sources and copy them to the directory that was specified by {{Code|sweets}} on configure stage. | |||
For glucose projects, there is no need even in calling {{Code|make}} command, python code will be reused from original place (see {{Code|binding}} options in recipe files), change the code and restart sugar. | For glucose projects, there is no need even in calling {{Code|make}} command, python code will be reused from original place (see {{Code|binding}} options in recipe files), change the code and restart sugar. | ||
For activities, follow regular activity developing procedure - clone them to {{Code|~/Activities}} directory and run from sugar shell. | |||
== Current limitations == | == Current limitations == | ||