Hello Norman,
that sounds interesting!
1)
First the versions of the used tools: gcc, swig, python:
PC169/.../simple$ gcc -v
Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: /netrel/src/gcc-3.2-1/configure
Claudius,
I think that your problem is that you are linking C++ dll with gcc
driver. Try to use g++ also for linking, and it should work OK. Or add
-lstdc++ switch ad the end of your link line (but using g++ for linking
C++ modules is generally preferred).
Pavel
[EMAIL PROTECTED] wrote:
Now,
On 11/5/2002 8:01 AM, Schnörr, Claudius Dr. wrote:
Now I wish to build a dynamic module for python in cygwin, which is compiled
with gcc-2.95.
Is the python module API a C++ API (i.e. does it use C++ classes to
communicate with modules)? Or a plain C API? C should be binary
compatible - try
--l76fUT7nc3MelDdI
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Claudius,
On Tue, Nov 05, 2002 at 05:01:23PM +0100, Schn=F6rr, Claudius Dr. wrote:
I would like to know whether a python-build for gcc-3.2 is available
Thank you for your replies, Jason and Shankar.
Unfortunately, it is a C++-based module, because I try to bind a
C++-library, which can no longer be compiled by gcc-2.95, to python by
swig-1.16.
I already tried to build an new python myself, but it failed just at the
beginning of make.
Why this
Claudius Schnörr writes:
Unfortunately, it is a C++-based module, because I try to bind a
C++-library, which can no longer be compiled by gcc-2.95, to python by
swig-1.16.
FYI
I use C++3.2 modules created by swig 1.16 with a 2.95 compiled python
You do have to make the module as a DLL though
6 matches
Mail list logo
