StormC 4 gcc, mui question.

[Olle]

Hello folks..

I have mostly been idle and mostly read others posts, but now i finally managed to post again, i've been busy with alot of work.

I started programming some C++ on my amiga again, and instantly turned into problems when using the GCC compiler option in StormC 4

Firstly i had to remake the protos, but that was the easy part, now it says that there is something wrong with the mui-macros. Anyone had this problem?

When using the StormC 3 compiler option, it all works. But i want the GCC option.  :-)

Any help appreciated. I know that perhaps the talented people i've seen around has the answers, like Odin, DaveP, Tickly or someone else..    :-D

Help pleaaaasee... .

[Cluke]

Sorry I'm not answering your question, but I wondered if you could tell me what "remaking the protos" involved.
I installed StormC 4 and was very disappointed that it did not seem to work out of the box in GCC mode. The ease of set up was one of the reasons I got it and was well annoyed to end up getting the same errors as I was getting as any other GCC installation I had tried.

[Olle]

Hi!..   Yes i found out how to solve my problem, i used muiplusplus.lha from aminet, and that works like a charm. And i also read on the yahoo MUI mailinglist about what caused the macro errors. So my question is now obsolete.

However i have to say that i have no big problems in using the GCC compiler of stormc4 as i have with the "normal" gcc compiler as i suck in using makefiles and such.

What i meant with remaking the protos was, that i used FD2Pragma with a special option (54 i think), but that is perfectly explained in the FD2Pragma documentation in StormC4

I compiled DCLIB without any problems in StormC4, but the problem came when linking, bcoz i didn't have the threads.lib, and the libxml2.libs, and then i haven't had time to compile those for StormC yet.

However i recently ported my Postscript parser to StormC, and it was no problems at all, except when drawing beziér curves on the amiga, i had to make my own polybeziér function, but then it worked fine. (ported from win32)

IMHO i must say that the debugger of StormC4 really deserves credits, atleast compared to Visual Studio 6. I have debugged some major faults in our "Public win32 software" that was accepted with Visual Studio, but found memory leaks under the StormC debugger.    :-D

I just think it's too bad this Bernie thingy, that Haage & Partner screwed up, because the StormC compiler is actually very good. One just needs to give it some time, and practice methinks.

Dunno if this helped you in any way, but....

Perhaps i can throw in another question here aswell, if i want to build a list of pens with dedicated
RGB values, and then use this with MUI, can someone direct me to a simple example?

I have tried to use the original MUI demos, but there's really not that kind of example, they call the color-palette requester and then creates the pen automagically..  

\Thanks

[Cluke]

Yes, that helped I think. I'll have a look at FD2Pragma then..