GUI in piCore 8

[mikedev]

I have started compiling Xorg stuffs for the piCore 8 GUI, according to https://www.x.org/wiki/ModuleDescriptions/

Since some package(s) depend on other package(s), any particular "sequence" that will make compiling more straightforward?

Thanks!

[Juanito]

You could check the Xorg section of lfs

[mikedev]

You could check the Xorg section of lfs

Thank you!

But just wonder what the sequence is used to compile the GUI components for piCore in previous versions so that I don't need to re-invent the wheel, since I can't found the ".build" file in the previous v7/v6/v5 of armv6 src repository.
 

[Juanito]

The x86 version of Xorg follows the same sequence as lfs

[Paul_123]

It's not an easy task.    Use the build order in Xorg scripts

First,  Here is the list of dependencies to be able to build, not sure if these all exist yet in piCore 8.x

Code: [Select]

tce-load -i \
gcc.tcz make.tcz automake.tcz m4.tcz libtool.tcz git.tcz glibc_base-dev.tcz \
linux-3.18.y_api_headers.tcz squashfs-tools.tcz python.tcz \
bash.tcz harfbuzz-dev.tcz libudev-dev.tcz libpng-dev.tcz glibc_gconv.tcz \
libgcrypt-dev.tcz python-dev.tcz python-setuptools.tcz grep.tcz pkg-config.tcz zlib_base-dev.tcz bison.tcz \
flex.tcz mtdev-dev.tcz gettext.tcz intltool-dev.tcz freetype-dev.tcz expat2-dev.tcz findutils.tcz fontconfig-dev

Compiler flags are the normal rpi compiler flags

Code: [Select]

export CFLAGS="-march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -O2 -pipe"
export CXXFLAGS="-march=armv6zk -mtune=arm1176jzf-s -O2  -pipe -fno-exceptions -fno-rtti"

When I did it I broke it up in to sections to make it easier to restart if a compile failed.   Or if a specific section needed special configuration switches.

[mikedev]

Just finish compiling lib in Xorg for armv6 (pi Zero) on piCore8 
app will be the next,
xserver will be the last.

Hopefully a GUI can be fired up soon.... 

[mikedev]

After finishing lib and app, get an obstacle in compiling xserver (xorg-server-1.12.2) https://www.x.org/releases/X11R7.7/src/xserver/
Hope someone can give a hint...
glproto can be found in https://www.x.org/releases/X11R7.7/src/proto/

However, I am not able to find the package "gl" anywhere in X.org...
Anyone know where I can get it?

Not sure I am in the right direction or not, when I download mesa-11.2.2 and compile it and hopefully get the gl package, it requires xserver, which actually the goal I need to compile and get.  Is the gl package found in somewhere else than the mesa from freedesktop?

Thanks.


... too long to list ...
checking for glibc...... yes
checking for clock_gettime... yes
checking for a useful monotonic clock ...... yes
checking whether to track client ids... yes
checking for XLIB... yes
checking for GL... no
configure: error: Package requirements (glproto >= 1.4.14 gl >= 7.1.0) were not met:

No package 'gl' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GL_CFLAGS
and GL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

[bmarkus]

gl is not part of X but MESA

[mikedev]

Thanks for the MESA hints!

lotssss of dependency for mesa, trying to resolve one-by-one....

[Juanito]

mesa is not dependent on xorg-server - as said earlier, the easiest thing would be to follow the lfs build order...

[bmarkus]

Just a note, Raspberry Pi is using framebuffer, not too much sense to use GL. Now in Raspbian there is an accelerated VC4 driver available but in binary only. So you can drop MESA at all safely.

[curaga]

FYI, xorg-server 1.12 is from 2012, a very old version.

[mikedev]

Just a note, Raspberry Pi is using framebuffer, not too much sense to use GL. Now in Raspbian there is an accelerated VC4 driver available but in binary only. So you can drop MESA at all safely.

Thanks all!

The MESA is compiled successfully and done.

How can I drop MESA at all safely?  It is because when I compile xorg-server, it mentioned about "gl" package is missing....


FYI, snapshot from mesa compilation...

...
        prefix:          /usr/local
        exec_prefix:     ${prefix}
        libdir:          ${exec_prefix}/lib
        includedir:      ${prefix}/include

        OpenGL:          yes (ES1: yes ES2: yes)

        OSMesa:          no

        DRI platform:    drm
        DRI drivers:     no
        DRI driver dir:  ${libdir}/dri
        GLX:             DRI-based

        EGL:             yes
        EGL platforms:   x11
        EGL drivers:     builtin:egl_dri2 builtin:egl_dri3

        llvm:            no

        Gallium drivers: r300 r600 svga swrast
        Gallium st:      mesa

        Shader cache:    yes
        With SHA1 from:  libnettle

        Shared libs:     yes
        Static libs:     no
        Shared-glapi:    yes
...

Continue working on xorg-server...

[mikedev]

FYI, xorg-server 1.12 is from 2012, a very old version.

Yea, it is...
Since it is my 1st time compiling the GUI/Xorg meta packages, it a good start / learning experience from a release perspective....
https://www.x.org/releases/X11R7.7/src/

Once it's done, I may recompile everything with the latest version from individuals.....  https://www.x.org/releases/individual/

Thanks.

[Paul_123]

Just remove the mesa driver from the build list.   And then there should be a configure option in xorg-server to not use gl or mesa.