I did it, I did it! I'll rule you all out by: QRule!!!11!1

QRule: A tool for measuring screen items.

@Scott

Making a soft link from your SOBJS: to SDK:local/newlib/lib/ for libz.so should help (*). Nevertheless I think your build might fail not because of the missing shared object, but because of the "undefined reference to `Button::pressed()'" error...

(*)
cd SDK:local/newlib/lib
makelink libz.so.1 FROM SOBJS:libz.so.1 SOFT

@zzd10h

Mail sent! (if your mailbox explodes, I'll might upload it somewhere else and provide a download link... ).

Hmm, should I publish this somehow?



...still has problems (especially Canvas refreshes) , but it is usable. Nevertheless I don't think it's ready for OS4Depot...

...you mean a Masonifier?

@alfkil

Yes, I did include the files you mentioned. And, thanks, I found the "Qt::FramelessWindowHint" WindowFlag!

@spotUP

Thanks, that was the lines of code was looking for!

Hey, all you Qt specialists!

Is there any chance to tell Qt to use a borderless window?

@spotUP

Where and how did you set the StackCookie in Lifetime2? I couldn't find anything in the source code...

@Chris, Alfkil

Ok, the line

"ld: warning: libfreetype.so, needed by /qt/lib/libQtGui.so, not found (try using -rpath or -rpath-link) "

is what's left for now...

Indeed my SDK install was somewhat borked, I did a fresh and new install and a whole bunch of problems are gone. Nevertheless libiconv.so and linintl.so are not part of the standard linking from the SDK, so I had to do them manually. Maybe this should be part of the Qt installation routine (check and link, if it's not present).


There's another culprit - but I assume this has nothing to do with Qt: While my Sam440ep (slooooow) and my X1000 (faaaast) compile stuff like Analogclock or Calculator, my Pegasos II does this only sometimes - ca. 30% of the gmakes fail with a GrimReaper in a "cc1plus" process... ?!?

AFAIK I use the same SDK than you (53.20). Maybe my install is borked, but I don't think so, because all my other stuff (plain C, AmigaOS API and Reaction tools) compiles just nice and never has ever complained about something missing...maybe Guillaume has an idea or tip, what might be wrong...

Ah, thanks. Copying/linking a bunch of sobjs from "SOBJS:" to "SDK:local/newlib/lib/" helped and, indeed, I were able to compile something!

But I *still* get complaints about:


...despite the fact that they *are* there. Wrong version of libfreetype.so and libc.so or wrong combination of .a/.so-files, perhaps?

I tried to obey to Scott's resume and tried to build at least some simple demo apps from the Qt archive. But, sadly, I can't seem to get anything builded.

1. There's no "ppc-amigaos-c++"/"ppc-amigaos-gcc" in my SDK. SOLVED by making appropiate soft links from "gcc" and "c++".
2. One after another "ld ..." from gmake fails, because it can't find something, first: "-lfreetype". SOLVED by downloading and installing the "libfreetype.lha" from OS4Depot.
3. Can't find "-lfontconfig", "-liconv", ... Huh?

I have a fresh install of the latest OS SDK, enriched with "freetype" (see above) and the changed "_signals" stuff. What am I missing?

Thanks for your insights into the "automatic effect" topic! Still, I think, a well thought and implemented "embleming" might be useful. But this isn't something that will replace the typical amigan "animated and glowing" effect...

And, by the way, I'm looking forward to see your new, shiny, perfect and excellent artwork for the next OS release!

It's only a frontend for ffmpeg - we don't need Qt for this. You can already use ffmpegGUI for stuff like this.

I assume it's the same cause as with the non-working tool tests: Somehow the started processes can't re-send their output back to QDevelop. You can see this when it (former QDevelop version) i.e. checks for qmake: QDevelop seems to open some PIPEs for refetching output from the started processes (i.e. qmake "-v" outputs), but never receives something.

Whether this is a specific tool problem or a general Qt thing or not - maybe we need some more test cases for this...

@zzd10h
Quote:
It should be possible to fix this, I checked with SnoopDOS and looked into the code snippet that is checking the tools qmake, make, ctags and gdb. Indeed all are found by QDevelop (if you configure the right pathes, i.e. "sdk/c/make"), but the simple string comparison doesn't seem to work:

SnoopDOS (qmake):


From "toolscontrolimpl.cpp" (test for "qmake"):


I assume the "lu = testqmake->readAll();" doesn't work and "lu" is empty, so the string tests afterwards fail. Maybe it's easier to make a simple "it's there" test like the author did for the other tools (linguist, see some lines further in the code...).

Nice port, by the way!

@Chris
Quote:
Ha! Thanks, that was the cause! Indeed my Sam440ep and my Pegasos II somehow missed the libsqlite3.so from Update 2 (!!!) - now no crashes, nice!

I can still confirm with both qOrganizer compliles that they both crash badly when hitting the SQLite button with my Sam440ep and my Pegasos II but *not* with X1000! Crashlog seems to indicate a problem somewhere in the libqsqlite.so. Strange.

I commented something about themes here: http://www.amigans.net/modules/xforum ... t_id=80748#forumpost80748

AFAIK nobody is working on a native skin atm - but I may be wrong here...

Is that browser different to the DemoBrowser that came with the Qt package?

@chris

qOrganizer is really nice - maybe i'll try to use the MySQL feature in the next days. BTW: Hitting the SQLite button leads to a system lockup/crash (the MySQL button doesn't).