still digging my way through all the new code, so the questions.
first, from what i see, even without running the scripts/feeds
script to update and install anything from the feeds, one can still
*configure* a build, correct? as in, there's nothing required from
downloading from the feeds that is required before running "make
menuconfig", yes?
as a followup to that question, with a fresh checkout, i just did a
"make defconfig" and that seemed to work just fine. i was curious
about what a totally generic "make defconfig" would do, and noticed
that the target chosen was "ar71xx", but it didn't take long to find
scripts/metadata.pl, and the snippet:
sub gen_target_config() {
my @target = parse_target_metadata();
my %defaults;
my @target_sort = sort {
target_name($a) cmp target_name($b);
} @target;
print <<EOF;
choice
prompt "Target System"
default TARGET_ar71xx
reset if !DEVEL
EOF
which is clearly where that is coming from, so that's fine. i'm
assuming all components of the build have default settings or are
based on the selected target.
finally, i was reading the "easy build" page, and this part threw
me -- "Install the feeds":
http://wiki.openwrt.org/doc/howto/easy.build#install.the.feeds
which shows perl code that refers to a variable named "$feed", but
surely that should really be, "Install the packages", no? it's not a
*feed* that's being "installed" in that perl code, it's a *package*,
isn't it?
more later.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users