Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
midori:contribute [2014/03/16 17:13] – kalikiana | midori:contribute [2015/08/30 21:05] – kalikiana | ||
---|---|---|---|
Line 17: | Line 17: | ||
Join [[irc:// | Join [[irc:// | ||
+ | |||
+ | //Note: Midori also has a mirrored room in Slack ([[https:// | ||
+ | |||
====== Contribute other than touching code ====== | ====== Contribute other than touching code ====== | ||
Line 37: | Line 40: | ||
cmake -DCMAKE_INSTALL_PREFIX=/ | cmake -DCMAKE_INSTALL_PREFIX=/ | ||
make | make | ||
- | sudo make install</ | + | sudo make install |
+ | sudo gtk-update-icon-cache / | ||
+ | </ | ||
//Advanced Tip: Pass "-G Ninja" to cmake to use [[http:// | //Advanced Tip: Pass "-G Ninja" to cmake to use [[http:// | ||
If using GTK+3 you'll want to add <code bash> | If using GTK+3 you'll want to add <code bash> | ||
+ | |||
+ | You can build Midori using another C Compiler for example Clang. Just | ||
+ | add -DCMAKE_C_COMPILER=/ | ||
+ | Then you can build following your normal procedure. Like this: | ||
+ | <code bash> | ||
+ | make</ | ||
Midori can be **run without being installed**. | Midori can be **run without being installed**. | ||
Line 69: | Line 80: | ||
<code bash>env MIDORI_DEBUG=help _build/ | <code bash>env MIDORI_DEBUG=help _build/ | ||
+ | |||
+ | Whilst -g is convenient you may want to use proper gdb: | ||
+ | |||
+ | <code bash>gdb | ||
+ | file _build/ | ||
+ | run | ||
+ | … | ||
+ | bt</ | ||
+ | |||
+ | On Windows you can open the folder where Midori is installed and double-click gdb.exe. A black command line window should appear. | ||
+ | |||
+ | <code bash> | ||
+ | run | ||
+ | … | ||
+ | bt</ | ||
To verify a regression you might need to revert a particular change: | To verify a regression you might need to revert a particular change: |