jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update for new runtime library approach (no more -runtime -noruntime)

Browse source 
Comment about inline destructors needed for some compilers added


git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@6535 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-10-27 20:59:55 +00:00
commit 8dced082d4
34 changed files with 109 additions and 336 deletions
Download patch file Download diff file Expand all files Collapse all files

15
Examples/tcl/import/README
View file

@ -17,8 +17,11 @@ 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.
If everything is okay, all of the modules will load correctly and
type checking will work correctly.
If everything is okay, all of the modules will load properly and
type checking will work correctly. Caveat: Some compilers, for example
gcc-3.2.x, generate broken vtables with the inline methods in this test.
This is not a SWIG problem and can usually be solved with non-inlined
destructors compiled into separate shared objects/DLLs.
Unix:
-----
@ -27,10 +30,8 @@ Unix:
Windows:
--------
- Use the Visual C++ 6 workspace file (example.dsw). Build the runtime
project DLL first followed by the other 4 DLLs as they all have a
dependency on the runtime DLL. The Batch build option in the Build menu
is usually the easiest way to do this. Only use the Release builds not
the Debug builds.
- Use the Visual C++ 6 workspace file (example.dsw). The Batch build option
in the Build menu is usually the easiest way to do this. Only use the Release
builds not the Debug builds.
- Run the test as described above