| Re: g++ with IDL call_external [message #45851 is a reply to message #45844] |
Tue, 11 October 2005 05:07   |
Nigel Wade
Messages: 286
Registered: March 1998
|
Senior Member |
|
|
Denis Barkats wrote:
> Hi, I've been trying to use call_external from within IDL to call a
> piece of code that I compiled with g++ instead of gcc. Here is the
> exemple.
>
> i have a file simple.c:
>
> #include <stdio.h>
> #include <stdlib.h>
>
> int Simple() {
> return 13;
> }
>
> Using gcc I do
> -gcc -c simple.c
> -gcc -bundle -flat_namespace -o simple.so simple.o
> which creates the sharable librairie simple.so which I can call from
> IDL as
> -print,call_external('/Users/denis/idl/bicep/simple.so','Sim ple',
> /unload)
> 13
>
> So everything is fine.
> However, now if I use g++
>
> g++ -c simple.c
> g++ -bundle -flat_namespace -o simple.so simple.o
> print,call_external('/Users/denis/idl/bicep/simple.so','Simp le',
> /unload)
> % CALL_EXTERNAL: Error loading sharable executable.
> Symbol: Simple, File =
> /Users/denis/idl/bicep/simple.so
> symbol not found
> it does not seem to work.
>
> DO any of you g++ users have any idea ?
> Thanks
My guess would be that you need to disable the g++ name-mangling. If you
look at the names produced in simple.o by g++ you will see that Simple
has been mangled into something strange like _X6Simplev (the mangled
name includes a signature, to allow overloading). You need to declare
Simple in an extern 'C', to tell g++ that it's a C function, not a C++
one, so overloading and mangling can be disabled.
I'll leave it as an exercise for the OP to determine how to do this
(principally because I can't remember the exact semantics).
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
