-The examples require the Android SDK and Android NDK which can be installed as per instructions in the links. +The examples require the Android SDK and Android NDK which can be installed as per instructions in the links. The Eclipse version is not required for these examples as just the command line tools are used (shown for Linux as the host, but Windows will be very similar, if not identical in most places). Add the SDK tools and NDK tools to your path and create a directory somewhere for your Android projects (adjust PATH as necessary to where you installed the tools):
diff --git a/Doc/Manual/CSharp.html b/Doc/Manual/CSharp.html index e55013b1c..76590d1cc 100644 --- a/Doc/Manual/CSharp.html +++ b/Doc/Manual/CSharp.html @@ -70,7 +70,7 @@ SWIG C# works equally well on non-Microsoft operating systems such as Linux, SolTo get the most out of this chapter an understanding of interop is required. The Microsoft Developer Network (MSDN) has a good reference guide in a section titled "Interop Marshaling". -Monodoc, available from the Mono project, has a very useful section titled Interop with native libraries. +Monodoc, available from the Mono project, has a very useful section titled Interop with native libraries.
-There is growing support for SWIG in some build tools, for example CMake +There is growing support for SWIG in some build tools, for example CMake is a cross-platform, open-source build manager with built in support for SWIG. CMake can detect the SWIG executable and many of the target language libraries for linking against. CMake knows how to build shared libraries and loadable modules on many different operating systems. diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html index b6885b94f..b953eb518 100644 --- a/Doc/Manual/Java.html +++ b/Doc/Manual/Java.html @@ -349,8 +349,6 @@ directory. If that doesn't work, you will need to read the man-pages for your compiler and linker to get the right set of options. You might also check the SWIG Wiki for additional information. -JNI compilation -is a useful reference for compiling on different platforms.
diff --git a/Doc/Manual/Javascript.html b/Doc/Manual/Javascript.html index 613ca99ed..69e6665ea 100644 --- a/Doc/Manual/Javascript.html +++ b/Doc/Manual/Javascript.html @@ -166,7 +166,7 @@ $ make check-javascript-examples V8_VERSION=0x032530 ENGINE=v8
To install node.js you can download an installer from their web-site for Mac OS X and Windows. For Linux you can either build the source yourself and run sudo checkinstall or keep to the (probably stone-age) packaged version. For Ubuntu there is a PPA available.
To install node.js you can download an installer from their web-site for Mac OS X and Windows. For Linux you can either build the source yourself and run sudo checkinstall or keep to the (probably stone-age) packaged version. For Ubuntu there is a PPA available.
$ sudo add-apt-repository ppa:chris-lea/node.js diff --git a/Doc/Manual/Makefile b/Doc/Manual/Makefile index d7011db06..7347691cd 100644 --- a/Doc/Manual/Makefile +++ b/Doc/Manual/Makefile @@ -34,14 +34,6 @@ check: tidy -errors --gnu-emacs yes -quiet Sections.html all=`sed '/^#/d' chapters | grep -v CCache.html`; for a in $$all; do tidy -errors --gnu-emacs yes -quiet $$a; done; -# Check for links which don't work including those generated from the individual .html files into SWIGDocumentation.html -linkchecker: - rm -rf linkchecker-tmp - mkdir linkchecker-tmp - cp SWIGDocumentation.html linkchecker-tmp - cp *.png linkchecker-tmp - (cd linkchecker-tmp && linkchecker -F text --no-warnings SWIGDocumentation.html) - generate: swightml.book swigpdf.book htmldoc --batch swightml.book || true htmldoc --batch swigpdf.book || true @@ -77,9 +69,18 @@ test: validate: all=`sed '/^#/d' chapters`; for a in $$all; do validate --emacs $$a; done; -# Link checking using linkchecker -linkchecker: +# Link checking using linkchecker of the index.html only file (including anchors) +linkchecker1: @echo ----------------------------------------------------------------------- @echo Note linkchecker versions prior to 6.1 do not work properly wrt anchors @echo ----------------------------------------------------------------------- - linkchecker --config=./linkchecker.config index.html + linkchecker --config=./linkchecker.config --anchors index.html + +# Check for links which don't work including those generated from the individual .html files into SWIGDocumentation.html +linkchecker2: + rm -rf linkchecker-tmp + mkdir linkchecker-tmp + cp SWIGDocumentation.html linkchecker-tmp + cp *.png linkchecker-tmp + (cd linkchecker-tmp && linkchecker --config=../linkchecker.config -F text --no-warnings SWIGDocumentation.html) + diff --git a/Doc/Manual/Ocaml.html b/Doc/Manual/Ocaml.html index da20b8da3..b927a7d8f 100644 --- a/Doc/Manual/Ocaml.html +++ b/Doc/Manual/Ocaml.html @@ -80,7 +80,7 @@ variants, functions, classes, etc.If you're not familiar with the Objective Caml language, you can visit -The Ocaml Website. +The Ocaml Website.
31.1 Preliminaries
diff --git a/Doc/Manual/Preface.html b/Doc/Manual/Preface.html index 23481d751..6ddea588a 100644 --- a/Doc/Manual/Preface.html +++ b/Doc/Manual/Preface.html @@ -370,7 +370,7 @@ installation of software you might have. However, this is generally not the rec technique for building larger extension modules. Instead, you should utilize Darwin's two-level namespaces. Some details about this can be found here -http://developer.apple.com/documentation/ReleaseNotes/DeveloperTools/TwoLevelNamespaces.html. +Understanding Two-Level Namespaces. diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html index 373472d86..962ee6843 100644 --- a/Doc/Manual/Python.html +++ b/Doc/Manual/Python.html @@ -2738,7 +2738,7 @@ in Python-2.2, an entirely new type of class system was introduced. This new-style class system offers many enhancements including static member functions, properties (managed attributes), and class methods. Details about all of these changes can be found on www.python.org and is not repeated here. +href="https://www.python.org">www.python.org and is not repeated here.@@ -5690,7 +5690,7 @@ import foo
refers to a top-level module or to another module inside the current package. In Python 3 it always refers to a top-level module -(see PEP 328). +(see PEP 328). To instruct Python 2.5 through 2.7 to use new semantics (that is import foo is interpreted as absolute import), one has to put the following line @@ -5881,7 +5881,7 @@ all overloaded functions share the same function in SWIG generated proxy class.
For detailed usage of function annotation, see -PEP 3107. +PEP 3107.
For details of abstract base class, please see -PEP 3119. +PEP 3119.
For more details about the surrogateescape error handler, please see -PEP 383. +PEP 383.