From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atme l: atngw100/target_skeleton atngw100/target etc...
Date: Tue, 28 Aug 2007 14:26:48 +0200 [thread overview]
Message-ID: <20070828122648.GB24891@aon.at> (raw)
In-Reply-To: <1188289279.7412.1.camel@localhost.localdomain>
On Tue, Aug 28, 2007 at 10:21:19AM +0200, Hans-Christian Egtvedt wrote:
>
>On Tue, 2007-08-28 at 10:10 +0200, Ulf Samuelsson wrote:
>> > Added:
>> > trunk/buildroot/target/device/Atmel/atngw100/target_skeleton/bin/
>>
>> What is up with all the directories? Is not defining them
>> in .../<board>/device_table.txt enough? I find it far better defining
>> them there since the access permissions can be defined as well.
>>
>>
>> Some stuff are needed
>> during the build and
>> the device table is only
>> used when you convert
>> $(TARGET-DIR) to
>> rootfs-avr32.$(fs) which
>> is too late.
>>
>> It can probably be done
>> better
>
>Indeed, the packages failing with an "empty" skeleton should have some
>mkdir -p actions in them IMHO. That way not all targets needs to be
>fixed, but just one package.
Yes, that's the proper thing to do, agree.
next prev parent reply other threads:[~2007-08-28 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 8:10 [Buildroot] svn commit: trunk/buildroot/target/device/Atme l: atngw100/target_skeleton atngw100/target etc Ulf Samuelsson
2007-08-28 8:21 ` Hans-Christian Egtvedt
2007-08-28 12:26 ` Bernhard Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-28 12:55 Ulf Samuelsson
2007-08-28 13:08 ` Hans-Christian Egtvedt
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=20070828122648.GB24891@aon.at \
--to=rep.dot.nop@gmail.com \
--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