Mail Archives: cygwin/1998/10/24/09:11:16
Hello all,
>>>>> "MK" == Mumit Khan <khan AT xraylith DOT wisc DOT edu> writes:
MK> Whenver loading fails, and you know that it's there, it's typically a
MK> question of calling the correct "name". For my applications, my load
MK> routines check for "foo" and "_foo" when asked to load "foo" to avoid
MK> MSVC vs GCC symbol naming issues.
I notice the difference between the ones that load and those that don't.
Andrew Mickish's .def has entries in name=name AT nn form while yours has them
in name AT nn form. When I changed yours to the former and changed the printf
to Andrew's jprintf it works too. It would be very nice if dlltool was
documented. I keep trying to guess what the syntax means!
Andrew mentions another gotcha. He says that printf will not work because
stdout is not accessible from cygwin's gcc/g++? Is that correct? It
definitely crashes with a printf in there on the NT box, but on the Sun
and HP we use gcc/g++ also and have no problem executing printf in our JNI
code. On those machines there is a problem calling printf in routines that
the JNI calls, but in the JNI code itself, it seems to work fine. What is
the difference? I noticed your code doesn't use jprintf like Andrew's.
How come?
MK> Are you creating .def files yourself? Are you checking to make sure
MK> that the decoration is correct (stdcall attribute adds those pesky
MK> @[num] at the end of symbols?
No, I let your dllwrap do it. It creates the name AT nn form, and then I go
back and change it to the name=name AT nn form by hand and run the stuff that
dllwrap would have done after the .def is created.
Thanks,
Glen.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -