Update Examples to not build runtime library

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@6415 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
John Lenz 2004-10-17 19:56:35 +00:00
commit d33f398c63
18 changed files with 25 additions and 97 deletions

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -lruntime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' perl5_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='baseclass' INTERFACE='base.i' perl5_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,8 +23,6 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
libruntime.so can be loaded.
- Run the test as described above
Windows:

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -l_runtime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' python_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='base' INTERFACE='base.i' python_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
@ -18,6 +16,6 @@ all::
clean::
$(MAKE) -f $(TOP)/Makefile python_clean
@rm -f foo.py bar.py spam.py base.py runtime.py
@rm -f foo.py bar.py spam.py base.py
check: all

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,8 +23,6 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
lib_runtime.so can be loaded.
- Run the test as described above
Windows:

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -l_runtime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' python_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='base' INTERFACE='base.i' python_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,7 +23,5 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
lib_runtime.so can be loaded.
- Run the test as described above

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -lruntime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' ruby_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='base' INTERFACE='base.i' ruby_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,8 +23,6 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
libruntime.so can be loaded.
- Run the test as described above
Windows:

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -lruntime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' ruby_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='base' INTERFACE='base.i' ruby_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,7 +23,5 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
libruntime.so can be loaded.
- Run the test as described above

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime

View file

@ -1,11 +1,9 @@
TOP = ../..
SWIG = $(TOP)/../swig
SWIGOPT = -noruntime
LIBS = -L. -lruntime
SWIG = $(TOP)/../preinst-swig
SWIGOPT =
LIBS =
all::
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='-runtime' \
LIBPREFIX='lib' TARGET='runtime' INTERFACE='runtime.i' tcl_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \
LIBS='$(LIBS)' TARGET='base' INTERFACE='base.i' tcl_cpp
$(MAKE) -f $(TOP)/Makefile SWIG='$(SWIG)' SWIGOPT='$(SWIGOPT)' \

View file

@ -15,12 +15,7 @@ a separate C++ class.
Each module used %import to refer to another module. For
example, the 'foo.i' module uses '%import base.i' to get
definitions for its base class. These modules do not generate
any runtime code (-noruntime commandline option).
The runtime.i file is an empty SWIG module which will generate
the runtime library code for sharing amongst the other modules
(uses -runtime commandline option).
definitions for its base class.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
@ -28,8 +23,6 @@ type checking will work correctly.
Unix:
-----
- Run make
- Make sure your LD_LIBRARY_PATH includes the current directory so that
libruntime.so can be loaded.
- Run the test as described above
Windows:

View file

@ -1,3 +0,0 @@
// Empty module for building the runtime library
%module runtime