Re: building kdenox in trunk
Adam Doppelt <[email protected]>
| Newsgroups | gmane.comp.kde.devel.konq-e |
|---|---|
| Message-ID | <[email protected]> |
When I try to build against qte2 using a slightly tweaked version of the qtopia configuration, I get: ksock.cpp:105: error: syntax error before `::' token ksock.cpp:109: error: `sin' was not declared in this scope ksock.cpp:111: error: `sin' was not declared in this scope ksock.cpp:111: error: ISO C++ forbids declaration of `memset' with no type ksock.cpp:111: error: `int memset' redeclared as different kind of symbol ... Adam Eva Brucherseifer wrote: > Am Mittwoch, 5. Juli 2006 21:52 schrieb Adam Doppelt: > >> Thanks for the suggestion. I am now trying to compile against qte3 using >> your suggested configuration. Unfortunately, the kdenox configure fails >> during qt detection with the following: >> >> /tmp/ccgVdTEJ.o:(.gnu.linkonce.r._ZTI6QGList+0x8): undefined reference >> to `typeinfo for QPtrCollection' >> > > You need threading and RTTI enabled in Qt. > > >> Earlier, I was able to get the Jan 2006 snapshot working against qt2, >> but it crashed on my test page. I figured I'd try trunk and see if it >> worked better. >> >> I don't have a preference for qte2 vs. qte3. My primary interest is the >> browser itself. Any other suggestions? >> > > Ah, if you want qte2, have a look into the kdenox-qtopia.kdevelop file, it > works with Qtopia 2.1. I am not sure I commited a pure qte2 version, but it > is not much different. > > With Qte2 you can use the ROAD GUI (--with-gui=road) which is what we've > worked on the last months. It is certainly more polished then the other GUIs > and it has some additional (tested) features. > > Cheers, > eva > _______________________________________________ konq-e mailing list [email protected] https://mail.kde.org/mailman/listinfo/konq-e