You need do only make (and not make install), copy the generated binaries in a bin directory inside the activity directory, and probably you will need start the acivity with a .sh file and set env variables. You can look at the Tuxmath activity as a example.
Gonzalo On Fri, Jun 29, 2012 at 10:59 PM, Sameer Verma <[email protected]> wrote: > On Fri, Jun 29, 2012 at 5:37 PM, Alan Jhonn Aguiar Schwyn > <[email protected]> wrote: > > > > Maybe I don't understand all.. > > When activity launs, calls a sh with the commands that you need to make > the > > binary. After, only calls the binary and start. > > > > Alan > > I was thinking about how we would package the binaries, given that the > .xo activity isn't supposed to install in /usr/local/bin and other > locations. If we bundle the RPM, the olpc user does not have rights to > install the binary. > > Sameer > > > > >> From: [email protected] > >> Date: Fri, 29 Jun 2012 17:35:07 -0700 > >> Subject: compiled to .XO > >> To: [email protected]; [email protected] > > > >> > >> We are looking at an app that goes through the classic "./configure, > >> make, make install" to compile from source. The compile process runs > >> ok (this is on a XO-1). We are also able to run the binary, but I am > >> unclear about how we would package this into a .xo activity. Any > >> pointers? > >> > >> cheers, > >> Sameer > >> _______________________________________________ > >> Devel mailing list > >> [email protected] > >> http://lists.laptop.org/listinfo/devel > _______________________________________________ > Sugar-devel mailing list > [email protected] > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
