Platform Team/Guide/Sweets Usage: Difference between revisions
No edit summary |
|||
| Line 32: | Line 32: | ||
sweets -ff make ''sweet'' | sweets -ff make ''sweet'' | ||
=== Run sweets from X session === | |||
Place sweets invocation to {{Code|~/.xsession}} file: | |||
PATH=$HOME/.local/bin:$PATH | |||
sweets sugar | |||
and create {{Code|/usr/share/xsessions/sweets.desktop}} desktop file: | |||
[Desktop Entry] | |||
Encoding=UTF-8 | |||
Name=Sweets | |||
GenericName=Sweets | |||
Exec=/etc/X11/Xsession | |||
Type=Application | |||
== Develop == | |||
Project 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. | |||
== Current limitations == | == Current limitations == | ||