Symbian C++ Development Under Mac OS X

Question

I've been developing for Symbian S60 3rd Edition since last year using Carbide.c++ under Windows. THe problem is that I moved to Mac OS X this year(bought a Macbook Pro) and when I was going to download Carbide.c++, I saw that it's Windows-only, because of the Requirements:

Microsoft Windows XP Professional Service Pack 2 or Microsoft Windows Vista (32-bit).
1 GB of RAM.
700 MB of free disk space for Carbide.c++.
1.8-GHz processor; x86 architecture.
ActiveState ActivePerl-5.6.1.635.
At least one Symbian OS platform SDK.
1,024 x 768-pixel screen capable of displaying 16-bit colour.

But there are any alternatives for Mac OS X?

Answer 1

As of now, Mac is not officially supported if you want to develop apps for Symbian (either using QT or without QT). The problem is that all the tools needed to create the final binary run only on Windows (abld).

This page on Forum Nokia makes it pretty clear:

Qt for Symbian development requirements In order to develop Qt applications for Symbian devices you'll need the following setup:

1. Development PC. You need a Windows PC. At present, Symbian development is best supported on Windows XP and Windows Vista.

You can use remote compiler from mac via qt. http://labs.qt.nokia.com/2011/01/20/qt-sdk-1-1-technology-preview-released/

Answer 2

running Symbian emulator in VMWare never worked 100% for me... If the Qt is enough for you you can use QtCreator - it is available also for MAC OS.

BR STeN

Answer 3

You can download Qt for MacOs from http://qt.nokia.com/downloads/sdk-mac-os-cpp. Nokia is strongly urging (standardizing on) Qt for new development. Stay tuned for the Nokia Investor Strategy and Financial Briefing on Feb. 11.

Answer 4

But there are any alternatives for Mac OS X?

One alternative is to use QT Creator on Mac to develop your Symbian app. You can develop and debug it for SImulator versions only on Mac, so once you're done developing/testing it on Mac, you can transfer your project/synch with your s/w versioning tool on Windows for actual on-target debugging.