Hey Kartikaya,
Thanks for the hint. Cloning the tinyxml2 repository results in an invalid ref, so it's broken atm; I guess that is the issue. christoph@blackbox:~/Software$ git clone git:// codeaurora.org/platform/external/tinyxml2 Cloning into 'tinyxml2'... remote: Counting objects: 4156, done. remote: Compressing objects: 100% (310/310), done. remote: Total 4156 (delta 3844), reused 4156 (delta 3844) Receiving objects: 100% (4156/4156), 584.85 KiB | 586.00 KiB/s, done. Resolving deltas: 100% (3844/3844), done. Checking connectivity... done. warning: remote HEAD refers to nonexistent ref, unable to checkout. I wanted to use the github repository located at https://github.com/leethomason/tinyxml2 as a replacement. How do I do that? Cheers, ~CM On Sat, Jun 7, 2014 at 6:28 PM, Kartikaya Gupta <[email protected]> wrote: > On 6/6/2014, 19:06, LazerUnicorns Developers wrote: > >> 3. The manifest files are out of date. I can't get anything built due to >> the missing tinyxml / tinyxml2 repositories that are not existing >> (base-caf-jb.xml manifest file). So in order to fix that, I had to fork >> your repositories to get it run properly. That sucks hard if you haven't >> built anything at that time and you have no idea what to do as a newbie. >> > > As far as I can tell the tinyxml and tinyxml2 repositories do exist and > are at the locations specified in the manifest file. You can verify this by > going to a tmp dir somewhere and doing this: > > git clone git://codeaurora.org/platform/external/tinyxml > > git clone git://codeaurora.org/platform/external/tinyxml2 > > and verifying that they clone to your local machine. > > Problems and Questions: >> ======================== >> - How can you build a "flame" variant properly? >> > > The command that you ran (as per your gistfile) should work just fine, as > far as I know. I saw the error in your log with cloning the tinyxml repo - > that might have been an intermittent network problem, or possibly a bad > local configuration on your machine (somebody recently had a problem where > git was automatically using http:// instead of git:// as the clone > protocol, and so it was failing to clone). I would suggest verifying that > you can clone the repo individually using the commands I listed above, and > try running the config.sh script again on a clean repo. > > Hope that helps. > > Cheers, > kats >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
