All of lore.kernel.org
 help / color / mirror / Atom feed
From: E Robertson <e.robertson.svg@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New OE user question
Date: Mon, 31 Mar 2008 11:19:47 -0500	[thread overview]
Message-ID: <200803311119.53596.e.robertson.svg@gmail.com> (raw)
In-Reply-To: <f96d234e0803310833g4565e51u2abbc47312c05f07@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

> The "User Manual" is maintained in the monotone repo, and can be
> checked out and edited.
>
> http://amethyst.openembedded.net/oe/viewmtn/viewmtn.py/branch/changes/org.o
>penembedded.documentation
>
> Patches welcome.

I'm not sure how your patch system works. I could checkout the documentation 
branch and edit it but should I do a diff and submit it? Or would it be best 
to edit the wiki?

> The rest of the documentation is in a Drupal wiki, and can be edited.
> You may need a user account.
>
> >  I got the tools built and running bitbake 1.8.10 and pulled
> >  org.openembedded.dev branch. I tried to build both nano and helloworld
> > and couldn't get pass the following error. I have chosen the
> > generic-uclibc DISTRO for starters.
>
> Try the angstrom distro first, as I don't think generic is currently
> maintained.  Sigh -- the OeFaq page has been spammed :-(

Would it be better to stick to one distro for the documentation? I think that 
would be best. Having said that, would Angstrom be the best place to start? 
I was looking for a simple distro to start with and I thought Angstrom might 
be a bit bulky. I'll use which ever the suggested one it. 

> This older page will tell you how to set Angstrom to uclibc until I
> figure out how to restore the correct page.
> http://www.openembedded.org/node/28/diff/964/1042




[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

  reply	other threads:[~2008-03-31 16:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 14:07 New OE user question E Robertson
2008-03-31 15:33 ` Cliff Brake
2008-03-31 16:19   ` E Robertson [this message]
2008-03-31 17:12     ` Cliff Brake
2008-03-31 17:09   ` E Robertson
2008-03-31 17:33     ` Cliff Brake
2008-03-31 15:44 ` Leon Woestenberg
2008-03-31 16:12   ` Koen Kooi
2008-03-31 16:26     ` E Robertson
2008-03-31 16:34     ` Geoffrey Wossum
2008-03-31 17:47       ` Leon Woestenberg
2008-04-01  5:45         ` Ulf Samuelsson
2008-03-31 16:01 ` Geoffrey Wossum
2008-04-01  6:40   ` OE Manual: License change? (was: Re: New OE user question) Marcin Juszkiewicz
2008-04-01 11:00     ` OE Manual: License change? Jeremy Lainé
2008-04-01 13:08       ` Leon Woestenberg
2008-04-01 15:27         ` Marcin Juszkiewicz
2008-04-01 15:54     ` Robert Schuster
2008-04-01 20:48       ` Richard Purdie

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=200803311119.53596.e.robertson.svg@gmail.com \
    --to=e.robertson.svg@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.