[KarstenBln]

Hello,

I had many problems getting Carbide.C++ Express up and running. There are some very important things that are unfortunately not listed in the release documentation or in the installation guides.
Some of them are mentioned in the Screencast. I watched it but I didn't know that there was a soundtrack. So I wondered why it took so long to start up and it was rather boring.
And there is another thread by michelasso in this forum that I have found when I had already recognised most of the traps: http://discussion.forum.nokia.com/fo...ad.php?t=87390 "Getting started without getting (too much) frustrated". Its item 1), no spaces in the paths, is mentioned in the Installation doku. Its item 2), SDK and workspace on the same drive, is not mentioned but important.

I have to add an item 2a):
It is necessary that the root directory is writeable! My first attempts failed because I have used a network drive as workspace which contradicts 2) and also 2a) because its root is write protected. I noticed an access denied message in the console window. Then I moved the workspace to another drive not knowing about 2). I found out that the drive letters are missing in the paths of the generated pkg file. So I moved to C: and again there was the problem it's write protected. I'm using a company's workstation as PC, so my access is restricted.

There is another issue with the installation order. The installation doku says, install the SDKs then install perl. The SDK release doku says, perl must be installed before you install the SDK.
Anyway, as discussed in other threads today, the order of SDK and Carbide should not matter. I assume that a JRE is installed anyway. Some people have reported problems with JAVA higher than 1.4.2_...

There was another issue today when using a non english MS Windows version. It's that the SDKs store common files in a folder "C:\<program files>\common files\symbian". It may be named different but Carbide always looks for a folder exactly named this way. More:
http://developer.uiq.com/forum/thread.jspa?threadID=690

Two things that do not concern installation but usage:
Exit the emulator before a new build is done (mentioned in the screencast).
Michelasso (4) and others had problems when they changed the loc file:
Delete the .rsc file in ...\epoc32\release\WINSCW\UDEB\Z\SYSTEM\APPS\<project> and then rebuild.

Regards,
Karsten