You Are Here:

Community: Blogs

Lucian Tomuta's Forum Nokia Blog

S60 SDK and tools on Windows Vista - a success story

ltomuta | 15 June, 2008 20:30

The following is a copy of a Discussion Board post from a thread discussing - again - the level of support of the S60 tools and SDK for the Windows Vista, or more likely the lack there of. 


This thread finally made me curious enough to try installing the SDK on Windows Vista. Here are my results:

OS: Vista Home Premium + SP1
SDK: S60 3rd FP1
IDE: Carbide.C++ 1.3 Pro (eval)
Tools: Active Perl 5.6.1 build 635, GCCE 2005-q1c

1) Install Carbide
setup.exe -> next -> ... the usual ... -> finish.

To be noted that the installation is done in C:\Apps rather than the protect c:\Program Files\...

2) From the html page displayed by Carbide at the end of the install download Active Perl

Since Perl was already reported to be tricky (and since it will try to touch at least the %PATH% env. variable) I've made sure to run the setup.exe in Administrator mode. All went just fine.

3) SDK download

Again, the SDK installs files under c:\Program Files\... so Admin mode is preferable. All went swell until I was prompted to ...

4) Install GCCE

Since I was not sure if the installation is to be run in Admin mode I've decided not to perform the install at that time. Once I've answered NO to the prompt the SDK install finalized with OK status.

Now, the GCCE installer can be found under %EPOCROOT%Epoc32\tools\distrib so the next step is to start the install from there with Admin rights. And all goes well.

5) Quick inspection of the tools (like in How do I start programming for Symbian OS?) and environment settings. Since all seems fine is time for ...
 
6) Carbide.c++ test

The usual restart after detecting the SDKs. Then example project import and build for emulator. All seems ok except for some warnings about non-existing pipe, I guess they are safe to ignore.

Unfortunately here I pause with the good news since I find that the emulator fails to start somewhere in the area of font loading.

Resuming the good news flow the GCCE build worked just fine and I ended up having a signed SIS file.

My conclusions:

- Installing the environment on Vista is not impossible and, at least when it comes to the actual install sequences it does not require any extra effort, maybe just a bit of patience and environment awareness
- Since there are some known problems with the emulator and certain hardware drivers I cannot blame Vista for the emulator problems. Not yet anyway :)
- Despite of the relative success of the test, and even after I'll solve the emulator issue, I still do not see Vista as the OS of choice for Symbian development. If anything I'll try to get back to XP which is more stable, less bloated and more importantly fully supported by the tools.

Update:

Ok, solved the emulator problem too. It was the much debated "FAULT: Exception 0x10000000" problem, with the fix being a change on Vista's Data Execution Protection (DEP) settings.

So, now I have a fully working environment. The next task will be to delete it, but that can wait until tomorrow. ;)

 

 


 

Well, I hope someone will find this useful. 

 

RSSComments

When?

kiran10182 | 15/06/2008, 21:23

kiran10182

Lucian, as you may see that Windows Vista comes everywhere nowadays. Can it be possible that we have everything "one shot setup" with SDK or Carbide.c++ without doing any such tweaks?

Soon

ltomuta | 15/06/2008, 22:09

ltomuta

Support for Vista will be provided in the [near] future but one should not expect that old SDKs releases (and one should count the SDK I used as old) will be touched in order to add Vista support.

So I am afraid one cannot completely ignore the need for tweaks. However, as this post demonstrates (I hope) there is really no need for major hacks, just a bit of understanding of the host OS and its limitations (some call them improvements) ;)

Re: S60 SDK and tools on Windows Vista - a success story

skumar_rao | 16/06/2008, 04:40

Hopping update will come before the market is flooded with Windows 7.

Re: S60 SDK and tools on Windows Vista - a success story

ltomuta | 16/06/2008, 07:22

ltomuta

I suggest that you make a VMware (or the likes) image of your current WinXP installation just in case.

Btw, will Windows 7 have more features than Windows 3.1.1 but less than Windows 95? ;)

S60 SDK & tools on Windows Vista- Having Problems

avijit_roy82 | 16/06/2008, 16:06

Where can I find GCCE? Is it necessary to install it for S60?

Re: S60 SDK and tools on Windows Vista - a success story

ltomuta | 16/06/2008, 16:42

ltomuta

