Hi Joone, I am sorry but there is something I don't understand so let me summarize.
As Quiang said, latest ozone-wayland sources can be found at https://github.com/01org/ozone-wayland.git ~/.gbs.conf has to be set with latest tizen repository Then the only thing to do is: git clone https://github.com/01org/ozone-wayland.git src/ozone cd src/ozone gbs build -A i586 --packaging-dir packaging/rpm --include-all If this is all right then this exatly what I did. Here is my .gbs.conf [general] #Current profile name which should match a profile section name profile = profile.tizen [profile.tizen] #Common authentication info for whole profile #user = #CAUTION: please use the key name "passwd" to reset plaintext password #passwd = obs = obs.tizen #Comma separated list of repositories repos = repo.tizen_latest #repos = repo.tizen_main, repo.tizen_base [obs.tizen] #OBS API URL pointing to a remote OBS. url = https://api.tizen.org #Optional user and password, set if differ from profile's user and password #user = #passwd = #Repo section example [repo.tizen_latest] #Build against repo's URL url = https://download.tizen.org/snapshots/tizen/ivi/ivi/latest/ #url = http://download.tizen.org/releases/daily/tizen/ivi/ivi/latest/repos/ivi/source/, http://download.tizen.org/releases/daily/tizen/ivi/ivi/latest/ #Optional user and password, set if differ from profile's user and password #user = #passwd = #Individual repo is also supported #[repo.tizen_base] #url = http://download.tizen.org/releases/daily/trunk/ivi/latest/repos/base/ia32/packages/ #[repo.tizen_main] #url = http://download.tizen.org/releases/daily/trunk/ivi/latest/repos/ivi/ia32/packages/ 2014-04-15 21:28 GMT+02:00 Hur, Joone <[email protected]>: > Hi Maximilien, > > First, you need to check your development environment. > ozone-wayland rpm build should work fine by just running gbs command like > > $ cd src/ozone > $ gbs build -A i586 --packaging-dir packaging/rpm --include-all > > You should specify the latest repository because ninja was added recently > and also update your local ozone-wayland repository. > The repository you are using is very old, which was built in Aug 23, 2012 > http://download.tizen.org/releases/daily/trunk/ivi/latest/ > > Instead, you have to add the following repository in .gbs.conf > https://download.tizen.org/snapshots/tizen/ivi/ivi/latest/ > > Thanks, > Joone > ________________________________ > From: mouton maximilien [[email protected]] > Sent: Tuesday, April 15, 2014 11:44 AM > To: Zhang, Qiang Z; Hur, Joone; VanCutsem, Geoffroy > > Cc: [email protected] > Subject: RE: ozone-wayland installation > > Hi, > > > > I could solve in part the issue. > > Ozone-wayland is part of chromium project. When you put the folder > ozone-wayland in the src folder of chromium project source (see > https://code.google.com/p/chromium/wiki/LinuxBuildInstructions) and rename > it as ozone, the installation passes the %prep step and continues until > %build with the following output: > > > > + ./build/gyp_chromium --no-parallel -Duse_ash=0 -Duse_ozone=1 -Dchromeos=0 > -Ddisable_nacl=1 -Dpython_ver=2.7 -Duse_aura=1 -Duse_x11=0 -Duse_cups=0 > -Duse_gconf=0 -Duse_kerberos=0 -Duse_system_bzip2=1 -Duse_system_icu=0 > -Duse_system_libexif=1 -Duse_system_libxml=1 -Duse_system_nspr=1 > -Denable_xi21_mt=1 -Duse_xi2_mt=0 -Dtarget_arch=ia32 -Duse_alsa=0 > -Duse_gnome_keyring=0 -Dlogging_like_official_build=1 > -Dtracing_like_official_build=1 -Drelease_unwind_tables=0 > -Dlinux_dump_symbols=0 -Denable_ozone_wayland_vkb=1 > > [ 294s] Traceback (most recent call last): > > [ 294s] File "./build/gyp_chromium", line 17, in <module> > > [ 294s] import vs_toolchain > > [ 294s] File > "/home/abuild/rpmbuild/BUILD/chromium/src/build/vs_toolchain.py", line 21, > in <module> > > [ 294s] import gyp > > [ 294s] ImportError: No module named gyp > > [ 294s] error: Bad exit status from /var/tmp/rpm-tmp.b9PNOs (%build) > > > > > > I think there is still something missing to install gyp in fakeroot. > > > > From: Zhang, Qiang Z [mailto:[email protected]] > Sent: mardi 15 avril 2014 04:52 > To: Hur, Joone; maximouton .; VanCutsem, Geoffroy > Cc: [email protected] > Subject: RE: ozone-wayland installation > > > > This should be the source code issue, or need import external sources. > > > > Add Joone, developer of this project. > > > > Joone, could you please help to answer this question? > > > > > > Thanks > > Qiang > > > > > > From: maximouton . [mailto:[email protected]] > Sent: Monday, April 14, 2014 6:22 PM > To: VanCutsem, Geoffroy > Cc: Zhang, Qiang Z; [email protected] > Subject: Re: ozone-wayland installation > > > > Hi Qiang and Geoffroy, > > > > Thanks for your help. > > > > @Geoffroy: I don't know exactly but what I see is .gbp.conf is very light > compare to the .gbs.conf I have. What I am sure is .gbp.conf is used at > installation start. > > > > > > @Qiang Ok now with the src folder, gbs is able to run ./gbp-flat-tree.sh. > > > > There are still some issues with chromium.spec > > > > What I understood for now is that an archive of src named chromium.tar is > created and copied in > ~/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0/home/abuild/rpmbuild/SOURCES > > Everything then is done in this folder. > > > > With my current settings it fails when trying to copy files from src: > > > > cp -a src/AUTHORS AUTHORS.chromium > > cp -a src/LICENSE LICENSE.chromium > > cp -a src/ozone/AUTHORS AUTHORS.ozone-wayland > > cp -a src/ozone/LICENSE LICENSE.ozone-wayland > > > > %patch1 > > > > Here chromium.spec expect src to contain several files that are not there > since we created it manually. > > For testing I tryied to bypass the error by commenting this and force my > version of chromium.spec with --include-all option. > > Even the next step fails because again chromium.spec is looking for a folder > called build located in src. > > > > > > > > 2014-04-14 10:17 GMT+02:00 VanCutsem, Geoffroy > <[email protected]>: > > Thanks Qiang for clarifying this. > > > > What is gbp and how are .gbs.conf and .gbp.conf different? > > > > Thanks, > > Geoffroy > > > > From: Zhang, Qiang Z > Sent: Monday, April 14, 2014 4:46 AM > To: VanCutsem, Geoffroy; maximouton . > > > Cc: [email protected] > Subject: RE: ozone-wayland installation > > > > Hi Maximilien and Geoffroy, > > > > No need to rename .gbp.conf as .gbs.conf, and .gbp.conf is for gbp used. > > > > I have tried in my local machine, I found it’s a little hack in > packaging/rpm/gbp-flat-tree.sh, which hard code and depend on a src > directory on top of ozone-wayland. > > So, the following command works: > > $ git clone https://github.com/01org/ozone-wayland.git src/ozone-wayland > > $ cd src/ozone-wayland/ > > $ gbs build --packaging-dir=packaging/rpm -A i586 > > > > Thanks > > Qiang > > > > > > From: IVI [mailto:[email protected]] On Behalf Of VanCutsem, > Geoffroy > Sent: Monday, April 14, 2014 12:38 AM > To: maximouton . > Cc: [email protected] > Subject: RE: ozone-wayland installation > > > > Hi Maximilien, > > > > I’m assuming you’re trying to build the git repo that’s here: > https://github.com/01org/ozone-wayland > > > > I’ve never tried myself (yet) but I’ve quickly looked at the code in there > and noticed that there is a file called .gbp.conf [1] which seems related to > the issue you’re facing below. If I understand that file correctly, the idea > is that it should be picked up by GBS automatically… but for that to happen > it should be called ‘.gbs.conf’ (instead of ‘.gbp.conf’). Can you rename it > and try again (you will need to use ‘--include-all’ if you don’t commit this > name change in your local git). > > > > Let us know if that helps! > > > > Cheers, > > Geoffroy > > > > [1] https://github.com/01org/ozone-wayland/blob/master/.gbp.conf > > > > > > From: maximouton . [mailto:[email protected]] > Sent: Sunday, April 13, 2014 5:37 PM > To: VanCutsem, Geoffroy > Cc: Tiago Vignatti; [email protected] > Subject: Re: ozone-wayland installation > > > > Right. gbs was pointing to the wrong URL. I didn't know where to change it. > > > > But still there is a problem may be due to a misconfiguration: > > > > gbs -c ~/.gbs.conf build -A i586 --packaging-dir packaging/rpm/ > --include-all > > info: generate repositories ... > > info: build conf has been downloaded at: > > /var/tmp/netlab-gbs/tizen.conf > > info: start building packages from: /home/netlab/Desktop/ozone-wayland (git) > > 2014-04-13 17:28 +0200 > > info: prepare sources... > > info: start export source from: /home/netlab/Desktop/ozone-wayland ... > > info: Creating (native) source archive chromium.tar from > '0b393ca1c4c4074e20a110413cd4b6e4f15267e7' > > removed ‘/var/tmp/.gbs_export_5KWF0s/chromium.tar’ > > Creating a new /var/tmp/.gbs_export_5KWF0s/chromium.tar from > /home/netlab/src > > tar: src: Cannot stat: No such file or directory > > tar: Exiting with failure status due to previous errors > > error: Couldn't run './gbp-flat-tree.sh': ./gbp-flat-tree.sh returned 2 > > error: <gbs>Failed to export packaging files from git tree > > info: retrieving repo metadata... > > info: parsing package data... > > info: building repo metadata ... > > info: package dependency resolving ... > > warning: no available packages to build. > > info: *** Build Status Summary *** > > === the following packages failed to build because export source files to > build environment failed (1) === > > chromium-35.0.1906.0-0 > > > > === Total succeeded built packages: (0) === > > info: generated html format report: > > /home/netlab/GBS-ROOT/local/repos/tizen/i586/index.html > > info: generated RPM packages can be found from local repo: > > /home/netlab/GBS-ROOT/local/repos/tizen/i586/RPMS > > info: generated source RPM packages can be found from local repo: > > /home/netlab/GBS-ROOT/local/repos/tizen/i586/SRPMS > > info: build logs can be found in: > > /home/netlab/GBS-ROOT/local/repos/tizen/i586/logs > > info: build roots located in: > > /home/netlab/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.* > > error: <gbs>some packages failed to be built > > > > Note that the folder /home/netlab/src nerver existed. > > > > Maximilien > > 2014-04-11 18:23 GMT+02:00 VanCutsem, Geoffroy > <[email protected]>: > > The repo your gbs.conf points to does not exist. You should update it to > point at a valid repo (which matches the Tizen image you want to build this > for). > > Geoffroy > > > -----Original Message----- > From: IVI [mailto:[email protected]] On Behalf Of Tiago Vignatti > Sent: Friday, April 11, 2014 6:16 PM > To: [email protected] > Subject: Re: ozone-wayland installation > > Hi, > > I don't know exactly why you're having this problem; looks more like a > network issue or something. > > In any case, Ozone-Wayland can be seen as a part of Chromium project meaning > that targets like Chromium Browser and Crosswalk are actually the ones > supposed to be built.. you know, with Ozone-Wayland only you cannot do > anything :) But as Joel said, come to #ozone-wayland and we try to track > down together what's going on... > > Tiago > > > On 04/11/2014 10:43 AM, maximouton . wrote: >> >> Recently I discovered this interesting project ozone-wayland. >> I decided to test it on my platform but when trying to build the rpm >> on ubuntu 13.10 I get the folowing: >> >> gbs -v build -A i586 --packaging-dir packaging/rpm/ >> info: generate repositories ... >> debug: fetching >> http://download.tizen.org/releases/daily/trunk/ivi/latest/repodata/rep > >> omd.xml => /var/tmp/netlab-gbs/gbscachedgb1H6/repomd.xml > >> debug: disable HTTP caching >> debug: fetching error:(22, 'The requested URL returned error: 404 Not >> Found') >> ... >> >> Did anybody tried to install ozone-wayland already? > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > > Intel Corporation NV/SA > Kings Square, Veldkant 31 > 2550 Kontich > RPM (Bruxelles) 0415.497.718. > Citibank, Brussels, account 570/1031255/09 > > This e-mail and any attachments may contain confidential material for the > sole use of the intended recipient(s). Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > > > > Intel Corporation NV/SA > Kings Square, Veldkant 31 > 2550 Kontich > RPM (Bruxelles) 0415.497.718. > Citibank, Brussels, account 570/1031255/09 > > This e-mail and any attachments may contain confidential material for the > sole use of the intended recipient(s). Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > Intel Corporation NV/SA > Kings Square, Veldkant 31 > 2550 Kontich > RPM (Bruxelles) 0415.497.718. > Citibank, Brussels, account 570/1031255/09 > > This e-mail and any attachments may contain confidential material for the > sole use of the intended recipient(s). Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
