"Fossies" - the Fresh Open Source Software Archive

Member "swig-4.1.1/Examples/README" (30 Nov 2022, 1578 Bytes) of package /linux/misc/swig-4.1.1.tar.gz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 SWIG Examples
    3 The subdirectories of "Examples" named after SWIG's language backends
    4 contain a number of simple examples that are primarily used for testing.
    6 The file 'index.html' is the top of a hyperlinked document that
    7 contains information about all of the examples along with various
    8 notes related to each example.
   10 Note: All of the examples rely upon the Makefile in this directory.
   11 You may need to edit it to reflect the configuration of your machine
   12 in case the configure script guesses incorrect settings.
   15 *** Special note concerning C++ ***
   17 The configure script is currently unable to handle all of the possible
   18 options for producing dynamically loadable C++ extensions.  Here are
   19 the rules of thumb for making C++ work:
   21  -  Try using the C++ as the linker for the shared library.  For example:
   23          g++ -shared $(OBJS) -o module.so
   25  -  If that doesn't work, you may need to explicitly link against some
   26     kind of C++ runtime library.  For example:
   28          ld -G $(OBJS) -L/opt/SUNWspro/lib -lCrun -o module.so
   30     This can be set by modifying the setting of CPP_DLLIBS in the
   31     Makefile.
   34 *** Special note for SWIG Maintainers ***
   36 When you add an example, consider arranging for the example to be also
   37 useful as part of the SWIG testing framework.  To do this, include in
   38 the example makefile a target "check" ("check: all" is sufficient for a
   39 first pass), and add an invocation to ../Makefile.in under target
   40 "check-examples" (or whatever is appropriate).  Later, we can add or
   41 expand the actions under target "check" to do more in-depth testing.