On 13/08/2015 11:10, [email protected] wrote:
On Thursday, August 13, 2015 at 4:40:23 PM UTC+8, Augustin Trancart wrote:
Seems that your tree points to mozilla-b2g/b2g-manifest instead of
b2g-sprout/b2g-manifest, ie they didn't change the repo in b2g-sprout/B2G.
Can you try with
BRANCH=v1.4 GITREPO=git://github.com/b2g-sprout/b2g-manifest ./config.sh
sprout
?
If it does not work, we'll seek other way to make this command longer ;-)
Good luck!
Augustin Trancart
Phoxygen
On 13/08/2015 10:27, [email protected] wrote:
On Thursday, August 13, 2015 at 4:11:51 PM UTC+8, [email protected] wrote:
On Thursday, August 13, 2015 at 4:00:37 PM UTC+8, Juan Gómez wrote:
Try to run config.sh like this:
BRANCH=v1.4 ./config.sh sprout
and then try to build:
./build.sh showcommands 2>&1 | tee build.log
If there are compiler errors, paste them in http://pastebin.mozilla.org and let
me check.
On Thu, Aug 13, 2015 at 5:05 AM, <[email protected]> wrote:
On Wednesday, August 12, 2015 at 10:38:56 PM UTC+8, Fabrice Desré wrote:
On 08/12/2015 06:54 AM, Juan Gómez wrote:
Well, you should:
1. - Clone B2G port: git clone [email protected]:b2g-sprout/B2G.git
2. - Run: ./config.sh sprout
At first glance, the author didn't upload the manifest file for this
device -- it should be named: sprout.xml, and be located in his fork of
b2g-manifest repo. So, it won't compile, unless you manage to get a copy
of the manifest file elsewhere and run the config.sh command like:
./config.sh sprout manifest_file.xml.
It is in the 1.4 branch. I remember the author telling me he was not
tracking master because he liked the 1.4 homescreen better.
That should not be hard to get working on master though.
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
Well, how can I do it then? Sorry, we're actually just web developers that
wants to create apps for FFOS for personal and community use and we don't
really know much about ROMs and compiling. I would really want to know also how
to compile and maybe choose different versions of the OS too so I can provide
FFOS's to Android One (Sprout) Smartphone users.
We're actually trying but our knowledge when it comes to this compiling thingy
is not that enough...Pls Help...
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
It is still looking for the missing, "sprout.xml"...
https://pastebin.mozilla.org/8842614 I tried all other versions but still...
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
I have a slow internet connection but I think it is working now. Thank you, it
means so much to us and we do really want to create apps for FFOS. (*bow) May I
also ask how to compile it for other versions too like v2.0 if ever that this
will now work so my friends would not have to get back here just to ask this
questions 'coz I believe some of them are a fan of FFOS's 2.0 Elegant UI and
excited for FFOS 2.5?
The first step would be to have your sprout.xml in the v2.0 branch of
the b2g-manifest repo (you'll need to fork it and make your build point
to your fork with GITREPO). Then change revisions in lines 15 to 23 from
'v1.4' to 'v2.0' (and commit them in your branch). That's more or less
what I'm sure about. You can try to build with this and see what happens :-)
I think you don't need to touch lines with revision b2g-4.4.2_r1 (I
guess it's following aosp version numbers?). Seeing flame.xml in the
mozilla v2.0 branch tells me it should work. So line 141 /should/ be
fine as well (cyanogenmod v11 is based on aosp 4.4).
About line 140:
<project name="device-sprout" path="device/google/sprout"
remote="b2g-sprout" revision="v1.4"/>
you don't have v2.0 branch in this repo... But there's only a diff of 2
commits between this branch and cm11 (one behind, one ahead), which
leads me to think that maybe this branch is not well-named. Maybe it
should have been b2g-4.4.2_r1. At least, let's hope for that :-D So
leave it like that for now. Btw you might want to check what commit has
been added in cm11 branch, maybe this v1.4 branch needs it...
Then, all the other lines, I have no clue. Better leave them like that
for now.
Hopefully, some people with more knowledge will step in and correct me!
Good luck for the long road ahead,
Augustin Trancart
Phoxygen
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
