All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Wilke <kenneth.wilke@RACKSPACE.COM>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
	OpenBMC Patches <openbmc-patches@stwcx.xyz>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH openbmc] Added ubuntu dependencies to readme
Date: Wed, 16 Dec 2015 13:43:45 +0000	[thread overview]
Message-ID: <1450273434139.10801@RACKSPACE.COM> (raw)
In-Reply-To: <87si327vzr.fsf@birb.au.ibm.com>

I like the idea of having Dockerfiles handy to aid in the process of automating builds and stuff, and providing an easy means to test on various distros. I'd like to see the dependencies and build procedures documented outside of code as well.

Thanks,
Kenneth

From: Stewart Smith <stewart@linux.vnet.ibm.com>
Sent: Wednesday, December 16, 2015 12:23 AM
To: OpenBMC Patches; openbmc@lists.ozlabs.org
Cc: Kenneth Wilke
Subject: Re: [PATCH openbmc] Added ubuntu dependencies to readme

OpenBMC Patches <openbmc-patches@stwcx.xyz> writes:
> From: kenneth-wilke <kenneth.wilke@rackspace.com>
> ---
>  README.md | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/README.md b/README.md
> index 49d4f94..0df0ad4 100644
> --- a/README.md
> +++ b/README.md
> @@ -8,9 +8,15 @@ OpenBMC uses Yocto/Open-Embedded for a build system, which supports an
>  out-of-tree build.  It is recommended that you create an empty directory
>  somewhere to hold the build.  This directory will get big.
>
> +On Ubuntu 14.04 the following packages are required to build the default target
> +```
> +sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
> +```
> +
>  To start a build:
>
> +```
>      cd <builddir>
>      . <repodir>/openbmc-env
>      bitbake obmc-phosphor-image
> -
> +```

(not saying you have to do this)

But i've been experimenting with including a skeleton Dockerfile in
projects to say "here are the build deps on platform X" which is then
programatically testable.

Might be worth it here too.


      reply	other threads:[~2015-12-16 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 22:20 [PATCH openbmc] Added ubuntu dependencies to readme OpenBMC Patches
2015-12-15 22:20 ` OpenBMC Patches
2015-12-16  6:23   ` Stewart Smith
2015-12-16 13:43     ` Kenneth Wilke [this message]

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=1450273434139.10801@RACKSPACE.COM \
    --to=kenneth.wilke@rackspace.com \
    --cc=openbmc-patches@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    /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.