**** BEGIN LOGGING AT Thu May 01 02:59:56 2008 May 01 08:31:27 hi everybody May 01 08:39:26 in order to configure/install qt/embedded on my pc i have to run ./configure -embedded [arch]. could someone explain me what's the meaning of this option? May 01 08:39:26 i mean... it seems to be of no help for crosscompiling (i'll have to use -xplatform and set properly qws/directories for that), so what's the point in telling him the arch? May 01 08:44:03 cheshair: hi. it depends May 01 08:44:31 are you talking about qt-embedded / qtopia-core or qtopia? May 01 08:45:00 tsdogs: i see... more precisely i wonder: what's the point in using -embedded when you have -platform and -xplatform May 01 08:45:07 tsdogs: qt/embedded May 01 08:45:58 tsdogs: yesterday night (CET) rohanpm very kindly explained me i just need qt/embedded to build/run a small app on my arm device May 01 08:46:13 so i'm focusing on that May 01 08:46:22 hmm, I'm not sure but probably it's disabling some features ... May 01 08:46:36 yes, if that's what you want (full screen app) May 01 08:47:04 tsdogs: you mean -embedded disables/enables some features? May 01 08:47:18 you only need -xplatform whatever -arch arm May 01 08:48:32 hmm checking May 01 08:48:37 cheshair: -embedded means "build Qt embedded", -embedded arm I think is the same as -embedded -arch arm May 01 08:49:01 cheshair: and -arch arm tells Qt to use ARM-specific code where necessary May 01 08:49:46 I think so too :) May 01 08:50:15 rohanpm and tsdogs: is not enough saying -xplatform linux-arm-g++? (hi rohanpm! nice to see you again!) May 01 08:50:43 cheshair: nope. May 01 08:50:45 cheshair: not necessarily, because you could be building Qt/X11 for ARM May 01 08:52:56 well... but i'm working inside qtopia-core-opensource-src-4.3.3 directory, shouldn't it be enough to get i want qt/embedded? May 01 08:53:53 so i am supposed to use -embedded arm even if compiling on my x86 pc some tests apps to be run on my pc itself... May 01 08:54:19 cheshair: yes you are May 01 08:55:09 rohanpm: i see... may i use this option even with an open source license? May 01 08:55:42 cheshair: Sure May 01 08:55:57 qt/embedded is GPL May 01 08:55:58 (in the INSTALL file i am told i need proper license to use -embedded switch) ah ok i see May 01 08:56:08 very good May 01 08:57:37 so i may also want to compile -embedded generic and -xplatform linux-arm-g++: that way i'd only get some harder binaries, but no mistakes in theory May 01 08:58:08 "harder" binaries? May 01 08:58:35 bigger ones May 01 08:58:38 :-) May 01 08:58:49 cheshair: I think that would work, yes, but some classes would be slower or possibly broken May 01 08:59:12 (sorry i'm not mother tongue... in case it's not evident... :-D ) May 01 08:59:26 rohanpm: very very clear May 01 09:00:06 rohanpm: thank you very much, i just need some practicee now May 01 09:01:15 "./configure -embedded arm -qvfb -prefix /home/user/local" should be ok right? (no cross compiling, only pc to pc compilation to have some tests) May 01 09:03:40 cheshair: if your pc is arm (which I dubt) yes May 01 09:04:13 If you want an x86 version running inside qvfb then the arm is wrong May 01 09:04:22 tsdogs: so it turns out i didn't understand very well... May 01 09:04:29 cheshair: I think you might find that does attempt to cross compile... I think it may try to guess xplatform if you give an arch May 01 09:05:00 (10:53:52 AM) cheshair: so i am supposed to use -embedded arm even if compiling on my x86 pc some tests apps to be run on my pc itself... May 01 09:05:07 so this is wrong May 01 09:05:37 cheshair: ah... sorry, yes, you are supposed to use `-embedded' but not `-embedded arm' May 01 09:06:03 i see, ok May 01 09:06:11 now i see May 01 09:06:51 in practice, to make it short, i will always want to use -embedded arm along with -xplatform linux-arm-g++ May 01 09:07:44 if building for the target platform yes (which means cross-compiling) May 01 09:07:56 tsdogs: great May 01 09:09:10 cheshair: if you look at the mkspecs/qws/linux-g++-arm you'll see what options will be enabled with the xplatform May 01 09:10:13 tsdogs: very nice! i consider that the very next step i'll take as soon as building some x86 test apps will work May 01 09:10:35 tsdogs: and i'll be back to bother you again, that's clear... :-D May 01 09:10:54 cheshair: I usually have 2 shadow builds, 1 with x86 and 1 for the target May 01 09:11:19 so you only need to run the corret qmake to have your app builded wither for x86 qvfb or arm May 01 09:11:22 cheshair: if you have questions and no-one answers, you can ask in #qt . After all, this is really about Qt, not Qtopia May 01 09:11:33 :) May 01 09:12:17 rohanpm: i see, i'll definitely join taht channel too (sorry if been a bit ot here) May 01 09:14:32 tsdogs: i'll have two shadow builds too then! which conf file am i supposed to manage to get that? May 01 09:15:47 cheshair: simply create a ../qtx86 and a ../qtarm folders then cd ../qtx86 and run ../qt_embedded/configure -embedded x86 -qvfb ... (and same for the other) May 01 09:16:02 then you simply run make in one folder May 01 09:16:53 tsdogs: with different -prefix i guess? or not? May 01 09:16:59 once they both built you use the qmake aganst your app .pro file and run make clean; make (when changing target) May 01 09:17:34 well it actually does not matter, as you won't install the arm on your PC but on the target May 01 09:17:42 device May 01 09:17:58 tsdogs: i see, sure May 01 09:18:43 i'm taking notes of all that you say: it will be so useful in the next days May 01 09:20:04 rohanpm: as you told me yesterday, i'll want to use qtopia instead of qt/embedded when developing some bigger/more complete project for my arm device, won't i? May 01 09:20:29 cheshair: maybe, maybe not. I don't know what you really want to do :-) May 01 09:20:55 If you actually want to make a functional phone, Qtopia is one of the fastest ways to get there May 01 09:21:19 If you want anything less than that then Qtopia probably has a lot of stuff you don't need May 01 09:21:24 rohanpm: what do i want to do? just some fear to nokia... :-D May 01 09:22:33 rohanpm: "to make a functional phone" or also, let me say, a functional gps, or some kind of portable device like that? it depends? May 01 09:23:20 Well, Qtopia 4.3 doesn't have anything for GPS May 01 09:24:29 Look at the Functional Descriptions page in the Qtopia docs for a broad overview of what there is May 01 09:24:33 roadmap has a gpsconsole (which uses gpsd), but there are many others May 01 09:25:56 http://84.18.144.44/tsdogs/roadmap/qpe4_roadgps1.png :) May 01 09:26:01 gg, cya May 01 09:26:39 rohanpm: i see, the point is i'm quite new to qt and i find some terms development: qt/embedded is aka qtopia-core, and similars so i'm still making some mistakes May 01 09:27:02 cheshair: when you're new, it's better to stick to the simpler stuff first, and Qt is a lot simpler than Qtopia May 01 09:27:56 rohanpm: sure, so i'll hang around qt for a while, that's for sure (when you say qt, you also mean qt/embedded?) May 01 09:28:05 Yes May 01 09:28:16 rohanpm: sure May 01 09:28:33 tsdogs: thanks, cya soon! May 01 11:58:56 hi again guys, i succesfully managed to configure/compile qt/embedded on my pc May 01 11:59:19 after a few tries anyway i think i corrupted my install May 01 11:59:44 in fact most of example apps now give me this message: ./puzzle/puzzle: symbol lookup error: ./puzzle/puzzle: undefined symbol: _ZN7QWidget8qwsEventEP8QWSEvent May 01 12:00:00 any hints? May 01 12:01:43 you have built against a qt-embedded, but tries to run it against a plain qt ? May 01 12:02:04 these are the steps i took: configured/build qt/embedded, many example apps did work by means of debian qvfb. they did not work properly as regard to mouse control so i decided to download and build qt (and qvfb alongside) from scratch May 01 12:03:09 pusling: then i tried removing my qt installation but i guess the toy had been broken... May 01 12:03:42 pusling: what does it mean "to run it against"? May 01 12:03:57 the system libs you try to use ... May 01 12:04:05 hmmm May 01 12:04:24 so probably qt installation overwrote qt/embedded one? May 01 12:04:47 or the linker just prefers your qt installation over the qt/embededd one. May 01 12:04:52 i configured both of them with -prefix /home/user/local May 01 12:05:22 then it might have overwritten th eexisting one. May 01 12:05:29 poiled linker! :-) May 01 12:05:30 the other one. May 01 12:05:33 spoiled linker! :-) May 01 12:06:18 what can i do? a plain clean&recompile? (for the joy of my dual core??) May 01 12:07:06 btw... i guess i'm ot here... May 01 13:22:01 morning **** ENDING LOGGING AT Fri May 02 02:59:57 2008