<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openembedded-core.git/oe-init-build-env-memres, branch dora</title>
<subtitle>Mirror of openembedded-core</subtitle>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/'/>
<entry>
<title>oe-init-build-env-memres: Unset BBSERVER if already set</title>
<updated>2013-10-04T17:25:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2013-10-04T13:17:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=f54bb9e7897e6e68acb7b4f88d998fdb149a7e47'/>
<id>f54bb9e7897e6e68acb7b4f88d998fdb149a7e47</id>
<content type='text'>
When starting a new server we don't want bitbake to connect to an existing
server so ensure BBSERVER is unset.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When starting a new server we don't want bitbake to connect to an existing
server so ensure BBSERVER is unset.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>oe-init-build-env-memres: use shell instead of Python to show the port number</title>
<updated>2013-09-26T16:08:09+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2013-09-26T15:11:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=024e95696bad8f2ff09e1fda28c96d89d10999a1'/>
<id>024e95696bad8f2ff09e1fda28c96d89d10999a1</id>
<content type='text'>
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Add memory resident bitbake script</title>
<updated>2013-08-26T10:23:43+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2013-08-23T16:28:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=52c7f8bba86a43b89f24a23d545c99d75b67555f'/>
<id>52c7f8bba86a43b89f24a23d545c99d75b67555f</id>
<content type='text'>
This adds an init script which instead of the standard bitbake, launches
a memory resident bitbake, defaulting to port 12345. It expects a port
number to use as the first option.

Right now this is experimental but I think its probably worth wrapping
up in a form people can more easily experiment with it. There are some
known issues:

a) It throws some debug output due to the lack of a UI which we need
   to clean up
b) It should probably be able to auto select a free port
c) You get a nice backtrace if you specify a build directory but
   not a port number

I'd also highlight there are security issues here if you don't trust
users who can connect into localhost. We might need to look at named
pipes or something similar for something limited to the current user.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds an init script which instead of the standard bitbake, launches
a memory resident bitbake, defaulting to port 12345. It expects a port
number to use as the first option.

Right now this is experimental but I think its probably worth wrapping
up in a form people can more easily experiment with it. There are some
known issues:

a) It throws some debug output due to the lack of a UI which we need
   to clean up
b) It should probably be able to auto select a free port
c) You get a nice backtrace if you specify a build directory but
   not a port number

I'd also highlight there are security issues here if you don't trust
users who can connect into localhost. We might need to look at named
pipes or something similar for something limited to the current user.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
