Pedro, First of all I'd consider updating. I clicked on your link to tizen and the snapshot is not there. It's been a while since I built an image entirely from source. It takes some time. I tend to focus on building the package I need to change and then make an image from rpm's already built with the code. Sometimes it's necessary to run gbs multipule times. Once some packages are built then others build. It would be important not to clean your GBS-ROOT. But basically to create a custom image all you should need is your modified rpm's and an appropriate kickstart file. I'd suggest looking at the following.
You might add something like this to your .gbs.conf [repo.tizen_ivi] url = http://download.tizen.org/snapshots/tizen/ivi/latest/repos/atom/packages/ to reference the repos at tizen. I hope you already have these but I found these the be excellent sources for building source and images. https://source.tizen.org/documentation/developer-guide/getting-started-guide/building-packages-locally-gbs https://source.tizen.org/documentation/developer-guide/getting-started-guide/creating-tizen-images-mic Once you have a kickstart file it's easy to modify to create the image you want with your own rpm's. I hope this helps guide you. *Art McGee* Infotainment Engineer Jaguar Land Rover North America, LLC 1419 NW 14th Ave, Portland, Oregon, 97209 Jaguar.com <http://jaguar.com/> | LandRover.com <http://landrover.com/> On 21 May 2015 at 07:10, <[email protected]> wrote: > Hello everyone, > > I have tried to build tizen ivi locally using gbs. I have followed the > instructions in > > http://download.tizen.org/snapshots/tizen/ivi/tizen-ivi_20150113.1/ > > > > Unfortunately as you probably can guess form the title, build did not > succeeded. Root causes of failure seem to be > > > > === the following packages failed to build due to missing build > dependencies (442) === > > === the following packages failed to build because export source files to > build environment failed (34) === > > > > build log and my gbs configuration is available in attachment > > > > repo manifest used to clone the sources was ivi.xml from the branch tizen > of the repository /scm/manifest > > > > I someone could point out some directions to the problem. And/or share a > working configuration would be great. > > > > Looking forward for your feedback. > > > > Best Regards, > > Pedro Q. > > > > ---------------------------------------------------------------- > Please note: This e-mail may contain confidential information > intended solely for the addressee. If you have received this > e-mail in error, please do not disclose it to anyone, notify > the sender promptly, and delete the message from your system. > Thank you. > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > -- *Art McGee* Infotainment Engineer Jaguar Land Rover North America, LLC 1419 NW 14th Ave, Portland, Oregon, 97209 Jaguar.com <http://jaguar.com> | LandRover.com <http://landrover.com>
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
