Improving Our Docs
jspaleta at fedoraproject.org
Tue Jul 2 16:31:06 UTC 2013
The list of psuedo-pretty instructions looks more than sufficient in
terms of level of detail. Just one suggestion.
If the set of deps for the patched xserver and mesa are the same as
development tip xserver and mesa, its sufficient to just say that. If
there are any deps beyond what those upstream projects need to build
their development tip, then it is sufficent and necessary to just name
those. Or to restart simply:
"Assume the system is prepped to build the unpatched upstream
dependences as a starting point"
And a couple of other questions.
Daniel, assuming Mir builds.. is this sufficient to get Mir up and
running and test mir native clients in a repeatable way as part the
documented instructions for testing? Same with xmir. If I want to
smoke fvwm2 on top of xmir, is this sufficient? Or do I need to also
build mir capable lightdm as the dm to manage creating the xmir backed
I am a bit concerned that Daniel and Robert are suggesting different
git branches for the patched mesa and xserver. Are they equivalent
for basic smoke testing? Perhaps you guys need to huddle up and come
to agreement as to which specific branches should be codified for
externals now to pull when doing the first build from source,
especially now a new ppa has been created and codified in the docs to
replace the staging ppa. is the new ppa automation pulling for the
branches that Robert pointed me to? I would hope that the specific
branches in the build from source instructions match what is getting
pulled into the ppa automation.
On Tue, Jul 2, 2013 at 2:46 AM, Daniel Holbach
<daniel.holbach at ubuntu.com> wrote:
> Hello everybody,
> On 02.07.2013 00:23, Jono Bacon wrote:
>> This thread has gone quiet. Daniel, I asked you to focus in on improving
>> our docs here, can you provide an update to the list?
>> I think our priorities are:
>> * Build instructions for other distros.
> I talked to several people and together with consulting
> http://unity.ubuntu.com/mir/building_source_for_pc.html and some help
> from IRC, I'd say that the following should help getting mir builds up
> and running. (Please let me know if any essential
> options/flags/build-dependencies are missing.)
> I tested this in an Ubuntu chroot today:
> # for Mir
> <install cmake cmake-data doxygen xsltproc graphviz libboost-all-dev
> protobuf-compiler libegl1-mesa-dev libgles2-mesa-dev
> libglm-dev libprotobuf-dev pkg-config libgoogle-glog-dev
> liblttng-ust-dev libxkbcommon-dev valgrind libdrm-dev
> libgbm-dev> (note that some package names might be different
> for other distros)
> bzr branch lp:mir
> cd mir; mkdir build; cd build
> cmake ..
> make -j8
> sudo make install
> # for mesa
> <install bison expat libexpat-dev llvm libxcb-xfixes0-dev autoconf
> automake libtool libxml2-dev python-libxml2 flex intltool
> git clone https://github.com/RAOF/mesa
> cd mesa
> ./autogen.sh --with-egl-platforms=mir,drm
> sudo make install
> # for xserver
> <install xutils-dev libpixman-1-dev libgcrypt11-dev x11proto-xcmisc-dev
> libxkbfile-dev x11proto-xf86dri-dev x11proto-render-dev
> x11proto-composite-dev x11proto-xinerama-dev
> x11proto-randr-dev x11proto-xf86bigfont-dev x11proto-video-dev
> x11proto-scrnsaver-dev libxfont-dev x11proto-resource-dev
> x11proto-record-dev libpciaccess-dev xfonts-utils
> git clone https://github.com/RAOF/xserver
> cd xserver
> ./autogen.sh --enable-xmir
> make -j8
> Unfortunately during the last step I run into
> http://paste.ubuntu.com/5835758/ - any help with resolving this would be
> Once this is resolved we should be able to update our docs and have a
> "build on non-Ubuntu" section, I guess.
> I'll udpate https://bugs.launchpad.net/mir/+bug/1193261 with my findings.
>> * Guide to building Mir support for a WM.
> I talked to several people and the consensus seemed to be that things
> are moving and changing too quickly right now to be able to document
> anything which doesn't have to be changed in a couple of weeks/days
> again. In https://bugs.launchpad.net/mir/+bug/1193260 I suggested to
> link to code examples.
> Have a great day,
> Get involved in Ubuntu development! developer.ubuntu.com/packaging
> Follow @ubuntudev on identi.ca/twitter.com/facebook.com/G+
More information about the Mir-devel