From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Allow users to choose Custom Skeleton directory
Date: Wed, 19 Mar 2008 21:46:24 -0700 (PDT) [thread overview]
Message-ID: <16171529.post@talk.nabble.com> (raw)
In-Reply-To: <47E1E4FE.4090208@speakeasy.net>
Hi,
>
>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.
shaleh, i 2nd you
Ulf Samuelsson, I use most of the stuff that comes with default config.in
but i want to use a different skeleton, with our own customs directories,
file, device nodes. I dont want to add code to all the places inside target,
with board specific parameters. i just want to have my own skeleton and use
default config values. So adding this patch, would allow me to specify
custom skeleton instead of hacing the config files.
Regards
Gururaja
--
View this message in context: http://www.nabble.com/-PATCH--Allow-users-to-choose-Custom-Skeleton-directory-tp16135129p16171529.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-03-20 4:46 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
2008-03-20 4:46 ` Hebbar [this message]
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=16171529.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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