AW: AW: cygwin.rules - Enabling shared libXt finally?

2003-10-22 Thread Ralf Habacker
No, there is no functional changes. I only want to make sure, that no c function in Intrinsic.c can use the symbol _y (in c 'y'), so this patch renames it to __$XtInherit, which isn't usable for c functions. BTW: I was very in rush while doing the last patch, which may fails to be applied. The sy

Re: AW: cygwin.rules - Enabling shared libXt finally?

2003-10-21 Thread Harold L Hunt II
I would be okay with that if it happened. I am the one that recompiled lesstif and I don't think that the maintainers of other Xt-dependent apps have recompiled yet. However, if it isn't a big deal then I will wait until the 4.4.0 release to make this change. 4.4.0 should be released around D

Re: AW: cygwin.rules - Enabling shared libXt finally?

2003-10-21 Thread Charles Wilson
Errm, this isn't going to change the public interface is it? That is, if Harold releases another libXt with this change, would that break the recently re-compiled and released lesstif, etc etc? -- Chuck Ralf Habacker wrote: Not sure I understand. What should be changed in the current version

AW: cygwin.rules - Enabling shared libXt finally?

2003-10-21 Thread Ralf Habacker
Harold > > Not sure I understand. What should be changed in the current version of > the Xt code? only note 1, chaning the label. The second note is only for completeness. > Attached are my curent xc/lib/Xt/[Initialize.c|IntrinsicP.h] files. > Please send a diff against these if anything