Xorg server 1.9 minimal

That’s what I’m using for MeeGo now. Autoconf parameters, theeere we go:

--disable-static --disable-aiglx --disable-config-dbus --disable-config-hal --disable-dbe --disable-dga --disable-dpms --disable-dri --disable-glx --disable-glx-tls --disable-int10-module --disable-ipv6 --disable-screensaver --disable-secure-rpc --disable-tcp-transport --disable-vbe --disable-vgahw --disable-xdm-auth-1 --disable-xinerama --disable-xwin --disable-xaa --disable-xace --disable-xdmcp --disable-xf86vidmode --disable-xfree86-utils --disable-xnest --disable-xvmc --disable-libdrm --enable-config-udev --enable-dri2 --enable-null-root-cursor --enable-record --enable-unit-tests --enable-visibility --enable-xorg --with-sha1=libsha1

PS: stop use kdrive hardware servers (Xfbdev and variants). They are dead!

6 thoughts on “Xorg server 1.9 minimal

  1. Can we have a comment or two on Wayland vs X11, like space, sizes, abilities, etc please.


  2. scsijon: it’s basically impossible at this point. Although the future seems more and more clear torwards Wayland for display and window management, the protocol itself is far to be completed. People are using the *demo* implementation, news articles keep talking about its success and a few others are relying on the Wayland protocol to build others protocols (so for instance clients from one implementation won’t run in the other, i.e. zero interoperability).

    The open community surrounding Wayland is great though, and I encourage you to help build the technology :)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s