On Fri, Jun 29, 2012 at 8:48 PM, Mikus Grinbergs mi...@bga.com wrote:
Am attaching an copy of an email I sent earlier to someone with a question
similar to yours. IMHO that email provides a concise how-to guide to
fashioning a bare-bones .xo package.
Great stuff. Someone, be brave and
, the olpc user does not have rights to
install the binary.
Sameer
From: sve...@sfsu.edu
Date: Fri, 29 Jun 2012 17:35:07 -0700
Subject: compiled to .XO
To: sugar-devel@lists.sugarlabs.org; de...@lists.laptop.org
We are looking at an app that goes through the classic ./configure,
make
On Fri, Jun 29, 2012 at 8:48 PM, Mikus Grinbergs mi...@bga.com wrote:
We are also able to run the binary, but I am unclear about
how we would package this into a .xo activity. Any pointers?
Am attaching an copy of an email I sent earlier to someone with a question
similar to yours. IMHO
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
Maybe I don't understand all..When activity launs, calls a sh with the commands
that you need to make thebinary. After, only calls the binary and start.
Alan
From: sve...@sfsu.edu
Date: Fri, 29 Jun 2012 17:35:07 -0700
Subject: compiled to .XO
To: sugar-devel@lists.sugarlabs.org; de
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: sve...@sfsu.edu
Date: Fri, 29 Jun 2012 17:35:07 -0700
Subject: compiled to .XO
To: sugar-devel
:35:07 -0700
Subject: compiled to .XO
To: sugar-devel@lists.sugarlabs.org; de...@lists.laptop.org
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
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.
Easy: no install the binaries.. only use them,,You can compile
We are also able to run the binary, but I am unclear about
how we would package this into a .xo activity. Any pointers?
Am attaching an copy of an email I sent earlier to someone with a
question similar to yours. IMHO that email provides a concise how-to
guide to fashioning a bare-bones .xo
9 matches
Mail list logo
