mbm resource target directory -- Carbide.vs or RetroBlaster problem?

[ET3D]

I imported the 2D Game Animation example, RetroBlaster. It crashed in the emulator, and it turned out that it couldn't find the file 'system\apps\RetroBlaster\retroblaster.mbm'.

Checking the build output, it seems that the file is being written to Epoc32\release\wins\udeb\ and not Epoc32\Release\wins\udeb\z\system\apps\RetroBlaster as the app expects it.

I don't know much about Series 60 programming yet, and can't tell whether the build is wrong or the application is looking at the wrong place, but it'd be nice to know the answer, and even nicer to get things working well.

(BTW, copying the file to where the application expects it made it run fine.)

[mitts]

Hi,

Mostly you would expect the mbm to end up in the application directory as you say this seems like a potential problem.
What SDK was this? Does the "START BITMAP" section in the .mmp file contain a "TARGETPATH" statement? If it does, what is it? If it is not there, you can try to add something like:

TARGETPATH \system\apps\<your_app_dir>

[ET3D]

Thanks for the response. IIRC there was no "TARGETPATH". I don't have time to check this now. Will check in a couple of days and let you know. The sample is not part of the SDK but is downloaded separately. What's the best way to provide feedback to Nokia about a sample?

[mitts]

Hi,

No need to report it, you actually found a minor bug in Carbide. If you omit TARGETPATH the mbm should by default be built into the application directory, so the sample itself is OK. Thanks for pointing it out.

[ET3D]

Okay, good to know. I'll be looking for an update of Carbide.vs, then, and meanwhile I'll add a TARGETPATH to the relevant section.