You need a dedicated compiler when building for the actual device. Since Symbian OS 9.x the supported compilers are RVCT and GCCE, the later shipped with the SDK (see %EPOCROOT%Epoc32\tools\distrib\arm-none-symbianelf-2005-q1c.exe).

So the answer is Yes, you need to install this compiler unless you have the RVCT.

More information in SDK's release notes.

Finally made it!!!

kiran10182 | 18/06/2008, 21:33

kiran10182

Finally i made it worked for GCCE UREL by getting rid of "BAREWORD ....." error.
Check it under "Latest Updates" on
http://wiki.forum.nokia.com/index.php/Moving_to_Windows_Vista

Kiran.

S60 2nd Edition FP3

udayapk | 04/07/2008, 04:17

Hello Lucian Tomuta,

I am trying install S60 2nd Edition FP3 in Windows Vista(tm) business OS.

I have installed Active Perl 5.6.1 build 638 using the Installer bat file ( NOT msiexec), then j2re-1_4_2_17-windows-i586-p and then SDK.(run as admin)

For IDE installed trial version of CodeWarrior personal edition.(run as admin).

When I try to compile the hello world program, I get "Failed to run makmake. System error: System cann't find the specified file". "makmake file failed to run".
This message comes from SymbianMMSImporter DLL of codewarrior.

Verified that EPOC32\Tools is in the path set in system variables.

Appreciate any pointers in this direction?

thank you.

-Uday.

Re: S60 SDK and tools on Windows Vista - a success story

ltomuta | 04/07/2008, 16:33

ltomuta

Why CodeWarrior? Where can one still find it for download?

I have not tried such thing, in fact I don't know if I can still find it somewhere for a test round, but one thing that I would do it to make sure that the application does not get installed in its default location, in Program Files. Instead send the installation to e.g. C:\Apps\CodeWarrior

I do not remember which installer version I used for Active Perl but probably the MSI version. But I guess if you can run perl at the command prompt, (e.g. call "perl -v") all is fine.

CodeWarrior is however an old product, check the release notes and see what are its requirements regarding the Active Perl version. If possible stick to that version so that you avoid further problems.

I think that the makmake type of problems reported by CodeWarrior were indeed related to Perl but you can easily verify this by doing some searches on the Discussion Boards.

Hope this helps!

Re: S60 SDK and tools on Windows Vista - a success story

ltomuta | 04/07/2008, 16:36

ltomuta

Also, try running the command line tools, do they work? It could also help if you would have a look at the "virtual store" concept introduced by Vista, I've found it to be interfering with my attempts to customize the SDK.

S60 SDK and tools on Windows Vista - a success story

udayapk | 05/07/2008, 17:35

Hello Lucian Tomuta,

Thank you for your response. I could successfully install and compile S60 2nd Edition FP3 on Windows Vista with CW 3.1 IDE.

The info in the below Wiki was also useful.

http://wiki.forum.nokia.com/index.php/Moving_to_Windows_Vista

Cheers,
Uday.

Re: S60 SDK and tools on Windows Vista - a success story

Baba_jani | 23/09/2008, 03:54

Hallo guys Can you tell me what is perl
his daffination and how can Get it ?
please help I'm gettig crazy with search enginssss

Re: S60 SDK and tools on Windows Vista - a success story

ltomuta | 23/09/2008, 08:15

ltomuta

You need ActivePerl by ActiveState, but to know which version of it (the latest version will not work) you need to read SDK's release notes.

The download page is http://downloads.activestate.com/ActivePerl/Windows/5.6/

s60 2nd Ed Fp2 Vs S60 3rd Ed FP any

jimgilmour1 | 13/10/2008, 12:09

Why did the sound on the emulator change in 3rd Edition and more importantly who chose to select Dolby 5 stereo and then could not suppport the driver block information.

Put simply we need a way of turning OFF MultiMedia Sound and why, NO model Phone will support this level, and in case you did not realise stereo 192kb can only be delivered by bluetooth.

Why did the driver select code 3 Dolby 5 and not select 0 standard PC sound. Initially I thought this was just Desktop PC, but this fails on my humble Vista laptop. We need a new driver or the same sound driver as 2nd Edition.
Jim

Re: s60 2nd Ed Fp2 Vs S60 3rd Ed FP any

ltomuta | 13/10/2008, 13:21

ltomuta

Hi Jim,

good question for the SDK team. I'll pass it on.

