On Thu, Apr 13, 2006 at 02:27:50PM +0200, Abdelrazak Younes wrote:
> Enrico Forestieri a écrit :

> >The qt3-win32.patch also contains my patches to Qt aimed at a
> >cygwin executable, but they do not harm a native build.
> >Although the patch may seem big, it does nothing more of what
> >you find described in qt3_patch_description.txt.
> 
> My question is: are those change needed for a native build also? Except 
> for the -mno-cygwin option, I guess not... are they?
> I know I am demanding too much her but you could try to push your patch 
> to the qt3win people. They seem pretty open minded.

No, the native build is only supported for mingw. I simply had handy
the overall patch and not separated it because it is ok for either
type of builds.

I have separated the patch needed for a cygwin build only and you can
find it here http://wiki.lyx.org/LyX/LyXOnCygwin

Cygwin/Win is a (almost) supported target (you can specify it by
-target cygwin-g++-win32) in Qt. I say almost because it seems an
unfinished work, and at first I had to massage it because of path
style problems. In a word, it compiled but was unusable.

Notice that I am talking about the cygwin-g++-win32 target, as there
is also a fully functional cygwin-g++ target but it uses X11.

The cygwin-g++-win32 target uses code from both the win32-g++
(native Windows) and the cygwin-g++ (Cygwin/X11) targets, and
allows building a Cygwin Qt without X11.

Apart the path-style problems, I recently merged the code dealing
with sockets for a posix target to cygwin-g++-win32, thus allowing
unixsockets in Cygwin Qt/Win (they are already functional for
Cygwin Qt/X11).

About pushing a change to people not interested in it... Uhm...
I have already to fight here to have accepted a change for cygwin
and I fear that I have neither time nor energy to open another
war front...

-- 
Enrico

Reply via email to