Le mercredi 25 mars 2015 à 11:43 -0400, John Szakmeister a écrit :
Why not just use:
./scripts/config/conf --savedefconfig=config.seed Config.in
When building systems for release, one has to be very careful for
security.
IMHO, I would not leave a toolchain and configuration on a build
On 2015-03-23 10:49, Jean-Michel Pouré - GOOZE wrote:
/target/linux/ar71xx/image/Makefile
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
Pardon my ignorance, I am new to OpenWRT.
If I select target TP-Link TL-WR841ND in target of make-menuconfig
this triggers
On Mon, Mar 23, 2015 at 10:50 AM, Jo-Philipp Wich j...@openwrt.org wrote:
Hi.
Thanks, I got it now. So I should run make oldconfig when compiling
automatically everyday?
The best approach is the following:
- Initially use menuconfig and select stuff as you like
- Extract the delta
On 23 March 2015 at 21:07, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu wrote:
but it works and you can tweak it individually via 'make menuconfig'.
what we do here, is e.g.:
echo .config 'CONFIG_TARGET_ar71xx_generic_TLWR1043=y'
Thanks. Due to ignorance, I could not figure it out.
So my
On 23 March 2015 at 20:07, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu wrote:
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
I am getting confused about the build system.
I am comparing .config generated by buildroot (today's GIT) with
but it works and you can tweak it individually via 'make menuconfig'.
what we do here, is e.g.:
echo .config 'CONFIG_TARGET_ar71xx_generic_TLWR1043=y'
Thanks. Due to ignorance, I could not figure it out.
So my script becomes:
git clone git://git.openwrt.org/openwrt.git openwrt-ar71xx
cd
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
I am getting confused about the build system.
I am comparing .config generated by buildroot (today's GIT) with
https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/config
and this is not the same file.
Obviously, I
* Jean-Michel Pouré - GOOZE jmpo...@gooze.eu [23.03.2015 13:30]:
Obviously, I need a default .config file before using buildroot.
Where is it stored and published?
just type 'make defconfig'.
this is maybe not the config you have found somewhere,
but it works and you can tweak it individually
On 23 March 2015 at 17:49, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu wrote:
/target/linux/ar71xx/image/Makefile
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
Pardon my ignorance, I am new to OpenWRT.
If I select target TP-Link TL-WR841ND in target of make-menuconfig
* Jean-Michel Pouré - GOOZE jmpo...@gooze.eu [23.03.2015 11:28]:
Will it select automatically this .config file:
target/linux/ar71xx/config-3.18
yes. the number is taken from 'include/kernel-version.mk'
bye, bastian
___
openwrt-devel mailing list
* Arjen de Korte arjen+open...@de-korte.org [23.03.2015 16:06]:
So I need to activate compilation with:
echo .config 'CONFIG_PACKAGE_luci=y'
No, you have to run 'make menuconfig' and select the luci package in
there. In many cases, other packages are needed when you select a
package. This
Citeren Jean-Michel Pouré - GOOZE jmpo...@gooze.eu:
Le lundi 23 mars 2015 à 15:18 +0100, Arjen de Korte a écrit :
No, you have to run 'make menuconfig' and select the luci package in
there. In many cases, other packages are needed when you select a
package. This is exactly what menuconfig
Le lundi 23 mars 2015 à 15:18 +0100, Arjen de Korte a écrit :
No, you have to run 'make menuconfig' and select the luci package in
there. In many cases, other packages are needed when you select a
package. This is exactly what menuconfig automates (so making
changes
by hand in the
Hi.
Thanks, I got it now. So I should run make oldconfig when compiling
automatically everyday?
The best approach is the following:
- Initially use menuconfig and select stuff as you like
- Extract the delta compared to the defualt configuration with
scripts/diffconfig.sh:
$
Citeren Jean-Michel Pouré - GOOZE jmpo...@gooze.eu:
Le lundi 23 mars 2015 à 21:21 +0800, Yousong Zhou a écrit :
./scripts/feeds install pkgname will make those packages
visible/available/selectable in menuconfig (creating links in
package/feeds/feedsname/) as the prior update action only
Le lundi 23 mars 2015 à 21:21 +0800, Yousong Zhou a écrit :
./scripts/feeds install pkgname will make those packages
visible/available/selectable in menuconfig (creating links in
package/feeds/feedsname/) as the prior update action only fetches them
down as is.
Thanks!
So I need to activate
/target/linux/ar71xx/image/Makefile
I read buildroot WIKI page:
http://wiki.openwrt.org/doc/howto/build
Pardon my ignorance, I am new to OpenWRT.
If I select target TP-Link TL-WR841ND in target of make-menuconfig
this triggers /target/linux/ar71xx/image/Makefile
Will it select automatically
Le lundi 23 mars 2015 à 16:09 +0100, Bastian Bittorf a écrit :
echo .config 'CONFIG_PACKAGE_luci=y'
make defconfig # (this solves the dependencies)
make
You spotted the right solution, this results in a nice configuration. I
feel that I am now able to automate daily compilation. OpenWRT
Le lundi 23 mars 2015 à 16:09 +0100, Bastian Bittorf a écrit :
echo .config 'CONFIG_PACKAGE_luci=y'
make defconfig # (this solves the dependencies)
make
Thanks. I probably want to go this way for a better automation.
Kind regards,
Gnutella
___
19 matches
Mail list logo
