Chino-- Looks to me like you're on the right path; the article you found seems to be the right recipe (that's what we've been using, anyway). "tizen" is the 3.0 (IVI) branch, so that *is* what you want.
Your repo comand looks correct to me. Maybe the manifest file is temporarily unavailable? "repo init" will download a .gbs.conf file that you should look at; I don't have it available to me at the moment to tell you what you should look for, though. :-( Don't forget the "repo sync"! So that you know, we've had a hard time getting the complete system to build with gbs. We've been told that obs is the right tool and gbs is not, but we don't have enough compute power (yet) to make that one a reality. Of note, it looks like the manifest file has to match up with the branch and label; many of the build errors we're seeing *look* like spec file and versioning type problems though honestly there are a few that look more like coding errors to me. The vast majority of tizen package seem to build for us, but there are 30-40 that do not. And there are some more that we haven't yet tried to build. (See the next section where they talk about circular references.) Make sure you've got enough disk space-- the gbs build (so far) is consuming almost 20GB in addition to the 1-2GB for sources and repositories. Also, you'll need a lot of memory: someone suggested 8GB of memory with 8GB swap space when I ran out of memory using --threads=4 on the command line. To get by on my (underpowered) laptop, I removed the threads line and gave the system 16GB of swap space. It's slow, but it seems to continue to the end now. Let me know if I can be of further help! Paul Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected] ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 On Sun, Sep 8, 2013 at 12:21 AM, Chino Aureus <[email protected]>wrote: > Hi, > > Also, I'm the instructions on this documentation: > *" Creating a Tizen Platform Image from Scratch through Local Build "* > and encountered this error:( > > .... > $ repo init -u ssh://<username>@review.tizen.org:29418/scm/manifest -b > tizen -m ivi.xml > > remote: Counting objects: 20, done > remote: Finding sources: 100% (13/13) > remote: Total 66 (delta 3), reused 64 (delta 3) > Unpacking objects: 100% (66/66), done. > From ssh://review.tizen.org:29418/scm/manifest > * [new branch] master -> origin/master > * [new branch] tizen -> origin/tizen > * [new branch] tizen_2.1 -> origin/tizen_2.1 > * [new branch] tizen_2.2 -> origin/tizen_2.2 > fatal: manifest 'ivi.xml' not available > > ... > > Please help :) > > Thanks > Chino > > > On Sun, Sep 8, 2013 at 2:55 PM, Chino Aureus <[email protected]>wrote: > >> >> Hi, >> >> Just registered on tizen OS development and been reading on the cloning >> and building documentation. >> >> As a starting point, I need on guidance on cloning / downloading the >> source and creating the image for the IVI,( kernel, modules, app/packages >> ) so that I can build exactly the same as the dowloadable IVI image >> builds. >> >> Once I'm successdul at this, I'll be starting contributing to the IVI >> project/s :) >> >> From this command, >> >> gbs clone --packaging-branch=<Branch> tizen:<Gerrit_Project> >> <Local_Project> >> >> >> The documentation says replace Branch with tizen. But I'm not sure what >> branch to put for IVI ad Gerrit Projects. >> >> Also, I've read about getting the source using repo... which one should I >> use :) >> >> Regards and Thanks in advance, >> Chino >> > > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > >
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
