I understand and agree Tizen Wayland still had dependencies on X11 elements.
Regards Joel -----Original Message----- From: Stéphane Desneux [mailto:[email protected]] Sent: Wednesday, January 08, 2014 11:48 AM To: Clark, Joel Cc: [email protected] Subject: Re: [Dev] Tizen Generic: Pure wayland build issue. Hi Joel, From the runtime point of view, you're right: there's no X11 server running in compatible mode (xwayland). Weston is alone and all graphical clients are necesseraly wayland clients. But from the build and dependencies point of view, the packages pointed by Ronan *require* some X11 libs. Otherwise, the build fails: that's what happens in Tizen:Generic in pure wayland mode where the OBS config defines: with_x=0 and with_wayland=1. We had to temporally set with_x=1 to have a buildable wayland image, but this flag will be removed soon on Tizen:Generic. Just check the list of installed packages in the latest IVI release: http://download.tizen.org/snapshots/tizen/ivi/ivi-release/latest/images/ivi-mbr-i586/tizen_20140107.12_ivi-mbr-i586.packages If you search for 'libX', you'll see that all usual X11 libs are installed: libX11, libXau, libXinerama etc. This means that there are still dependencies on X11 that must be removed. I see at least two cases to fix: - a package has multiple implementations (one for wayland, another one for X perhaps others for directfb etc.). In this case, removing the appropriate BuildRequire in spec files in conjunction with good configure options should do the trick. - a package has no other implementation but X. In this case, I don't see any easy solution: actually the package builds successfully, is installed successfully and is responsible for the installation of X layers (as deps). But it fails at runtime (there's no X server!). So the wayland code must be developped (or activated, or merged from upstream wayland branches etc.). Given the number of packages to fix we have to plan how things should be done. Also note that there are probably more packages than those we listed, as Tizen:Generic doesn't contain every IVI package. Kind regards, Stéphane -- Stéphane Desneux Intel OTC - Vannes/FR Clark, Joel wrote: > Tizen:IVI is currently only "pure wayland platform (no x11)". > > Regards > Joel > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of ronan > Sent: Wednesday, January 08, 2014 8:48 AM > To: [email protected] > Subject: [Dev] Tizen Generic: Pure wayland build issue. > > Hi all, > as you could notice, Tizen project builds for dislay: > - x11 (Tizen:Mobile). > - x11+wayland (Tizen:IVI). > > using macro: > %with wayland > %with x > > meaning: > > | wayland | x | meaning > |--------------------------- > | 0 | 1 | pure X11 platform(no wayland) > | 1 | 0 | pure wayland platform (no X11) > | 1 | 1 | wayland but X compatibility > | 0 | 0 | no X and no wayland > > Currently we are trying to build Tizen:Generic for x and wayland (pure > without x11). > > During the recent build, we noticed some build issues for (pure) wayland. > > In a pure wayland build: > - mesa (mesa-libGL) does not provide pkgconfig(gl). > - ecore does not provide pkgconfig(ecore-x). > > Package | unresolvable > _____________________________________________________________________ > app-selector nothing provides pkgconfig(ecore-x) > camera nothing provides pkgconfig(ecore-x) > capi-media-player nothing provides libecore_x.so.1()(64bit) > capi-network-nfc nothing provides libecore_x.so.1()(64bit) > capi-system-system-settings nothing provides libecore_x.so.1()(64bit) > data-provider-master nothing provides pkgconfig(ecore-x) > data-provider-slave nothing provides pkgconfig(ecore-x) > draglock nothing provides pkgconfig(ecore-x) > emotion nothing provides pkgconfig(ecore-x) > nothing provides pkgconfig(evas-opengl-x11) > enlightenment nothing provides pkgconfig(ecore-x) > expedite nothing provides pkgconfig(gl) > image-viewer nothing provides pkgconfig(ecore-x) > libGLU nothing provides pkgconfig(gl) > lockscreen nothing provides pkgconfig(ecore-x) > nfc nothing provides pkgconfig(ecore-x) > nfc-manager nothing provides pkgconfig(ecore-x) > player nothing provides pkgconfig(ecore-x) > settings nothing provides pkgconfig(ecore-x) > system-settings nothing provides pkgconfig(ecore-x) > syspopup nothing provides libecore_x.so.1()(64bit) > nothing provides pkgconfig(ecore-x) > webkit2-efl nothing provides pkgconfig(gl) > wrt nothing provides pkgconfig(gl) > wrt-installer nothing provides pkgconfig(ecore-x) > wrt-plugins-common nothing provides libecore_x.so.1()(64bit) > xf86-video-intel nothing provides pkgconfig(gl) > > > QUESTIONS: > (1) Do some actions have been taken to solve those issues? > > (2) should I post a bug for each package? > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
