On 27 de febrer de 2017 14:11:32 GMT-03:00, Juergen Kimmel <juergenkimmel@gmail.com> wrote:
Hi.
@Ilario
There is not yet lime-packages branch for 17.02 because we are just in
the starting to create this new release. It is not yet an official
release, just a starting point to make it. So for the moment, we will
use "develop" branch.
@Jurgen
Please refer to the lime-build README.md file to understand what Profile
and Target means [1]. Profile makes reference to a "libremesh" flavor,
nothing to do with the hardware.
As Ilario said, the kernel error is nothing important, it is just that
this target does not have a specific kernel configuration (for the
moment only ar71xx-mini has a specific kernel to remove kernel modules
not required and reduce the firmware image size to the minimum possible).
About the @ misplaced, you are right. The commit was not merged into
17.02 branch. Now it is done, so you should "git pull origin 17.02" your
lime-build local repository. Danke!
About mt7620 target, I don't think this hardware is gonna work. The
drivers are kind of abandoned and the support for Ad-Hoc is very poor.
However you can try, in any case I think you must use 802.11s as a link
layer instead of Ad-Hoc.
If you want to create your own menuconfig configuration because your
target does not exist in lime-build you can run:
make T=mt7620 P=generic menuconfig
Then do whatever change you want to do and compile:
make T=mt7620 P=generic J=4
The configuration file will be saved on build/configs directory.
Cheers.
[1] https://github.com/libremesh/lime-build
On 24/02/17 14:58, Juergen Kimmel wrote:
> I started compilation for mt7620 not for ar71xx ??
> No profile for ape522ii? But menuconfig let me choose ape522ii
>
> BTW: misplaced @ in makefile (branch 17.02) line 89 ist still there
>
>
> Ilario <iochesonome@gmail.com> schrieb am Fr., 24. Feb. 2017 um 12:33 Uhr:
>
>> 2017-02-24 12:08 GMT+01:00 Juergen Kimmel <juergenkimmel@gmail.com>:
>>> So I started as well compiling for ZBT APE522ii using menuconfig which
>>> failed.
>>>
>>> At the very beginning I noticed:
>>> "Adding profile packages: lime-full cp: Aufruf von stat für
>>> 'targets/ar71xx.kernel' nicht möglich: Datei oder Verzeichnis nicht
>> gefunden
>>
>> This is normal (maybe there should be a check and not an error? Should
>> be easy to fix, anyone?) in English (for pasting output for debug
>> please use English, prepend "LANG=C " at the beginning of the command
>> line for changing language) I get:
>> cp: cannot stat 'targets/ar71xx.kernel': No such file or directory
>> this means that the profile you're using doesn't have any specific
>> configuration for kernel.
>> For example ar71xx-mini does have one.
>>
>>> Then I tried:
>>> osboxes@osboxes:~/lime-build-17.02$ make T=mt7620 P=ape522ii UPDATE=1
>> J=1
>>> Profile of APE522ii is missing?
>>
>> There's no such profile I think... You can use
>> make info
>> for listing the profiles, you may use the profile "generic".
>> The image for APE522ii should be built for the target you selected.
>>
>>> So why branch=develop?
>>
>> Uh! There's no branch "17.02" in lime-packages, at a certain point
>> (now?) we will need to create that first (devs...?) and then change
>> this line:
>> https://github.com/libremesh/lime-build/blob/17.02/config.mk#L7
>> _______________________________________________
>> lime-users mailing list
>> lime-users@lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>
>
>
> _______________________________________________
> lime-users mailing list
> lime-users@lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
--
./p4u
_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users