Re: [Tora-develop] build procedure for tora-qt4 on windows

[Mike J. <mrj...@mi...>]

On Thu, 2008-01-03 at 20:30 +0100, Petr Vanek wrote:
> well, I'm able to drop cmake support in one minute when I'll be sure the 
> autotools can do its job in Windows ;). Is there any howto? I know you 
> said something about Cygwin, but I'd like to use real Win Qt4 libs.

real win libs? it uses the real libraries. depends how you build qt.

actually, my memory is a little fuzzy here, but i think they ship with
mingw .a files in addition to the .dlls now days. doesn't matter though,
since you have to rebuild to get the sql plugins anyhow...

well, i never got around to making a howto, but if you install cygwin
(with autotools, gcc, and other bits) then it should work with
just ./configure, blah... or at least i'll be able to help you from
there.

the only reason i was using cygwin is msys was missing some stuff i
wanted. i think it was some windows headers missing that cygwin had. i
did end up removing the CRegistry stuff so it might even work using msys
now. anyway, it should die in the configure phase if there's something
important missing (be sure to run autogen first).

> yep, RPMs here. It prints some warning about libc5 due the Oracle client 
> here - but it works.

i'm not sure what you were trying to do, but linking against libclntsh
does everything you need. maybe it's as simple as that?

> maybe. But the code is hard to split now. Be relaxed, no big changes to 
> come ;)

sweet. i'm trying to port everything that uses q3listview. since they
all depend on each other and what not, it's very hard to port one
without porting them all at once. yay.

just about got it now. i've gotta go soon, but maybe in a day or two
i'll have time to iron out the rest of the bugs...

> I tried it only for finding the easiest solution. I don't plan to use it 
>   now. It takes hours to setup the environment and hours to compile (CPU 
> over 70 Celsius degrees)

yeah i set mine to compile and left. when i got back it was shutting
down. it thought it had kernel panicked at first. lol. been a long time
since i've seen one of those.