Linking error using S60_3rd_Beta SDK

[iulian_moldovan]

Hello!

I get a link error when I'm trying to build my project:

mwldsym2.exe: Undefined symbol: 'int E32Main(void) (?E32Main@@YAHXZ)'
mwldsym2.exe: referenced from '__E32Startup' in uc_exe.cpp:46 (EEXE.LIB)
Errors caused tool to abort.
MyProject : error PRJ0002 : error result returned from 'link.exe'.

eexe.lib is linked

The project I'm trying to build is in fact a S60_v20 project that I'm trying to port to S60_3rd_Beta. I eliminated all the missing libraries, I fixed all compiler's new raisen errors, but I'm stuck here.

Can anybody help?

I mention again that I'm using Vs.NET +Carbide.vs + S60_3rd_Beta SDK

[mitts]

Hi,

I'm seriously outside my area of competence here but did you modify the application entry point to something like:

GLDEF_C TInt E32Main()

Somebody else will have to fill in the details but the way that application entry point is defined has changed when moving to 3.0.

[iulian_moldovan]

No, the entry point is

GLDEF_C TInt E32Dll( /*TDllReason*/ )
{
	return KErrNone;
}

For the moment TDllReason triggers a compiler error, so I commented it.

Thanks anyway for your information, I will check the doc.

[mitts]

Just out of curiosity, how did you create the 3.0 project, using import and setting project type to Symbian9 or using the Clone function?

[iulian_moldovan]

I used Import then setting to Symbian9, not Clone.
Why?

[mitts]

Just curious to know if anybody finds the Clone thing useful as this is something for which there is no previous comparable functionality. Were you able to get the build to work?

[iulian_moldovan]

Just curious to know if anybody finds the Clone thing useful as this is something for which there is no previous comparable functionality. Were you able to get the build to work?

Nope, I did not use Clone until now.
The problem is that I had multiple mmp files / projects in 60_20 and some custom libraries and now I cannot build in the right way since I do not have the libraries rebuilt for this Symbian version.

If I get the build to work? No! I removed all custom libraries and related-code, but I somehow managed to make my emulator crash at it's initialization and the epoc.exe file dissappear.

I still think if it would be better to start a fresh new S60_3rd application and add my old application files one by one (but there's almost 140 of them)

[mitts]

But you got past the linking problme then I gather?

Another thing to watch out for is the UID used for 3.0, the emulator is quite picky with that. Carbide.vs uses the range 0x10000000-0x1FFFFFFF.

See for instance: http://discussion.forum.nokia.com/fo...ad.php?t=69289

[RyanSantos]

I think that the solution to the linking problem is that there is a binary break when it comes to S60 3rd Ed due to the new kernel defined in the code by the "EKA2" macro and that there is a new framework for doing the UI. Hope I get this right because from my point of view, instead of doing the usual

EXPORT_C CApaApplication* NewApplication()
{
return new YourApplication;
}

// DLL entry point, return that everything is ok
GLDEF_C TInt E32Dll(TDllReason)
{
return KErrNone;
}

You do

// Create an application, and return a pointer to it
CApaApplication* NewApplication()
{
return new YourApplication;
}


TInt E32Main()
{
return EikStart::RunApplication(NewApplication);
}

For me it is so much easier doing the ff:
1. Creating a new project using Codewarrior v3.1 and S60 3rd Ed SDK
2. Editing the MMP file to include the required libraries and additional files after you copy them to the project directory in a folder of your choice
3. Re-importing the project and making sure everything compiles smoothly
4. Test if your functionality still works as expected.

Hope this helps.

[iulian_moldovan]

Thanks!

I did that last week, and that was the only solution. It was kinda' tricky because I had to use my old app files, I copied the ones from the new application and adapted them.... a whole story. But it works.

Thanks anyway!

[prakashnadar]

if you building a application and not a dll, then you need to ahve E32main inside your project and not E32Dll

[RyanSantos]

Does that always hold true for s60_3rd_Beta SDK about having E32Main instead of E32Dll?

In previous SDKs, it does not follow that if you are building a Symbian application or an *.app it does not mean that your entry point should necessarily be an E32Main. I have been building Symbian apps and dlls using E32Dll in S60 2nd Ed FP2

[prakashnadar]

Ryan,

with my humble experience on symbian, for apps and dll, you need E32DLL as the entry point which is correct, I dont know if you there is any way to have E32Main as the entry point for apps, and dll (apps are dlls anyways).

In symbian 9, Targettype=App is deprecated. as i was answering the original question (I assumed that he was building an app project using symbian 9)

-Prakash

[RyanSantos]

Thanks for your answer =)

I thought that apps still needed an E32Dll entry point in Symbian OS v9.1. When I create a new project using Codewarrior v3.1 for S60_3rd_Beta SDK, I get #ifdefs in my project and those #ifdefs show that it is still possible to have an E32Main and an E32Dll if the macros __UI_FRAMEWORKS_V2__ is defined and EKA2 is not defined.

[prakashnadar]

it is still possible to have an E32Main and an E32Dll if the macros __UI_FRAMEWORKS_V2__ is defined and EKA2 is not defined.

Yes ryan, if I am not wrong , this is only applicable to targettype=exedll and not for either exe or dll.

-prakash