Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Perry <shaleh@speakeasy.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Allow users to choose Custom Skeleton	directory
Date: Wed, 19 Mar 2008 21:15:58 -0700	[thread overview]
Message-ID: <47E1E4FE.4090208@speakeasy.net> (raw)
In-Reply-To: <047f01c88a0a$8a1ef5d0$070514ac@atmel.com>

Ulf Samuelsson wrote:
> 
> If someone wants to have a custom skeleton, why not
> create support for a new board where the board makefile
> specifies the target skeleton.
> 
> I can't really see why you want to be able to specify a non-existing skeleton.
> 

because not all of us need or want to go through setting up a board, 
project, et al.

At work we use busybox on IA32 for IA32 and I have to use glibc, so I 
use crosstool as an external toolchain. It all works, and works quite 
well. I just hand hacked the config to use my skeleton, but this is 
definitely a better approach.

  reply	other threads:[~2008-03-20  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19  1:06 [Buildroot] [PATCH] Allow users to choose Custom Skeleton directory Hebbar
2008-03-19 21:45 ` Ulf Samuelsson
2008-03-20  4:15   ` Sean Perry [this message]
2008-03-20  4:46     ` Hebbar
2008-04-01  0:12       ` Hebbar

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=47E1E4FE.4090208@speakeasy.net \
    --to=shaleh@speakeasy.net \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox