<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
Angus Leeming schrieb:<br>
<br>
<span style="white-space: pre;">> Ralf Habacker wrote:<br>
> <br>
>> On Friday 22 April 2005 13:32, Angus Leeming wrote:<br>
>> <br>
>>> Angus Leeming wrote:<br>
>>> <br>
>>>>> On cygwin I'm using the following switch, which
may help to<br>
>>>>> prevet seg faults. It requires a relink of the
qt-3.dll <br>
>>>>> QMAKE_LFLAGS = <br>
>>>>>
-Wl,--script,$(QTDIR)/mkspecs/cygwin-g++/i386pe.x-no-rdata<br>
>>>> <br>
>>>> Now that is very, very interesting. I'll try it out.
(Am I<br>
>>>> correct to say that only the dll needs to be
re-linked?<br>
>>> <br>
>>> Hi, Ralf.<br>
>>> <br>
>>> I have some good news and some bad news to report.<br>
>>> <br>
>>> a cross-compiled LyX/Win 1.3.x runs beautifully on
Windows, but<br>
>>> only when I use a natively compiled qt3.dll. If I try
and use<br>
>>> the cross-compiled qt3.dll, then I get the dreaded popup
"The<br>
>>> application failed to initialise itself correctly".<br>
>> <br>
>>> This is true both with a qt3.dll using the 'standard'
linker<br>
>>> options<br>
>>> <br>
>>> QMAKE_LFLAGS = -Wl,-enable-stdcall-fixup <br>
>>> -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc<br>
>>> <br>
>>> and when I add your script:<br>
>>> <br>
>>> QMAKE_LFLAGS = <br>
>>>
-Wl,--script,$(QTDIR)/mkspecs/cygwin-g++/i386pe.x-no-rdata <br>
>>> -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import <br>
>>> -Wl,-enable-runtime-pseudo-reloc<br>
> <br>
> <br>
> I see from your other reply that this would not have worked
anyway,<br>
> because I did not use the script when linking lyx.exe.<br>
></span><br>
I just tried to relink the cross compiled qt3dll and the qt tools<br>
(designer/assistant/linguist) with the above mentioned QMAKE_LFLAGS<br>
and got they running under windows without any problems. (The<br>
x-no-rdata file is very important)<br>
If you can build at least linguist or assistant and it will run under<br>
windows with the cross compiled qt3.dll and you got any seg faults,<br>
the qt dll will probably not the problem.<br>
<br>
<span style="white-space: pre;">>> It is interesting that the
problem is really the dll and not in<br>
>> the exe. Seems that there is a seg fault in the dll startup
code.<br>
>> Very difficult to catch, because it is not clear from which
part<br>
>> this comes. It may be a mingw provided static lib or the
mingw<br>
>> runtime library. (Do have used the mingw runtime dll from the<br>
>> cross compile package ?)<br>
> <br>
> <br>
> No, everything else is native Windows. Only lyx.exe and qt3.dll<br>
> were produced by cross compilation.<br>
> <br>
>> If you have time you can try to profile the application with<br>
>> depends <a class="moz-txt-link-freetext" href="http://www.dependencywalker.com/">http://www.dependencywalker.com/</a>. It may give some
hints<br>
>> about where the seg fault happens.<br>
<br>
> I currently think Windows is evil and would like to jump on its<br>
> grave :) Give me a day or so to gather some energy.<br>
></span><br>
Okay. Thanks for you contribution.<br>
Ralf<br>
<br>
-----BEGIN PGP SIGNATURE----- <br>
Version: GnuPG v1.4.1 (MingW32) <br>
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a> <br>
<br>
iD8DBQFCaSeHGkrI36lV8gURAozfAKCKu9SXHA0wj81Q3Elh9+xQW3N/PwCeNujB <br>
Hoy2RG1cVvToH1wC6uQMm8U= <br>
=MAkC <br>
-----END PGP SIGNATURE----- <br>
<br>
</body>
</html>