Hi, I use Carbide c++ v 2.0 OEM edition.
I have RVCT 2.2. installed. I can build my project OK on command line with "abld build armv5 udeb/urel".
When I import my project in Carbide, emulator build works, but armv5 build ("Build configuration->Phone Release (armv5)") does not. My project consists of multiple mmp files.
Carbide seems to compile some of the files, or at least it does create some ".d" files:
Created \S60\devices\S60_5th_Edition_SDK_v0.9\EPOC32\BUILD\myproject\group\mmpname\ARMV5\urel\file.d "
But then it stops with an error:
" C:\myproject\group\someotherfile.d does not exist "
I have no idea what Carbide is doing here.. What are these .d files anyway? Why Carbide creates them, and does the command line build chain create them?
How can I make Carbide to build my project?
Please ask if you need any clarifications...
My ultimate goal is to create a device debug build using armv5 udeb target and debug that in Carbide. If I do a armv5 udeb build on command line and then start debugging in Carbide, the break points are all messed up. I.e. Carbide does not stop at the right locations in code. So I hope that doing the build in Carbide vs. on command line would take this problem away.