Changeset 64419b7 for x/lib/webkitgtk2.xml
- Timestamp:
- 08/29/2014 11:34:30 AM (10 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- a9ee0599
- Parents:
- a9f8fb9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
x/lib/webkitgtk2.xml
ra9f8fb9 r64419b7 92 92 93 93 <note><para> 94 WebKit2 links against GTK+ 2 (even if GTK+ 3 is being used), in order to 95 be able to use NPAPI plugins such as Adobe Flash. 94 <application>WebKit2</application> links against<application>GTK+ 95 2</application> (even if <application>GTK+ 3</application> is being 96 used), in order to be able to use NPAPI plugins such as Adobe Flash. 96 97 </para></note> 97 98 … … 131 132 132 133 <para> 133 Upstream standard now is to link this package against GTK+ 3. However, 134 for backward compatibility, manu users need also another instance, linked 135 to GTK+ 2. Both can be installed in the same system, without problem. 136 However, some packages can alternatively be linked to either one. Here, 137 both build methods are presented and recommended to be built, but if you 138 know which one you need, just jump to the respective part. 134 Upstream standard now is to link this package against <application>GTK+ 135 3</application>. However, for backward compatibility, manu users need 136 also another instance, linked to <application>GTK+ 2</application>. Both 137 can be installed in the same system, without problem. However, some 138 packages can alternatively be linked to either one. Here, both build 139 methods are presented and recommended to be built, but if you know which 140 one you need, just jump to the respective part. 139 141 </para> 140 142 141 143 <!-- ==== WebKitGTK+ against GTK+ 3 ====== --> 142 <bridgehead renderas="sect3">Build and install WebKitGTK+ against 143 GTK+ 3</bridgehead> 144 <bridgehead renderas="sect3">Build and install 145 <application>WebKitGTK+</application> against <application>GTK+ 146 3</application></bridgehead> 144 147 145 148 <para> … … 185 188 186 189 <!-- ==== WebKitGTK+ against GTK+ 2 ====== --> 187 <bridgehead renderas="sect3">Build and install WebKitGTK+ against 188 GTK+ 2</bridgehead> 190 <bridgehead renderas="sect3">Build and install 191 <application>WebKitGTK+</application> against <application>GTK+ 192 2</application></bridgehead> 189 193 190 194 <para> … … 196 200 197 201 <para> 198 If you have built and installed the package against GTK+ 3, skip the 199 following command, because the previous docummentation also applies here: 202 If you have built and installed the package against <application>GTK+ 203 3</application>. skip the following command, because the previous 204 docummentation also applies here: 200 205 </para> 201 206 … … 333 338 <listitem> 334 339 <para> 335 contains core JavaScript API functions used by <command>jsc-1</command> 336 and <filename class="libraryfile">libwebkitgtk-1.0.so</filename>. 340 contains core JavaScript API functions used by 341 <command>jsc-1</command> and <filename 342 class="libraryfile">libwebkitgtk-1.0.so</filename>. 337 343 </para> 338 344 <indexterm zone="webkitgtk2 libjavascriptcoregtk-1"> … … 347 353 <listitem> 348 354 <para> 349 contains core JavaScript API functions used by <command>jsc-3</command> 350 and <filename class="libraryfile">libwebkitgtk-3.0.so</filename>. 355 contains core JavaScript API functions used by 356 <command>jsc-3</command> and <filename 357 class="libraryfile">libwebkitgtk-3.0.so</filename>. 351 358 </para> 352 359 <indexterm zone="webkitgtk2 libjavascriptcoregtk-3">
Note:
See TracChangeset
for help on using the changeset viewer.