There's another better choice: use Tizen 3.0 mobile repo, which contains the same base packages (including tool chains and cross compiling tools) with tizen 3.0 ivi.
Step 1: Clone Tizen 3.0 ivi source code: You can follow gbs document Step 2: Update .gbs.conf in topdir of Tizen source, which is downloaded using repo command: [general] tmpdir=/var/tmp/ profile = profile.tizen3.0_ivi_arm work_dir=. [repo.ivi_release] url=http://download.tizen.org/snapshots/tizen/rd-pq/tizen_20131202.3/ [profile.tizen3.0_ivi_arm] repos=repo.ivi_release buildconf=~/ivi.conf Please note that, the buildconf is the customized one(attached) using: http://download.tizen.org/releases/daily/tizen/ivi/ivi/latest/builddata/42ddd32831ab4380781e0a3fbdb1a3d21d8bee8784892267292b18617d180af8-build.conf The changes of the ivi build conf is update cross compiler package. Step 3 building: $ nohup gbs build -A armv7l --threads=4 --exclude=texinfo >ivi-arm.log 2>&1 & There's a cycle dependency, so one package (texinfo) should be excluded in the first building. Thanks Qiang From: [email protected] [mailto:[email protected]] On Behalf Of Clark, Joel Sent: Tuesday, December 3, 2013 11:19 AM To: Prathamesh P Ghanekar; [email protected] Cc: Vidyesh Nabar; Jay D Bhatt Subject: RE: Cross compiling x86 based packages for ArmV7l using GBS build I'm certainly no expert on either how to build Tizen or ARM releases. However there are very significant fundamental changes between Tizen 2.0 and Tizen 3.0, so trying to add a few 3.0 packages to a 2.0 build may not be the best approach. I think it would be better to find the list of packages in 2.0 that are needed for ARM board support (perhaps starting with those packages in the IVI-Panda 2.0 that are not in the ivi-x86 2.0 build, and then figure out how to port them to Tizen 3.0. Regards Joel From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Prathamesh P Ghanekar Sent: Monday, December 02, 2013 6:56 PM To: [email protected]<mailto:[email protected]> Cc: Vidyesh Nabar; Jay D Bhatt Subject: Cross compiling x86 based packages for ArmV7l using GBS build Hello, I am working on Tizen3.0 IVI. I wish to build my custom image for Armv7l based architecture using GBS build. So, there can be 2 approaches I can think of. Approach 1: 1) Take latest IVI-panda release as a baseline (https://download.tizen.org/releases/previews/2.0/). 2) List the IVI specific projects in the manifest of Tizen-3.0-IVI. 3) Locally build the projects which were absent in IVI-panda release, but are present in 3.0-IVI. Approach 2: 1) Take latest IVI-panda release as a baseline. (https://download.tizen.org/releases/previews/2.0/). 2) List the latest IVI specific packages in 3.0-IVI release (but are built for x86). 3) Take the source code (src.rpm ) of those packages and manually cross compile each of them, and generate RPMs. Which one of the two approaches shall I go for? Or some entirely different approach is needed!! If I go by approach 1, how can I set cross compiler path for the 'gbs build' command? Thanks and regards, Prathamesh Ghanekar ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Information contained and transmitted by this e-mail is confidential and proprietary to iGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or [email protected]<mailto:[email protected]>. iGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of iGATE. iGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While iGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about iGATE please visit www.igate.com<http://www.igate.com>. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ivi.conf
Description: ivi.conf
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
