Beta testing

@spotUP

Did you try Alfkil's previous suggestion? http://www.amigans.net/modules/xforum ... t_id=80278#forumpost80278

could someone upload those two files somewhere?
i can't find them in the repo...

these files:
.qmake.cache and .qmake.var

the only qt related path i have is:

Bob:Qt-4.7/Qt-4.7/bin

and it looks correct to me.
.. uhm.. i seem to have forgotten how to set paths, how do i do?

alfkil: it's this one:
http://Qt-Apps.org/content/show.php/Scythia?content=61326

I, too, had problem to build my first Qt program, I had to put "moc" and "uic" in SDK:local/newlib/bin
(or something like that, I'm not in front of my Amiga for the moment)

@alfkil

I downloaded the QT4.7 from OS4 depot an decompressed it on my micro A1. However, every time I try to install it using the install icon provided, the installer runs for about 10 minutes or so (800MHz G3 cpu) and then I get a series of DSI errors. I have tried repeatedly decompressing the QT file I downloaded and starting to install again, but always the same results. Note - the decompress shows no errors.

Any ideas?

Thanks!

@spotUP

The files are right here:

http://sourceforge.net/p/qtamigaosnative/code/131/tree/trunk/

About the path that I mentioned: I am pretty sure, that if you look in the makefile (not the .pro file), you will see some variable in that line, ie.

(cd $SOMEVAR/src/tools/moc && gmake)

By the way, this only happens because gmake cannot find moc, and hence tries to build it. The answer is the same as to zzd10h, namely to add something like this to your user-startup:

setenv PATH $PATH:/qt/bin

NOTE: This line should come after any AmiCygnix install proceedure!

@alfkil

Okay, got it installed. It seems that if I try to install it FROM any JXFS\4 partition, I get a DSI error just before the install completes (around 90%). I copied everything over to an SFS\02 partition and installed from there and it installed just fine! How strange is that?
Anyway, tried the demos - great work! I look forward to trying to compile and build some QT programs.


Thanks!

Scott

alfkil ok, i copied those two files and added setenv PATH $PATH:/qt/bin to my user-startup after the amicygnix stuff.
things goes a little bit better.
it starts to compile for a while and then stops with:


(cd /src/tools/moc && /SDK/C/gmake)
T:gmake.sh.223.SBMFAX[1]: cd: /src/tools/moc - Device not configured
gmake: *** [moc] Error 1
7.Bob:Coding/Projects/qtstuff/VizMol/VizMol>

i logged it with snoopy and found this line:
00343 : sh : FAIL = Lock("src:tools/moc",SHARED) [102uS]

@Alfkil :
In the readme, you write

"QtCore: - QProcess does not implement every feature, but should work for
most situations"

Is your implementation works to start asynchronously a command with arguments ?

Thank you

trying out another project now, and i stumbled into this:

uic searchdlg.ui -o ui_searchdlg.h
uic: File generated with too old version of Qt Designettr (3.3)
File 'searchdlg.ui' is not valid

i googled it it and i got the answer, open it in qtdesigner and resave it.
fine.
i tried to do that. but qtdesigner doesn't redraw it's screens, i get a lot of grey areas. this happens in some other qt apps as well. maybe some setting?
this default value should proably be changed if that is the case?

I changed the painting engine to non-native. I still get grey areas and the mouse is offsetted. I tried to open the file anyway and i got this message in a shell window:

QProcess: Destroyed while process is still running.

So something seems off here.

Btw, these tests were done with compositing off. Will try with compositing enabled.
Every window that comes knfront of a qt app leaves grey areas as if the qt app fails to redraw it's content.

@spotUP

moc issue: This is still the same thing as before, it tries to build moc, but can't, because some path variable is missing. This could be because of some issue with the timestamp of the moc executable. Try resetting the date of the moc exe to the current date, and see if that helps.

EDIT: If that strategy fails, try going into the makefile and delete the line that says

(cd $(QTDIR)/src/tools/moc && $(MAKE))


Grey area issue: I canged all windows to use simple refresh, which is probably why you get the grey areas when Qt windows are at the back. This could be graphics card related. I have only tested on my X1000, and here the problem doesn't appear. I will try and test on my sam to see, if I get the same issue, and if so, I will probably change back to SMARTREFRESH.

@zzd10h

qtdemo uses QProcess to start programs asynchronously, so the answer is yes :)

I cannot remember exactly what it is, that it cannot do, but AFAIR it has got to do with piping input and output streams.

Quote:

Which app produced this warning, and what did you do in order for it to happen?

Mouse offset in gl mode: Yeah, something is wrong, I have to look into it.

With compositing enabled the grey area problem goes away.

The app that makes designer go nuts is qpaddy. Open searchdlg.ui by chosing open in the file menu.

I just tried again with native paint engine and i don't get the error it just stalls.

my moc executable:
moc 2210244 ----rwed 26-Jun-13 16:56:11
looks correct i guess?

edit: testing with current date now.. let's see...

edit: nope: same thing when compiling scythia:

4.Bob:Coding/Projects/qtstuff/scythia> gmake
(cd /src/tools/moc && /SDK/C/gmake)
T:gmake.sh.521.TLOVXF[1]: cd: /src/tools/moc - Device not configured
gmake: *** [moc] Error 1
4.Bob:Coding/Projects/qtstuff/scythia>

when deleting that line in the makefile i get:

T:gmake.sh.521.RTOVXF[1]: moc: cannot execute - Permission denied
NIL::1: sh stoppat, felkod 126

If i try to execute moc n shell by typing moc i get:
Moc: file is not executeable.
I just did protect qt:bin/moc +e let's see what happens.