Changes between Version 49 and Version 50 of WebKitGTK/StartHacking
- Timestamp:
- Jun 3, 2015, 1:16:17 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WebKitGTK/StartHacking
v49 v50 239 239 {{{ 240 240 #!sh 241 $ Tools/Scripts/run- launcher --gtk241 $ Tools/Scripts/run-minibrowser --gtk 242 242 }}} 243 243 … … 373 373 === Working behind a proxy === 374 374 375 Sometimes you are in a resricted environment and you need your WebKit development environment to work properly behind a proxy, so things like `run- launcher --gtk http://www.webkit.org` will actually work, instead of getting stuck trying to load stuff using the wrong "no proxy" settings.375 Sometimes you are in a resricted environment and you need your WebKit development environment to work properly behind a proxy, so things like `run-minibrowser --gtk http://www.webkit.org` will actually work, instead of getting stuck trying to load stuff using the wrong "no proxy" settings. 376 376 377 377 In order to do that, you would need to build `dconf` inside the jhbuild environment, so glib-networking will be able read your configuration through GSettings properly, instead of just reading the default values from the GSettings memory backend that would be in use otherwise. … … 382 382 }}} 383 383 384 After that, every single thing you do inside the `jhbuild` (e.g. using the `run- launcher` script) should properly pick up your proxy settings and work.384 After that, every single thing you do inside the `jhbuild` (e.g. using the `run-minibrowser` script) should properly pick up your proxy settings and work. 385 385 386 386 === Extending jhbuild with custom modules or newer versions ===