The (bad) assumption is that if you are using an EMX build, you don't have
the toolkit installed.
for VACPP we have to use the toolkit RC, for EMX you have to use the OS/2
RC.
ugly.
Mike
Henry Sobotka wrote:
> Simply a note that may spare someone else needless hairpulling.
>
> Yesterday I finally regained a debug emx build by configuring with
> --disable-debug --enable-optimize and then manually replacing -O with
> -g; this works around the longstanding nglayout.dll linkage failure. But
> when trying to launch the beast, no splashscreen would appear and the
> immediate crash would corrupt the entire desktop, e.g. windows would
> remain painted on the screen after an app had closed, blank windowlist
> etc., requiring a reboot. Even idebug crashed trying to load
> mozilla.exe. After countless reboots and poring over diffs, this
> afternoon I noticed that toolkit/bin/rc.exe was being used instead of
> os2/rc.exe to compile and bind the icon and splashscreen bitmap in
> xpfe/bootstrap. I disabled it, forcing os2/rc.exe to run. It immediately
> failed, complaining it couldn't find mozos2.ico and splashos2.bmp.
> Copying them into the objdir fixed that and the result was a healthy
> mozilla.exe and normal desktop. Using the toolkit rc with the resources
> in the objdir would probably have the same effect as it works fine for
> wdgtres.dll (where we do copy the resource files to the objdir); I just
> haven't tried it yet.
>
> h~
