X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=README;h=fd832ca94b8e677f28a8952270468ba1c956d764;hb=3ccb027c907f9ee2890028e83b60296204bbf478;hp=3e2ae2d6ad52b7d6c2a53f80af9826104e108573;hpb=836b84a05a3a8e2f9941cdcd01e3c334d2dff15c;p=platform%2Fupstream%2Fdbus.git

diff --git a/README b/README
index 3e2ae2d..fd832ca 100644
--- a/README
+++ b/README
@@ -140,3 +140,24 @@ Note that the high-level bindings are _separate projects_ from the
 main D-Bus package, and have their own release cycles, levels of
 maturity, and ABI stability policies. Please consult the documentation
 for your binding.
+
+Bootstrapping D-Bus on new platforms
+===
+
+A full build of D-Bus, with all regression tests enabled and run, has some
+dependencies which themselves depend on D-Bus, either for compilation or
+for some of *their* regression tests: GLib, dbus-glib and dbus-python are
+currently affected.
+
+To avoid circular dependencies, when bootstrapping D-Bus for the first time
+on a new OS or CPU architecture, you can either cross-compile some of
+those components, or choose the build order and options carefully:
+
+* build and install D-Bus without tests
+  - do not use the --enable-modular-tests=yes configure option
+  - do not use the --enable-tests=yes configure option
+* build and install GLib, again without tests
+* use those versions of libdbus and GLib to build and install dbus-glib
+* ... and use those to install dbus-python
+* rebuild libdbus; this time you can run all of the tests
+* rebuild GLib; this time you can run all of the tests