summaryrefslogtreecommitdiffstats
path: root/oe-init-build-env-memres
AgeCommit message (Collapse)AuthorFilesLines
2013-10-07oe-init-build-env-memres: Unset BBSERVER if already setRichard Purdie1-0/+4
When starting a new server we don't want bitbake to connect to an existing server so ensure BBSERVER is unset. (From OE-Core rev: f54bb9e7897e6e68acb7b4f88d998fdb149a7e47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-26oe-init-build-env-memres: use shell instead of Python to show the port numberRoss Burton1-1/+1
(From OE-Core rev: 024e95696bad8f2ff09e1fda28c96d89d10999a1) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-26Add memory resident bitbake scriptRichard Purdie1-0/+55
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. (From OE-Core rev: 52c7f8bba86a43b89f24a23d545c99d75b67555f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>