|
|
failed to make sys file
| Tue, 2007-10-30 15:31 | |
|
Hi, I have more 11 days to expire the trial license. I am using carbide on personal laptop:-- lenovo y- series do I require to buy the license now . I get the following errors when I build using "phone release (gcce) S60_3rd_FP1" 1> \Symbian\9.2\S60_3rd_FP1\EPOC32\BUILD\Symbian\Carbide\workspace\helloworld\group\ 2> file I/O fault. helloworld/sis helloworld_S60_3_X_v_1_0_0.pkg line 27 1193745194332 377 3> makesis.exe returned with exit value = 1 When I go for command line build:-------- but: makesis does not work; (in sis folder) following errors are obtained:- Also, |
|
Forum posts: 1890
This is not a license issue but an installation one. I don't remember which were the error that can cause this problem however.
(Working on D: is not necessary a very good idea... if you want to avoid unnecessary annoyance, install everything on C:. If your application does compile and run for emulator then this is not an issue). Another point: avoid Windows Vista.
Eric Bustarret
NewLC Founder & CEO / Professional Symbian OS Consultant
Forum posts: 6
hi,
There are lot of problems then.........
Let me explain exactly what I did.......
It may be very weired explanation but I am confused what to do?
When I bought the laptop:-
I had 2 partitions:----C: and D:
in C:-- I had "vista"
I tried to install symbian on vista, but carbide did not install.
Then I deleted D: drive and made 3 small partitions------ D:,F;,G:(E: is used by DVD RW)
I installed "XP" into D:
then again installed symbian and carbide on "XP"
I did not test if the makesis command was working or not
When I rebooted the laptop
"Vista" did not work(it even did not show up in the OS selection menu , which appears when any system is started)
only "XP" worked
and the factory settings (in vista--like face recognition, shuttle centre) of the system were lost
Then I loaded "Vista" into G: drive
When I rebooted the system:
"XP" did not work(its entry was marked as corrupted in OS selection menu)
both "vista"s (in C: and G:) were working
THEN I COPIED THE SHORTCUT TO CARBIDE FROM D: DRIVE (XP PARTITION) TO DESKTOP OF C; DRIVE(VISTA PARTITION)
AND COULD RUN CARBIDE ON C: DRIVE
Then I thought of repairing the corrupted "XP" on D: drive and on rebooting, the same thing happened:
1.only xp remained
2.no vista was working
3.also makesis was not working even on xp
Now, I again loaded "vista" on G; drive
and again there is no XP.
Now what should I do?
Forum posts: 6
I read some forum posts......
including (C:\Program Files\CSL Arm Toolchain\bin) may solve this problem---------------from what I understood
But in my case which path should I choose:---
C:\Program Files\CSL Arm Toolchain\bin
or
D:\Program Files\CSL Arm Toolchain\bin
Can I add both the paths......
Also in some other forum posts I read that CSL Arm Toolchain is not supported by vista
Now I think I should try to include both the paths on both OS "Vista" and "XP" and then see what happens......
Forum posts: 463
There are a few patches in the forum nokia wiki for vista. But quite frankly, for beginners, I would still suggest sticking to XP as suggested by eric.
To add to eric's suggestion : Have everything on C(your sdk, carbide, workspace) Also note not to have white spaces in the paths of sdk or workspcace.
Forum posts: 6
Hi,
I have formated all of my hard disk.
Loaded xp into C: drive
re-installed everything into c: drive
while installing carbide I got a warning:-------
IF YOU WANT TO BUILD FROM THE EMULATOR FROM THE COMMAND LINE, RUN THE TOOL FROM THE START MENU SHORTCUT: cONFIGURE ENVIRONMENT FOR WINSCW COommand lineMMAND LINE BUILDS. IT WILL SETUP NECESSARY ENVIRONMENT VARIABLES.YOU DO NOT NEED TO DO THIS IF YOU WILL ONLY BE BUILDING EMULATOR TARGETS(WINSCW) FROM IDE.
What does this mean....
how to run the tool from srart menu......
what is this tool......
Forum posts: 699
Clieck on the "Start" button, then "Programs" and then find where Carbide is. There you should also find "Configure environment for WINSCW command line".
Forum posts: 6
I went to the specified location "Start" button/ "Programs" / Carbide / "Configure environment for WINSCW command line" and configured for Winscw cmdline...
I got a cmdline opened that prompted me:--
do you want to make changes..(y/n)
I entered (y)
Now I can build from emulator for both "GCCE build" and "WinScw emulator debug "(sis and sisx files are made )
But not for ARM build(I get 5 errors)
1.RVCT not isntalled or 'armcc' is not on PATH. Please check that your environment for the RVCT compiler is correct.
2. file I/O fault. helloworld/sis helloworld.pkg line 27 1194101913156 9
3.make[1]: *** No rule to make target `\Symbian\9.2\S60_3rd_FP1\EPOC32\BUILD\Symbian\Carbide\workspace\helloworld\group\HELLOWORLD\ARMV5\HELLOWORLD.ARMV5'. Stop.
4.makesis.exe returned with exit value = 1
5.RVCT not isntalled or 'armcc' is not on PATH. Please check that your environment for the RVCT compiler is correct.
Also I can not build from commandline.
bldmake bldfiles gives warning:------
when building for ARMV5 platform COmpiler RVCT2.2 is required
makesis helloworld.pkg returns with error----
1> cannot find file:--<$EPOCROOT>Epoc32/release/$< PLATFORM>/$< TARGET>/helloworld.exe
2>error: I/O fault
I again went to "Start" button/ "Programs" / Carbide / "Configure environment for WINSCW command line"
and got the following lines there--------
This program will attempt to change environment variables reflecting the tools corrs to your current working directory
Current working dir is: C:\Program Files\Nokia\Carbide.C++v 1.2\x86build\env_switch
Tools will be located at C:\Program Files\Nokia\Carbide.C++v 1.2\x86build\Symbian_tools\Command_line_tools
MWCSYM2INCLUDES already reflects tools;not modified
MWSYM2LIBRARIES already reflects tools;not modified
MWSYM2LIBRARYFILES already reflects tools;not modified
PATH already reflects tools;not modified
nOW what to do to build from command line.
But the helloworld.exe file is present in epoc32/release/gcce/urel
Then I opened the .pkg file and added the path of helloworld .exe by replacing
;Files to install
;You should change the source paths to match that of your environment
;
"$(EPOCROOT)Epoc32\release\$(PLATFORM)\$(TARGET)\helloworld.exe" -"!:\sys\bin\helloworld.exe"
"$(EPOCROOT)Epoc32\data\z\resource\apps\helloworld.rsc" -"!:\resource\apps\helloworld.rsc"
"$(EPOCROOT)Epoc32\data\z\private\10003a3f\apps\helloworld_reg.rsc" -"!:\private\10003a3f\import\apps\helloworld_reg.rsc"
"$(EPOCROOT)Epoc32\data\z\resource\apps\helloworld.mif" -"!:\resource\apps\helloworld.mif"
WITH
;Files to install
;You should change the source paths to match that of your environment
;
"C:\Symbian\9.2\S60_3rd_FP1\Epoc32\release\gcce\urel\helloworld.exe" -"!:\sys\bin\helloworld.exe"
"C:\Symbian\9.2\S60_3rd_FP1\Epoc32\data\z\resource\apps\helloworld.rsc" -"!:\resource\apps\helloworld.rsc"
"C:\Symbian\9.2\S60_3rd_FP1\Epoc32\data\z\private\10003a3f\apps\helloworld_reg.rsc" -"!:\private\10003a3f\import\apps\helloworld_reg.rsc"
"C:\Symbian\9.2\S60_3rd_FP1\Epoc32\data\z\resource\apps\helloworld.mif" -"!:\resource\apps\helloworld.mif"
But this means everytime I create a .pkg file, I have to make these changes
Is there any other way
Forum posts: 6
I got another solution...........
it works for carbide c++ v1.2
1.
search the menus on top of carbide.
go to project/active build configuration
select phone release (gcce)
2.
copy ur signed cerificates into any drive(eg. c:,d:..... )
3.
go to
project/properties/carbide build configurations
select all the paths from the menu that appears
Its a one time job per project.
u dont have to type those long commands every time u compile......
Forum posts: 463
Yes true, when you make a gcce build with setting paths to the devcerts, etc, command line is not needed.
Check this http://www.forum.nokia.com/info/sw.nokia.com/id/af80987a-a72d-44cf-bf00-1926be01058c/Carbide_cpp_Getting_Started_v1_1_en.exe.html
Although the screencast is for 1.1, it should be a good starting point for getting used to carbide(For anybody who is looking at this thread for possible solutions)