Problems building Weston/demo applications on the Raspberry Pi
Hi everyone I am trying to build libwayland, Weston and the demo programs on my Raspberry Pi following the guide at http://wayland.freedesktop.org/raspberrypi.html When compiling Weston and the demo programs however, I get the attached error and no Makefile is being created. What confuses me is that the guide says that "When adding --disable-wayland-compositor you can remove the dummy wayland-egl.pc pkg-config file", except that the --disable-wayland-compositor-flag is present by default in the build guide and the wayland-egl.pc file has not been mentioned before at all (i. e. does not seem to belong to the group of pkg-conf files that the guide mentions earlier). Is there something obvious I am missing? Thanks for your support! Kind regards, Silvan autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I /home/pi/local/share/aclocal --force autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoreconf: running: /usr/bin/autoconf --force autoreconf: running: /usr/bin/autoheader --force autoreconf: running: automake --add-missing --copy --force-missing autoreconf: Leaving directory `.' checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking whether make supports nested variables... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking for a sed that does not truncate output... /bin/sed checking build system type... armv6l-unknown-linux-gnueabihf checking host system type... armv6l-unknown-linux-gnueabihf checking how to print strings... printf checking for a sed that does not truncate output... (cached) /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert armv6l-unknown-linux-gnueabihf file names to armv6l-unknown-linux-gnueabihf format... func_convert_file_noop checking how to convert armv6l-unknown-linux-gnueabihf file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DP
Re: Problems building Weston/demo applications on the Raspberry Pi
On Sun, 15 Sep 2013 21:29:24 +0200 Silvan Jegen wrote: > Hi everyone > > I am trying to build libwayland, Weston and the demo programs on my > Raspberry Pi following the guide at > > http://wayland.freedesktop.org/raspberrypi.html > > When compiling Weston and the demo programs however, I get the attached > error and no Makefile is being created. > > What confuses me is that the guide says that "When adding > --disable-wayland-compositor you can remove the dummy wayland-egl.pc > pkg-config file", except that the --disable-wayland-compositor-flag is > present by default in the build guide and the wayland-egl.pc file has > not been mentioned before at all (i. e. does not seem to belong to the > group of pkg-conf files that the guide mentions earlier). > > Is there something obvious I am missing? Hi, the "When adding" refers to the old version of the guide. This is about migrating from a old build where the configure flags were different. That's what the "if you installed it before" meant. Granted, is not too clearly written. I guess we could now remove these leftovers. I see we also need to fix that build guide. Your problem comes from --with-cairo-glesv2, which before just silently fell back to cairo-image, but now triggers an error. --with-cairo-glesv2 should simply be removed from the configure line. Thanks, pq ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Problems building Weston/demo applications on the Raspberry Pi
> the "When adding" refers to the old version of the guide. This > is about migrating from a old build where the configure flags > were different. That's what the "if you installed it before" > meant. Granted, is not too clearly written. I guess we could now > remove these leftovers. That's what I suspected but I wasn't sure. > I see we also need to fix that build guide. Your problem comes > from --with-cairo-glesv2, which before just silently fell back to > cairo-image, but now triggers an error. > > --with-cairo-glesv2 should simply be removed from the configure line. Sadly, that fix was not obvious to me. Removing the flag solved the problem, thanks a lot! In the attached patch I removed the flag and tried to make the text less confusing. Kind regards, Silvan >From 72a2436d1876267d8516a40b3e7efb2f158695e6 Mon Sep 17 00:00:00 2001 From: Silvan Jegen Date: Mon, 16 Sep 2013 18:00:49 +0200 Subject: [PATCH] Building: update the Raspberry Pi weston section Update the Weston autogen.sh flags and make the accompanying text less confusing. --- raspberrypi.html | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/raspberrypi.html b/raspberrypi.html index 44d9ce4..c65d918 100644 --- a/raspberrypi.html +++ b/raspberrypi.html @@ -146,24 +146,24 @@ contains similar files for Android, and will not work. $ git clone git://anongit.freedesktop.org/wayland/weston $ cd weston -$ ./autogen.sh --prefix=$WLD \ ---disable-setuid-install --with-cairo-glesv2 \ +$ ./autogen.sh --prefix=$WLD --disable-setuid-install \ --disable-x11-compositor --disable-drm-compositor \ --disable-fbdev-compositor --disable-wayland-compositor \ ---disable-weston-launch --disable-simple-egl-clients \ ---disable-egl --disable-libunwind --disable-colord \ ---disable-resize-optimization --disable-xwayland-test \ +--disable-weston-launch --disable-simple-egl-clients --disable-egl \ +--disable-libunwind --disable-colord --disable-resize-optimization \ +--disable-xwayland-test \ WESTON_NATIVE_BACKEND="rpi-backend.so" $ make $ make install -When adding --disable-wayland-compositor you can remove the -dummy wayland-egl.pc pkg-config file, if you installed it before. -This makes sure, that toytoolkit (Weston demo programs) does not use Cairo -EGL. EGL does not work for clients due to EGL Wayland platform being -unimplemented on Raspberry Pi. +If you decide to use the --disable-wayland-compositor +flag supplied above you can remove the dummy wayland-egl.pc +pkg-config file which you may have installed from following an older +version of this guide. This flag makes sure, that toytoolkit (Weston +demo programs) does not use Cairo EGL. EGL does not work for clients due +to the EGL Wayland platform being unimplemented on the Raspberry Pi. Weston should work by running weston. Remember to have the environment set up, and it is useful to have an ssh session open to your -- 1.8.4 ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Problems building Weston/demo applications on the Raspberry Pi
On Mon, 16 Sep 2013 18:17:16 +0200 Silvan Jegen wrote: > > the "When adding" refers to the old version of the guide. This > > is about migrating from a old build where the configure flags > > were different. That's what the "if you installed it before" > > meant. Granted, is not too clearly written. I guess we could now > > remove these leftovers. > > That's what I suspected but I wasn't sure. > > > > I see we also need to fix that build guide. Your problem comes > > from --with-cairo-glesv2, which before just silently fell back to > > cairo-image, but now triggers an error. > > > > --with-cairo-glesv2 should simply be removed from the configure line. > > Sadly, that fix was not obvious to me. Removing the flag solved the > problem, thanks a lot! > > In the attached patch I removed the flag and tried to make the text less > confusing. Hey, thanks for the patch! :-) One minor correction: it is not exactly the flag, but removing wayland-egl.pc that makes sure that toytoolkit does not use cairo-egl. Otherwise looks good, and the patch is an improvement even as is. Cheers, pq ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Problems building Weston/demo applications on the Raspberry Pi
> thanks for the patch! :-) You are very welcome! > One minor correction: it is not exactly the flag, but removing > wayland-egl.pc that makes sure that toytoolkit does not use cairo-egl. > Otherwise looks good, and the patch is an improvement even as is. You see, I TOLD you the text is confusing! :-) When I get home from work (in 8 hours...) I will resend a corrected version of the patch. Cheers, Silvan ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
