summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorVolker Grabsch <vog@notjusthosting.com>2012-03-28 14:20:17 (GMT)
committerVolker Grabsch <vog@notjusthosting.com>2012-03-28 14:20:17 (GMT)
commit244bd7b987866808da93e43c831bfbfad5d153a9 (patch)
treef54809e2f85255ce17b3042f5e894aa343d4a1e1 /doc
parent8aa924723db05a1bac211f30e526186f542354f8 (diff)
downloadmxe-244bd7b987866808da93e43c831bfbfad5d153a9.zip
mxe-244bd7b987866808da93e43c831bfbfad5d153a9.tar.gz
mxe-244bd7b987866808da93e43c831bfbfad5d153a9.tar.bz2
Replace links into the web repository from hg.savannah.nongnu.org to github.com
History links have been preserved, though.
Diffstat (limited to 'doc')
-rw-r--r--doc/index.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/index.html b/doc/index.html
index 3208389..adeabfb 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -461,7 +461,7 @@ USE_OSGPLUGIN(&lt;plugin2&gt;)
<p>
You can also browse the
- <a href="http://hg.savannah.nongnu.org/hgweb/mingw-cross-env">web repository</a>.
+ <a href="https://github.com/mxe/mxe">web repository</a>.
</p>
<p>
@@ -919,13 +919,13 @@ USE_OSGPLUGIN(&lt;plugin2&gt;)
For instance,
when adding a GNU library,
you should take a package like
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/gettext.mk">gettext.mk</a>
+ <a href="https://github.com/mxe/mxe/blob/master/src/gettext.mk">gettext.mk</a>
or
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/libiconv.mk">libiconv.mk</a>
+ <a href="https://github.com/mxe/mxe/blob/master/src/libiconv.mk">libiconv.mk</a>
as the base of your work.
When using a SourceForge project,
you could start with a copy of
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/xmlwrapp.mk">xmlwrapp.mk</a>.
+ <a href="https://github.com/mxe/mxe/blob/master/src/xmlwrapp.mk">xmlwrapp.mk</a>.
And so on.
</p>
</li>
@@ -964,7 +964,7 @@ USE_OSGPLUGIN(&lt;plugin2&gt;)
<p>
You might also have to provide a patch for it.
In that case, have a look at other patches such as
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl-2-fix-dinput.patch">sdl-2-fix-dinput.patch</a>.
+ <a href="https://github.com/mxe/mxe/blob/master/src/sdl-2-fix-dinput.patch">sdl-2-fix-dinput.patch</a>.
In particular, each patch file should be named as:
</p>
<pre>PACKAGE-PATCHNUMBER-DESCRIPTION.patch</pre>
@@ -1015,7 +1015,7 @@ https://...</pre>
depending on whether it is a C or C++ library.
To get a clue,
please have a look at existing test programs such as
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl-test.c">sdl-test.c</a>.
+ <a href="https://github.com/mxe/mxe/blob/master/src/sdl-test.c">sdl-test.c</a>.
</p>
<p>
@@ -1023,7 +1023,7 @@ https://...</pre>
you should build the test program in a generic way,
using strict compiler flags.
The last few lines of
- <a href="http://hg.savannah.gnu.org/hgweb/mingw-cross-env/file/tip/src/sdl.mk">sdl.mk</a>
+ <a href="https://github.com/mxe/mxe/blob/master/src/sdl.mk">sdl.mk</a>
will give you a clue.
</p>
</li>