cygwin.rules - Enabling shared libXt finally?

[Harold L Hunt II]

Alexander,

I don't understand how your example code relates to the problem at hand. 
  I have created a more sophisticated example and I wish that you could 
look at it and modify it if it doesn't currently exhibit the problem 
either.  The code is attached, just 'make' it.

Of course, anyone else is free to look at the code and comment.

The code compiles fine for me and gives the following results:

$ ./xtest
x1.callback: 0x4010e0
x2.callback: 0x4010e0


$ ./xtest2
x1.callback: 0x4010f0
x2.callback: 0x4010f0


You can uncomment the DEFINES in Makefile to define SHAREDCODE or not... 
which changes the way that _XtInherit is defined in sharedlib.c.

I am not really sure what it is I am trying to do here.  Making this 
example feature complete will really help me to understand.

Thanks,

Harold

Alexander Gottwald wrote:

> Harold L Hunt II wrote:
> 
> 
>>>gcc -shared -o x1.dll x1.c xtinherit.c
>>
>>                  ^^^^^^      ^^^^^^^^^^^
>>
>>That is the crux of my whole argument, and I believe it is what Alan was
>>trying to tell me to do.  You do *not* link xtinherit.c/o into x1.dll.
>>Instead, only for demonstration purposes, you can link it directly into
>>any executables that link to x1.dll.
>>
>>What is your response to that?
> 
> 
> i686-pc-cygwin32-gcc -shared -o x1.dll x1.c
> /tmp/ccE9Szng.o(.data+0x0):x1.c: undefined reference to `__XtInherit'
> 
> bye
>     ago
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libtest.tar.bz2
Type: application/x-tar
Size: 1063 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-xfree/attachments/20031003/27271913/attachment.tar>