From: Saul Wold <sgw@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: FW: curious about ref manual, sec 6.1.11, oe-init-build-env-memres
Date: Wed, 06 Nov 2013 12:38:13 -0800 [thread overview]
Message-ID: <527AA8B5.8060603@linux.intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983F44CAE@ORSMSX101.amr.corp.intel.com>
On 11/06/2013 11:11 AM, Rifenbark, Scott M wrote:
> Anyone know this?
>
>> -----Original Message-----
>> From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
>> Sent: Wednesday, November 06, 2013 10:48 AM
>> To: Rifenbark, Scott M
>> Subject: curious about ref manual, sec 6.1.11, oe-init-build-env-memres
>>
>>
>> i've never used that memory-resident version of bitbake -- it's not clear from
>> that section whether you need to start bitbake running before you run that
>> script.
>>
Running that scripts will start the server at the default port of 12345
and setup the default "build" directory.
>> that is, it's not really *explicitly* explained whether running that script with a
>> port number *starts* the bitbake server. does it?
>>
Yes, running the script with a port number will start the server using
that port number.
The bitbake -m command will Stop the server.
Sau!
>> rday
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-11-06 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1311061346180.25975@oneiric>
2013-11-06 19:11 ` FW: curious about ref manual, sec 6.1.11, oe-init-build-env-memres Rifenbark, Scott M
2013-11-06 20:38 ` Saul Wold [this message]
2013-11-06 20:41 ` Robert P. J. Day
2013-11-07 15:35 ` Rifenbark, Scott M
2013-11-07 16:37 ` Rifenbark, Scott M
2013-12-12 1:01 ` Rudolf Streif
2013-12-12 12:44 ` Rifenbark, Scott M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527AA8B5.8060603@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.