Hello again,
On 6/7/14, 9:47 PM, LazerUnicorns Developers wrote:
Hey guys,
I wanted to give you an update, I managed to root the device and inspect /
reverse engineer the stuff that is going on there.
good news!
I'm currently trying to port autosign for Linux, so that you can ship ROMs
with your own update.zip on SD card, which eases up installation pretty
much.
Very cool.
2. I have never built anything but gaia, as I can't get through the
config.sh call.
If you read that shell script and trace it out, it's essentially making
a trivial config file (.config) and then doing massively heavy 'repo
sync' which is downloading all the git repositories for all the projects
(gigabytes). This second will fail a few times before the hundred or so
repositories all get downloaded correct; you can run 'repo sync' again
anytime to try again or to update the projects later.
Btw, the 'repo' tool splits the source code repositories (.git
directories) which it puts, by default, in
$b2g_work_dir/.repo/projects/,
from the working copies (i.e. the files) which you see in your B2G
working directory. The 'manifest file' is also in the .repo/ directory.
(So yes, the repo developers decided to store GIGABYTES in hidden
directories; some people don't really understand. However, you *can*
make .repo a symlink to a REPO/ directory to clarify for yourself what
is happening.)
Gaia itself was built successfully and flashed after the
rooting process. As the master variant depends on the new Gecko API, I
guess I have to built everything from scratch
(navigator.mozInputMethod.removeFocus() seems to be not existing in the OEM
Gecko variant, so all select fields are broken :P).
3. I couldn't fix the xml file myself. How can I fix the repo url?
The URL is set in $b2g_work_dir/.repo/manifest.xml
(note the dot in .repo)
which is a symlink to $b2g_work_dir/.repo/manifests/$mydevice.xml. So
backup and hack away to your heart's content.
You set a <remote name=... url=...> block at the top of the file with
the URL. You then, in the individual <project ..> block add two
attributes: remote='$name_used_above' and revision=..
Take a look at hamachi.xml for an example.
The
problem is - as I never built anything yet - I have no idea where the
repository has to be cloned to.
repo takes care of that so you don't need to change anything. It uses
git commands to put the git 'repository' in .repo/projects/ and the
working copy (the files) in the $b2g_work_dir.
Should it land in external/tinyxml2 or platform/external/tinyxml2?
Again, leave in place what is there; you just add to xml attributes to
the file.
It's superconfusing, I have really no idea how to overwrite it correctly as
the platform/external/tinyxml2 is listed nowhere as a remote inside the
base-caf-jb.xml.
If the remote= and revision= are not set, repo uses the defaults which
are set globally for the manifest file.
Please help.
hope that helps,
~adrian
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
