summaryrefslogtreecommitdiffstats
path: root/oe-init-build-env-memres
Commit message (Collapse)AuthorAgeFilesLines
* oe-init-build-env-memres: Add auto port functionalityJason Wessel2013-12-021-11/+16
| | | | | | | | | | | In order to run multiple bitbake memory resident servers on the same machine they must each use different ports. This patch works in conjuction with bitbake to make the auto port selection and lazy server startup the default. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Allow startup with and without memresJason Wessel2013-12-021-3/+18
| | | | | | | | | | | | | Use the bitbake --status-only and the fact that bitbake.lock will contain the host name and port to determine when to activate or shutdown the stay resident bitbake server. This allows a end developer to cleanly switch between the two ways to use bitbake as well as enter the memres bitbake server from multiple shells without starting the server if it is already running. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env-memres: Unset BBSERVER if already setRichard Purdie2013-10-041-0/+4
| | | | | | | 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 <richard.purdie@linuxfoundation.org>
* oe-init-build-env-memres: use shell instead of Python to show the port numberRoss Burton2013-09-261-1/+1
| | | | | Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add memory resident bitbake scriptRichard Purdie2013-08-261-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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>