how to create sis file without using Carbide C++ IDE

[somnathbanik]

Hi,

I am trying to create .sis file from command prompt without using the Carbide C++ IDE.
I tried

first checked the default SDK selected.

"bldmake clean"
"bldmake bldfiles"
"abld build winscw udeb " / "abld build gcce urel"

But the .exe is not generating
I checked in "epoc32\release\winscw\udeb" and "\epoc32\release\gcce\urel" folder but the exe file is not there.
Even I set the environment variable, but nothing happens.

Could anyone please help me how to create the exe file from the project using the Command Prompt and where do I find that exe file?

Thanks in Advance

[wizard_hu_]

Have you executed "Configure environment for WINSCW command line" from the program group of Carbide?

Anyway, either "yes" or "no", there must be some error messages in the build output, try locating them (you may have to increase the buffer size of the command line window).

[kamalakshan]

what is the out put of

abld build gcce urel

Is it getting compiled properly with out any errors.

[somnathbanik]

Hi,

I did the "Configure Environment for WINSCW command line", but the problem is still there , i am not able to create the exe file.
please help me.

[wizard_hu_]

Perhaps this is the time when you should consider checking the build output...

[somnathbanik]

Hi,

Sorry but i didn't get you much. I an trying not to use the carbide IDE. could you please be more specific.

[wizard_hu_]

Hmm... You are probably typing the "abld build winscw udeb" command into a big black rectangle appearing on the screen. After pressing the Enter key, you probably get several lines of text, their color is some kind of light gray. Those are the ones you should read carefully, especially the ones containing sad words like "error" or "failed".

[somnathbanik]

Hi

I got another issue with the Grid icons
please follow the link for the details.

http://discussion.forum.nokia.com/fo...d.php?t=169176


please help me with some code

[kamalakshan]

what about this thread have you got this issue resolved.