I'm new to this forum and do my first steps in OpenWRT configuration.
Having some basic or advanced linux knowledge - depends on your
definition - and working with linux for the last two decades
Have reading the first step intro as well as the compile instructions.
Was able to generate and load the first image to the SD card and boot
up the PBI-R2.
Now looking for a .config file to get a fast impression which config switches
and which packages are necessary and useful.
My basic goal is to have a separation between my DSL router (FB7560) and
my home lan. Later on I would like to have a DNSSEC relay and a private
inbox/out storage box ( in common slang called private cloud) for data
exchange. And as a final stage a home observation system via webcam and
a alarm guard with mail/voip notification.
Could you please give me some hints for a proper configuration and what is
the efficient way to achieve this goal - cross compile b4 or just install the default
image and compile on the ARM every needed package - I know this will last a while.
As this will be a longer way as I believe I have two R2 in order improve one of
the SBC while the second is already doing his job with a reduced functionality
at the beginning while I doing my first steps.
Many thanks in advance for useful hints and explanations.
What's about cross or onboard compiling?
What's about the minor amount of necessary packages?
Markus
PS.: How to mod the Makefile's that just only one target
will be compiled and not all - what's the main target and
the subtarget (mediatek / mt7623 ??) and where to enter
this? (on cli as env var or inside a config file ??)
According to make help the mentioned question above is
obsolate - right?
make help ...
Run "make menuconfig" to select your preferred configuration for the
toolchain, target system & firmware packages.
Run "make" to build your firmware. This will download all sources, build
the cross-compile toolchain and then cross-compile the Linux kernel & all
chosen applications for your target system.
...
But how rerun the compiler without compiling from the beginning but only the
changed files. Normally make should do this automatically - but the make scripts
seems to initiate always a compilation from the beginning.
Just because make runs through the list of targets it needs to build. It doesn't necessarily mean it will rebuild. If the target is current it will just move on to the next.
The durations for compilation according to LEDE Project build service
are listed below. I listed the most intensive tasks.
A full build last 1 1/2 hour.
But I was thinking that just a make call without any change should be
much shorter then 3 minutes. What I'm doing wrong and how to adapt
this.
MAKEFLAGS+=--debug; MAKEFLAGS+=--trace; make OPENWRT_BUILD=0 QUIET=0
or
MAKEFLAGS+=--debug; MAKEFLAGS+=--trace; make OPENWRT_BUILD=1 QUIET=0
I get depending of the status of the source files
make: 'world' is up to date.
That was what I'm searching for - immediate feedback that all are up to date.
But I have to check if I will get a successful and complete build for the mt7623
when changing some source - have to test.
Once the cross-compile build chain is built, running with ccache, a clean build of OpenWrt takes me about 20 minutes on an i3-7100T, and about 12 minutes on a Ryzen 5 2600X
Have someone proper knowledge concerning the MT7530
in order to enable the missing two NIC's.
With the default BPI-R2 config I get just eth1/2 as physical
interface wan linked logically to MAC of eth1 and lan0-lan3
is linked logically to eth0.
Dose a patch exist to enable eth2/3 in openWRT/LEDE on
BPI-R2.
My corrent build is:
root@LEDE:/# uname -a
Linux LEDE 4.9.44 #0 SMP PREEMPT Tue Jun 26 11:00:25 2018 armv7l GNU/Linux
I was thinking the build process take always the newest kernel via git - is this an con-
figuration issue? How I get 4.16 or 4.18 onto my SBC?
Have found that from github commit list:
So OpenWRT v18.06.1 provides kernel 4.9 und 4.14 - right?
Sorry for confusion and asking?
Markus
|13 days ago |Jo-Philipp... |OpenWrt v18.06.1: adjust config defaults v18.06.1 |commit | commitdiff | tree | snapshot|
|---|---|---|---|
|13 days ago |Jo-Philipp... |rpcd: update to latest git HEAD |commit | commitdiff | tree | snapshot|
|2018-08-15 |Hauke Mehrtens|openssl: update to version 1.0.2p |commit | commitdiff | tree | snapshot|
|2018-08-15 |Hauke Mehrtens|kernel: bump kernel 4.9 to version 4.9.120 |commit | commitdiff | tree | snapshot|
|2018-08-15 |Hauke Mehrtens|kernel: bump kernel 4.14 to version 4.14.63 |commit | commitdiff | tree | snapshot|
Not so much "provides", but "uses" -- Specific architectures (devices) are supported on 4.9 or 4.14 at this time. As far as I know, there is no "choice" in the build environment over which kernel to use for which architecture (though the build system does support a user-supplied kernel tree). The kernel sources are downloaded from "upstream" and then patched, as needed.