Issues with build in Carbide C++ 2.0

Question

I'm building my application and when I try to run it on the emulator, I get this error.

Creation Time   Description Resource Path Location Type
1254339868582   BLDMAKE ERROR: Directory "\S60\devices\Nokia_N97_SDK_v1.0\epoc32\" does not exist ZeFirst  Unknown C/C++ Problem

The folder does exist and does have the necessary rights.

The console has the following set of warning messages

warning: "C:\S60\devices\Nokia_N97_SDK_v1.0\epoc32\tools\GCCEV6.bsf" Invalid BSF specification - customization restricted to ARMV5, ABIv2 and valid BSF platforms
warning: "C:\S60\devices\Nokia_N97_SDK_v1.0\epoc32\tools\GCCEV6T2.bsf" Invalid BSF specification - customization restricted to ARMV5, ABIv2 and valid BSF platforms
warning: "C:\S60\devices\Nokia_N97_SDK_v1.0\epoc32\tools\GCCEV7A.bsf" Invalid BSF specification - customization restricted to ARMV5, ABIv2 and valid BSF platforms

Answer 1

What other development tools do you have installed on your computer?

Is there a chance your path environment variable is in the wrong order and you're not using the correct version of the compiler, for example?

Feel free to post your path, it can only provide more information.

Answer 2

I'm not sure if this will work, but try this:

Subst a drive to C:\S60\devices\Nokia_N97_SDK_v1.0\

Start, Run...
subst x: C:\S60\devices\Nokia_N97_SDK_v1.0\

Then in carbide, set your SDK to point to this subst location.

Window, Preferences, Carbide C++, SDK .. 
Change the paths to use "x:\"  rather than C:\...

Delete any imported projects in Carbide

Select project, right-click, delete.
(Do NOT click the tick box that is displayed).

Re-import your project

File, Import, x:\.....\bld.inf

Answer 3

I have faced a similar problem once.

If you have been able to build and launch the eumlator on earlier occasions, then the only solution that worked for me was to re-install the SDK.

Answer 4

Techeretic,

make sure that your workspace is located in the same driver partition (C:) of your Symbian SDK installation. If don't try changing it.

Sometimes I solved that problem by changing .pkg file's content to use a relative path. For example:

;Files to install
;You should change the source paths to match that of your environment
;<source> <destination>
"$(EPOCROOT)Epoc32\release\$(PLATFORM)\$(TARGET)\MyApp.exe"  -"!:\sys\bin\MyApp.exe"
"$(EPOCROOT)Epoc32\data\z\resource\apps\MyApp.r01"   -"!:\resource\apps\MyApp.r01"
"$(EPOCROOT)Epoc32\data\z\private\10003a3f\apps\MyApp_reg.r01"  -"!:\private\10003a3f\import\apps\MyApp_reg.r01"
"$(EPOCROOT)epoc32\data\z\resource\apps\MyApp_aif.mif" -"!:\resource\apps\MyApp_aif.mif"
"$(EPOCROOT)epoc32\data\z\resource\apps\MyApp.mbm" -"!:\resource\apps\MyApp.mbm"

Hope it helps.