You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditFurlTechnocratiMagnoliaTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxCarbiderE20E7cE2025E20OctoberE2cE202007E2009E3a28E20AtE20postE3aEa0AssemblingE20GUIE20setE20reflectingE20futureE20BluSPANE20functionalityE20IE20haveE20shownE20theE20GUIE20thatE20willE20takeE20placeE20atE20BluSPANE20applicationE2eE20NowE20IE20willE20tellE20youE20aboutEa0someE20difficultiesE20IE92veE20facedE20duringE20thisE2eSinceE20theE20E93StatusE94E20menuE2ditemE20inE20OptionsE20menuE20wasE20createdE2cE20IE20wantedE20itE20toE20performE20E51ueryE20E4cistE20popupE20forE20userE20canE20selectE20hisE20statusE2eE20ThisE20wasE20doneE20withE20E93E4cistE20SingleE20E51ueryE20E44ialogE94E20componentE2eE20AfterE20lotsE20ofE20researchE2cE20andE20lookingE20atE2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fopenE2dsourceE2dbluetoothE2dpansE2dforumE2dnokiaE2dblogE2f2007E2f10E2f25E2fcodeE2dimplementationE2dforE2dguiX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxOpenE20SourceE20BluetoothE20PANE27sE20ForumE20NokiaE20BlogE20E7cE20CodeE20implementationE20forE20GUIX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfnTypeZBlogContentQ qdcZtypeQUqfnTypeZBlogE45ntryQ qdcZtypeQUqfnTypeZCommunityContentQ qdcZtypeQUqfnTypeZE52esourceQ qdcZtypeQUqfnTypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxCarbiderE20E7cE2025E20OctoberE2cE202007E2009E3a28E20AtE20postE3aEa0AssemblingE20GUIE20setE20reflectingE20futureE20BluSPANE20functionalityE20IE20haveE20shownE20theE20GUIE20thatE20willE20takeE20placeE20atE20BluSPANE20applicationE2eE20NowE20IE20willE20tellE20youE20aboutEa0someE20difficultiesE20IE92veE20facedE20duringE20thisE2eSinceE20theE20E93StatusE94E20menuE2ditemE20inE20OptionsE20menuE20wasE20createdE2cE20IE20wantedE20itE20toE20performE20E51ueryE20E4cistE20popupE20forE20userE20canE20selectE20hisE20statusE2eE20ThisE20wasE20doneE20withE20E93E4cistE20SingleE20E51ueryE20E44ialogE94E20componentE2eE20AfterE20lotsE20ofE20researchE2cE20andE20lookingE20atE2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUqfnTopicZcppQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZseriesE5f60QRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfnTypeZBlogContentQ qfnZtypeQUqfnTypeZBlogE45ntryQ qfnZtypeQUqfnTypeZCommunityContentQ qfnZtypeQUqfnTypeZE52esourceQ qfnZtypeQUqfnTypeZWebpageQ qfnZupdatedQDx2007E2d11E2d02X qfnZuserE5ftagQSxs60X qfnZuserE5ftagQSxsymbianE2dcE2bE2bX qmarsZdescriptionQSxCarbiderE20E7cE2025E20OctoberE2cE202007E2009E3a28E20AtE20postE3aEa0AssemblingE20GUIE20setE20reflectingE20futureE20BluSPANE20functionalityE20IE20haveE20shownE20theE20GUIE20thatE20willE20takeE20placeE20atE20BluSPANE20applicationE2eE20NowE20IE20willE20tellE20youE20aboutEa0someE20difficultiesE20IE92veE20facedE20duringE20thisE2eSinceE20theE20E93StatusE94E20menuE2ditemE20inE20OptionsE20menuE20wasE20createdE2cE20IE20wantedE20itE20toE20performE20E51ueryE20E4cistE20popupE20forE20userE20canE20selectE20hisE20statusE2eE20ThisE20wasE20doneE20withE20E93E4cistE20SingleE20E51ueryE20E44ialogE94E20componentE2eE20AfterE20lotsE20ofE20researchE2cE20andE20lookingE20atE2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfnTypeZBlogContentQ qrdfZtypeQUqfnTypeZBlogE45ntryQ qrdfZtypeQUqfnTypeZCommunityContentQ qrdfZtypeQUqfnTypeZE52esourceQ qrdfZtypeQUqfnTypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