10 Jul
2016
10 Jul
'16
11:19 p.m.
Hi.
I've been working on a huge modification for lime-build. The idea was to
simplify it by removing some functions which were not used anymore and
make it more adapted to our current needs. I hope this way we will
manage to use it by default.
I've add a new concept for Profile, which might be for instance:
generic, freifunk or chef (easy configurable in profile.mk). So this
should be enough to compile one of them:
make info
make T=ar71xx P=freifunk
But please, take a look on the README to know more:
https://github.com/libre-mesh/lime-build/tree/v2.0
I've based it on develop, so right now only compiles develop. If
everything works as expected and we all agree, we can migrate the rest
of the branches.
Testing, bugs, pull-request are welcome!
Cheers.
11 Jul
11 Jul
3:35 p.m.
2016-07-11 1:19 GMT+02:00 p4u <pau(a)dabax.net>et>:
I've been working on a huge modification for
lime-build. The idea was to
simplify it by removing some functions which were not used anymore and
make it more adapted to our current needs. I hope this way we will
manage to use it by default.
I've add a new concept for Profile, which might be for instance:
generic, freifunk or chef (easy configurable in profile.mk). So this
should be enough to compile one of them:
make info
make T=ar71xx P=freifunk
But please, take a look on the README to know more:
https://github.com/libre-mesh/lime-build/tree/v2.0
Looks great :D
Thank you Pau!
I like the most the fact that now targets are architecture based and not
anymore device based (now is much more tidy).
I just run it and it works :)
If you want to try it:
git clone https://github.com/libre-mesh/lime-build.git
cd lime-build
git checkout v2.0
make clean
make T=ar71xx P=generic
and the resulting images will be present in the "output" directory.
A question: is it possible to specify a custom LIME_GIT variable? This
would be useful if someone wants to work on his own lime-packages fork.
Maybe even an option for specifying the OpenWrt source URL could be useful
(for working on a OpenWrt fork or even on LEDE?).
What do you think?
Ciao,
Ilario
PS I noticed that in the "images" directory there's a broken link to
../build/develop/bin/ar71xx, in my opinion the "images" directory is not
useful anymore, could we eliminate it?
6:49 p.m.
Thank you for testing Ilario. I added your suggestions.
From the README: Or to use your own LiMe packages git repository and/or
OpenWRT/LEDE (must be executed the first time make is invoked or after
clean).
make LIME_GIT="http://foo.git" T=ar71xx P=generic
OWRT_GIT="http://foo.git"
The images/ directory is not longer in the GIT repository. I think you
should remove the whole lime-build and clone it again with version 2.0
to avoid possible mistakes.
What I would like is to test the resulting firmware images because I'm
not sure about the combination OpenWRT release + packages + luci + etc...
Cheers.
On 11/07/16 17:35, Ilario wrote:
2016-07-11 1:19 GMT+02:00 p4u <pau(a)dabax.net
<mailto:pau@dabax.net>>:
I've been working on a huge modification for lime-build. The idea
was to
simplify it by removing some functions which were not used anymore and
make it more adapted to our current needs. I hope this way we will
manage to use it by default.
I've add a new concept for Profile, which might be for instance:
generic, freifunk or chef (easy configurable in profile.mk
<http://profile.mk>). So this
should be enough to compile one of them:
make info
make T=ar71xx P=freifunk
But please, take a look on the README to know more:
https://github.com/libre-mesh/lime-build/tree/v2.0
Looks great :D
Thank you Pau!
I like the most the fact that now targets are architecture based and
not anymore device based (now is much more tidy).
I just run it and it works :)
If you want to try it:
git clone https://github.com/libre-mesh/lime-build.git
cd lime-build
git checkout v2.0
make clean
make T=ar71xx P=generic
and the resulting images will be present in the "output" directory.
A question: is it possible to specify a custom LIME_GIT variable? This
would be useful if someone wants to work on his own lime-packages fork.
Maybe even an option for specifying the OpenWrt source URL could be
useful (for working on a OpenWrt fork or even on LEDE?).
What do you think?
Ciao,
Ilario
PS I noticed that in the "images" directory there's a broken link to
../build/develop/bin/ar71xx, in my opinion the "images" directory is
not useful anymore, could we eliminate it?
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
11:41 p.m.
2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net>et>:
From the README: Or to use your own LiMe packages git
repository and/or
OpenWRT/LEDE (must be executed the first time make is invoked or after
clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx P=generic
OWRT_GIT="http://foo.git" <http://foo.git>
Wow!
The images/ directory is not longer in the GIT
repository. I think you
should remove the whole lime-build and clone it again with version 2.0 to
avoid possible mistakes.
You're right, it was a directory from the previous lime-build environment :)
What I would like is to test the resulting firmware
images because I'm not
sure about the combination OpenWRT release + packages + luci + etc...
I will try in the next days...
Meanwhile, if someone wants to try the images without running
lime-build-v2.0 again, I put the whole compilation directory here, you can
find the compiled images in the "output" directory:
http://ilario.verona.ninux.org/libre-mesh/lime-build-v2.0-UNSTABLE/
please note that this is *not* a stable Libre-Mesh release, don't use these
images in production and be sure to know how to recover the device is
something goes wrong.
Ciao!
Ilario
12 Jul
12 Jul
8:31 p.m.
2016-07-12 1:41 GMT+02:00 Ilario <iochesonome(a)gmail.com>om>:
Meanwhile, if someone wants to try the images without
running
lime-build-v2.0 again, I put the whole compilation directory here, you can
find the compiled images in the "output" directory:
http://ilario.verona.ninux.org/libre-mesh/lime-build-v2.0-UNSTABLE/
These images resulted in clean OpenWrt, my fault I think, sorry, I issued a
make clean and I'll build again in the same directory.
@Pau, which is the lime-build branch you suggest to use for testing?
10:08 p.m.
Mine are working fine, I'm testing now in RAMIPS and X86 devices.
Use the 15.09 better and pull for the last changes please.
Cheers.
On 12/07/16 22:31, Ilario wrote:
2016-07-12 1:41 GMT+02:00 Ilario <iochesonome(a)gmail.com
<mailto:iochesonome@gmail.com>>:
Meanwhile, if someone wants to try the images without running
lime-build-v2.0 again, I put the whole compilation directory here,
you can find the compiled images in the "output" directory:
http://ilario.verona.ninux.org/libre-mesh/lime-build-v2.0-UNSTABLE/
These images resulted in clean OpenWrt, my fault I think, sorry, I
issued a make clean and I'll build again in the same directory.
@Pau, which is the lime-build branch you suggest to use for testing?
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
13 Jul
13 Jul
12:03 a.m.
2016-07-13 0:08 GMT+02:00 p4u <pau(a)dabax.net>et>:
Mine are working fine, I'm testing now in RAMIPS
and X86 devices.
Yep, now I tested the images produced after the make clean and looks ok.
Use the 15.09 better and pull for the last changes
please.
Ok
Now I changed to the develop lime-build branch:
git checkout develop
make T=ar71xx P=generic J=3 UPDATE=1
but I still have the 15.09 branch of the lime-packages repos, is it normal?
Is it needed a make clean when I change lime-build branch?
Thanks!
Ilario
8:33 a.m.
2016-07-13 2:03 GMT+02:00 Ilario <iochesonome(a)gmail.com>om>:
Now I changed to the develop lime-build branch:
git checkout develop
make T=ar71xx P=generic J=3 UPDATE=1
but I still have the 15.09 branch of the lime-packages repos, is it normal?
I think the problem comes from the fact that in the code simplification
commit the update_all target disappeared from Makefile:
https://github.com/libre-mesh/lime-build/commit/020a14e01249fd993de19f17a41…
11:49 a.m.
Should be fixed in last commit of 15.09 (I'll cherry pick it to develop).
However using the same lime-build tree for develop and 15.09 release is
gonna work only if you perform a "make clean" and change the lime-build
whole branch. I've also commited to not remove output/* when clean. So
you can do:
git checkout 15.09
make T=ar71xx J=4
make clean
git checkout develop
make T=ar71xx J=4
Or another option is to have two lime-build separate clones.
Cheers.
On 13/07/16 10:33, Ilario wrote:
2016-07-13 2:03 GMT+02:00 Ilario
<iochesonome(a)gmail.com
<mailto:iochesonome@gmail.com>>:
Now I changed to the develop lime-build branch:
git checkout develop
make T=ar71xx P=generic J=3 UPDATE=1
but I still have the 15.09 branch of the lime-packages repos, is
it normal?
I think the problem comes from the fact that in the code
simplification commit the update_all target disappeared from Makefile:
https://github.com/libre-mesh/lime-build/commit/020a14e01249fd993de19f17a41…
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
2847
days inactive
2850
days old
8 comments
2 participants
participants (2)
-
Ilario -
p4u