Changes between Version 136 and Version 137 of BuildingGtk

Timestamp:

Mar 18, 2020, 3:29:33 AM (5 years ago)

Author:

Philippe Normand

Comment:

--

BuildingGtk

@@ -15 +15 @@
 = Building WebKitGTK from git =
 
-If you want to do development on WebKit itself, you'll need a git checkout. You'll also need to use our JHBuild moduleset to build several dependencies, as using other versions of dependencies may cause layout tests to fail. '''The following steps are suitable for WebKit development only, not for production builds. Our JHBuild moduleset does not receive security or bugfix updates and it is not suitable for any purpose other than development and running layout tests. Do not run against untrusted websites.'''
+If you want to do development on WebKit itself, you'll need a git checkout. You'll also need to use our Flatpak-based SDK, as using other versions of dependencies may cause layout tests to fail. '''The following steps are suitable for WebKit development only, not for production builds. Our Flatpak SDK does not receive security or bugfix updates and it is not suitable for any purpose other than development and running layout tests. Do not run against untrusted websites.'''
 
 == Getting the source ==
@@ -35 +35 @@
 }}}
 
-     Consider to `export JHBUILD_WIPE_ON_CHANGE=0` because, if this is the first time you compile the environment, it might fail, and running again the command, without this environment variable, the build directory will be wipe out and the build will start all over again.
-
 == Building ==
 
@@ -48 +46 @@
  * You can pass parameters to the make command with the ''--makeargs'' argument.
    * For example, you can pass ''--makeargs="-jXX"'', where XX is an integer, to set the number of threads make will use. The default is one per logical CPU detected, but you might want fewer if it's bogging down your system.
- * JHBuild configuration and module files are stored as `Tools/gtk/jhbuildrc` and `Tools/gtk/jhbuild.modules`.
  * If everything builds properly tests should typically pass on your system. Please file a bug if they do not.
  * If you get build errors saying a library could not be found but you have the appropriate packages installed make sure you have up-to-date multiarch-support and binutils (or binutils-gold) packages.