×

Discussion Board

Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Carbide 1.1 Developer problems

    Hello

    I just went from Carbide Express 1.0 to 1.1 Developer.

    First I tried reusing my old projects but kept getting a strange error. I figured there might be problems with project settings between the two versions so I created an empty S60 v3 GUI project using the Carbide 1.1 Dev wizard. I also gave it a new workspace. Unfortunately the problem still exists and it doesn't seem to have anything to do with the actual code since my /data files look the same coming from the wizard as the ones I'm using in my projects that work with 1.0 Express.

    I will paste my build ouput here. The error is:

    make: *** [C:/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.rsc] Error 1

    The rsc file is created and the exe is created too but they are not found by the emulator.

    I will post the full ouput in the next entry due to message length limitation

  2. #2
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    And here is the full output:

    Code:
    **** Full rebuild of configuration S60 3.0 Emulator Debug for project PhotoManager_S60_v3 ****
    
    make -k all 
    'Building file: ../gfx/PhotoManager_S60_v3.mifdef'
    'Invoking: MIF Compiler'
    perl -S epocmifdef.pl  -p"K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\" -hC:\Symbian\9.1\S60_3rd\EPOC32\include\PhotoManager_S60_v3.mbg -o"/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.mif" ../gfx/PhotoManager_S60_v3.mifdef
    Reading source list file: ../gfx/PhotoManager_S60_v3.mifdef.txt
    Checking: K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\gfx\qgn_menu_PhotoManager_S60_v3.svg
    Choosing...
    Loading mif icons...
    Loading file: K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\gfx\qgn_menu_PhotoManager_S60_v3.svg
    Writing mif: /Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.mif
    Writing mbg...C:\Symbian\9.1\S60_3rd\EPOC32\include\PhotoManager_S60_v3.mbg
    'Finished building: ../gfx/PhotoManager_S60_v3.mifdef'
    ' '
    'Building file: ../data/PhotoManager_S60_v3.rss'
    'Invoking: Resource Compiler'
    perl.exe -S epocrc.pl -u -MD -DLANGUAGE_SC -I"K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -I"K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -I- -I"C:\Symbian\9.1\S60_3rd\epoc32\include" -I"C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -IC:\Symbian\9.1\S60_3rd\epoc32\include\oem -o"C:/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.rsc" -hC:\Symbian\9.1\S60_3rd\EPOC32\include\PhotoManager_S60_v3.rsg ../data/PhotoManager_S60_v3.rss
    
    ..\data\PhotoManager_S60_v3.rss(127) : Warning: (047) the STRUCT that this resource is based on contains a STRUCT[] data member which has not been used in this resource, the missing element is: 'view_list'
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(220) : Warning: (045) the following label is used but has not been declared: R_AVKON_LIST_HEADING_PANE
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(683) : Warning: (045) the following label is used but has not been declared: R_AVKON_SOFTKEYS_OK_CANCEL
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(693) : Warning: (045) the following label is used but has not been declared: R_AVKON_SOFTKEYS_OK_CANCEL
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(823) : Warning: (045) the following label is used but has not been declared: R_AKN_SELECTION_LIST_DIALOG
    make: *** [C:/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.rsc] Error 1
    'Building file: ../src/PhotoManager_S60_v3.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3.o ../src/PhotoManager_S60_v3.cpp
    'Finished building: ../src/PhotoManager_S60_v3.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3AppUi.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3AppUi.o ../src/PhotoManager_S60_v3AppUi.cpp
    'Finished building: ../src/PhotoManager_S60_v3AppUi.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3AppView.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3AppView.o ../src/PhotoManager_S60_v3AppView.cpp
    'Finished building: ../src/PhotoManager_S60_v3AppView.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3Application.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3Application.o ../src/PhotoManager_S60_v3Application.cpp
    'Finished building: ../src/PhotoManager_S60_v3Application.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3Document.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3Document.o ../src/PhotoManager_S60_v3Document.cpp
    'Finished building: ../src/PhotoManager_S60_v3Document.cpp'
    ' '
    'Building file: ../.generated/winscw_uid.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o .generated/winscw_uid.o ../.generated/winscw_uid.cpp
    'Finished building: ../.generated/winscw_uid.cpp'
    ' '
    'Building target: C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe'
    'Invoking: WINSCW C/C++ Linker'
    mwldsym2.exe -sym full -subsystem windows -msgstyle parseable -nowraplines -stdlib -noimplib -m="?_E32Bootstrap@@YGXXZ" -leexe.lib  -leuser.lib -lapparc.lib -lcone.lib -leikcore.lib -lavkon.lib -lcommonengine.lib -lefsrv.lib -lestor.lib  -L"C:\Symbian\9.1\S60_3rd\epoc32\release\winscw\udeb" -o "C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe" -search  ./src/PhotoManager_S60_v3.o ./src/PhotoManager_S60_v3AppUi.o ./src/PhotoManager_S60_v3AppView.o ./src/PhotoManager_S60_v3Application.o ./src/PhotoManager_S60_v3Document.o  ./.generated/winscw_uid.o    
    'Finished building target: C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe'
    ' '
    make: Target `all' not remade because of errors.
    Build complete for project PhotoManager_S60_v3
    Last edited by ltomuta; 2007-03-16 at 21:21. Reason: Now is a bit more ... reader friendly

  3. #3
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    As you can see both the rsc and exe are created but something seem to go wrong. Anyone else had this problems?

    Is there a problem having both 1.0 Express and 1.1 Developer installed?

    Do I need to reinstall perl or the SDKs?

    Please help me out since I'm evaluating 1.1 to see if we should buy it for the company. It's essential that I get on device debug going.

    Many thanks,

    Martin Malek

  4. #4
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,684

    Re: Carbide 1.1 Developer problems

    Can it happen that you have the emulator running in the background? You should stop it prior to (re-)building resources.

  5. #5
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    I wish it was that easy. I restarted my computer and still get the same problems.

    I don't get it why I get an error when in fact it does create a new rsc file. Am I really the only one that has had this problem?

  6. #6
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: Carbide 1.1 Developer problems

    Quote Originally Posted by Martin_Malek
    Code:
    ...
    Writing mif: /Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.mif
    Writing mbg...C:\Symbian\9.1\S60_3rd\EPOC32\include\PhotoManager_S60_v3.mbg
    'Finished building: ../gfx/PhotoManager_S60_v3.mifdef'
    ' '
    'Building file: ../data/PhotoManager_S60_v3.rss'
    'Invoking: Resource Compiler'
    perl.exe -S epocrc.pl -u -MD -DLANGUAGE_SC -I"K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -I"K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -I- -I"C:\Symbian\9.1\S60_3rd\epoc32\include" -I"C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -IC:\Symbian\9.1\S60_3rd\epoc32\include\oem -o"C:/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.rsc" -hC:\Symbian\9.1\S60_3rd\EPOC32\include\PhotoManager_S60_v3.rsg ../data/PhotoManager_S60_v3.rss
    
    ..\data\PhotoManager_S60_v3.rss(127) : Warning: (047) the STRUCT that this resource is based on contains a STRUCT[] data member which has not been used in this resource, the missing element is: 'view_list'
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(220) : Warning: (045) the following label is used but has not been declared: R_AVKON_LIST_HEADING_PANE
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(683) : Warning: (045) the following label is used but has not been declared: R_AVKON_SOFTKEYS_OK_CANCEL
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(693) : Warning: (045) the following label is used but has not been declared: R_AVKON_SOFTKEYS_OK_CANCEL
    C:\\Symbian\\9.1\\S60_3rd\\epoc32\\include\\avkon.rh(823) : Warning: (045) the following label is used but has not been declared: R_AKN_SELECTION_LIST_DIALOG
    make: *** [C:/Symbian/9.1/S60_3rd/EPOC32/RELEASE/WINSCW/UDEB/Z/resource/apps/PhotoManager_S60_v3.rsc] Error 1
    'Building file: ../src/PhotoManager_S60_v3.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3.o ../src/PhotoManager_S60_v3.cpp
    'Finished building: ../src/PhotoManager_S60_v3.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3AppUi.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3AppUi.o ../src/PhotoManager_S60_v3AppUi.cpp
    'Finished building: ../src/PhotoManager_S60_v3AppUi.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3AppView.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3AppView.o ../src/PhotoManager_S60_v3AppView.cpp
    'Finished building: ../src/PhotoManager_S60_v3AppView.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3Application.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3Application.o ../src/PhotoManager_S60_v3Application.cpp
    'Finished building: ../src/PhotoManager_S60_v3Application.cpp'
    ' '
    'Building file: ../src/PhotoManager_S60_v3Document.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o src/PhotoManager_S60_v3Document.o ../src/PhotoManager_S60_v3Document.cpp
    'Finished building: ../src/PhotoManager_S60_v3Document.cpp'
    ' '
    'Building file: ../.generated/winscw_uid.cpp'
    'Invoking: WINSCW C/C++ Compiler'
    mwccsym2.exe -sym full -c -wchar_t off -align 4 -enum int -str pool -nostdinc -exc ms -inline off -msgstyle parseable -nowraplines -cwd source -O0 -D_UNICODE -D__SYMBIAN32__ -D__CW32__ -D__WINS__ -D__EXE__ -D__WINSCW__ -D_DEBUG -D__SUPPORT_CPP_EXCEPTIONS__ -D__SERIES60_30__ -D__SERIES60_3X__ -include "C:\Symbian\9.1\S60_3rd\epoc32\include\variant\Symbian_OS_v9.1.hrh" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\inc" -i "K:\applications\stable\Solutions\Symbian_Test\PhotoManager_S60_v3\data" -i- -i "C:\Symbian\9.1\S60_3rd\epoc32\include" -i "C:\Symbian\9.1\S60_3rd\epoc32\include\variant" -i C:\Symbian\9.1\S60_3rd\epoc32\include\oem -w cmdline -w pragmas -w empty -w possible -w unusedarg -w unusedvar -w extracomma -w pedantic -w largeargs -w ptrintconv -w tokenpasting -w missingreturn -MD -o .generated/winscw_uid.o ../.generated/winscw_uid.cpp
    'Finished building: ../.generated/winscw_uid.cpp'
    ' '
    'Building target: C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe'
    'Invoking: WINSCW C/C++ Linker'
    mwldsym2.exe -sym full -subsystem windows -msgstyle parseable -nowraplines -stdlib -noimplib -m="?_E32Bootstrap@@YGXXZ" -leexe.lib  -leuser.lib -lapparc.lib -lcone.lib -leikcore.lib -lavkon.lib -lcommonengine.lib -lefsrv.lib -lestor.lib  -L"C:\Symbian\9.1\S60_3rd\epoc32\release\winscw\udeb" -o "C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe" -search  ./src/PhotoManager_S60_v3.o ./src/PhotoManager_S60_v3AppUi.o ./src/PhotoManager_S60_v3AppView.o ./src/PhotoManager_S60_v3Application.o ./src/PhotoManager_S60_v3Document.o  ./.generated/winscw_uid.o    
    'Finished building target: C:/Symbian/9.1/S60_3rd/epoc32/release/WINSCW/UDEB/PhotoManager_S60_v3.exe'
    ' '
    make: Target `all' not remade because of errors.
    Build complete for project PhotoManager_S60_v3
    As you can see the main resource was not built and there is no atempt to build the registration resource either, therfore the application is invisible. You are also using a deprecated version of the SDK, please try the MR version.

  7. #7
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    Quote Originally Posted by ltomuta
    As you can see the main resource was not built and there is no atempt to build the registration resource either, therfore the application is invisible. You are also using a deprecated version of the SDK, please try the MR version.
    Hi Itomuta

    Thanks for pointing out the MR issue to me. I will upgrade as soon as I get back to work on monday. Do you think this could be the issue? I'm using that SDK with Carbide 1.0 Express and it works just fine creating sis and all.

    Would you know of any other reasons why the resource files are not built? This test project contains nothing but wizzard generated code.

    Do you know of any other reports with broken resource compilers? Or perhaps some incompabilities when having both Carbide 1.0 Express and 1.1 Developer installed?

    Do the resource compilers come with the SDKs or with the IDE. I'm asking so I know which one to re-install.

    Many thanks,

    Martin Malek

  8. #8
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: Carbide 1.1 Developer problems

    Working with up-to-date tools (e.g. Carbide.c++ 1.1) and SDKs (S60 3rd SDK MR) can only help yet I could not finger point the exact problem in your case.

    Multiple Carbide installation should also not interfere with each other as long as they are installed in different locations and have different workspaces.

  9. #9
    Registered User
    Join Date
    Oct 2006
    Posts
    8

    Re: Carbide 1.1 Developer problems

    Hi,

    I had similar problem when I have installed Carbide 1.1 Express edition. The reason was the Carbide installation path. I used the default installation folder, which contained white spaces and also could not compile skeleton code. I reinstalled using folder name without white spaces and all worked fine. So maybe that is the case?

  10. #10
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    That might very well be it. I too use the default installation path. Will re-install first thing in the morning. Thanks for the tip.

    / Martin Malek

  11. #11
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: Carbide 1.1 Developer problems

    Quote Originally Posted by mGolonka
    Hi,

    I had similar problem when I have installed Carbide 1.1 Express edition. The reason was the Carbide installation path. I used the default installation folder, which contained white spaces and also could not compile skeleton code. I reinstalled using folder name without white spaces and all worked fine. So maybe that is the case?
    I find this hard to believe and in fact I have all versions of Carbide installed with the default blank spaced paths without any side effects. The path to the workspace however, that is a different story. In fact this issue is documented in Carbide's release notes (IIRC).

  12. #12
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    Quote Originally Posted by ltomuta
    I find this hard to believe and in fact I have all versions of Carbide installed with the default blank spaced paths without any side effects. The path to the workspace however, that is a different story. In fact this issue is documented in Carbide's release notes (IIRC).
    Itomuta. You are absolutely right. The installation path does not matter what DOES matter is the workspace path. I changed to a path without spaces and it works fine. Perhaps it's time to start reading them release notes.

    (Or perhaps it's time to fix that white space bug which makes me feel like it's still 1980)

    Thanks,

    Martin Malek

  13. #13
    Registered User
    Join Date
    Sep 2006
    Posts
    47

    Re: Carbide 1.1 Developer problems

    Let me rephrase that. Wizard projects now work fine. As for my imported 1.0 Express projects I still experience the problem with failed *.rsc compilation in emulator debug mode and linking problems in release gcc mode.

    In GCC mode the linker complains that it can't find any of the libraries or dso's.

  14. #14
    Registered User
    Join Date
    Feb 2007
    Posts
    6

    Re: Carbide 1.1 Developer problems

    Hello,

    I can add some information, as I am having the same problem as Martin Malek. I have found that it may be related to the Carbide.c++ project importing.

    Please let me explain:
    1. A new Carbide.c++ 1.1 DEV project was created in a brand new workspace area for Carbide 1.1. This project builds just fine. S60 3 SDK was used.

    2. Now, as in most software development projects, our team uses source revision control software, and our development projects must be able to be placed on any area of the filesystem, for example: Doing feature development on a trunk checkout, while bugfixing on a release branch checkout.

    3. Each developer in the team handled this in Carbide.c++ 1.0 by importing the currently active carbide project into his workspace using the "import from existing project" function.

    4. When i create a copy the created project mentioned in (1) and import it into a different workspace in Carbide.c++ 1.1 DEV, it causes the above mentioned problems with the *.rsc compilation. Same thing happens if i import it directly from the original workspace.

    Anybody seen this, or have any ideas?

    BR
    Björn

  15. #15
    Registered User
    Join Date
    Jan 2007
    Posts
    15

    Re: Carbide 1.1 Developer problems

    bjorn,

    I'm having this same issue.

    I've tried copying the checkout project into the workspace directory then importing. That seems to fix the rsc compilation error, but now after carbide creates the exe, it doesn't go on to create the pkg or sis files.

    For me this has all been done in carbide.c++ 1.1 developer so there are no version issues. The SDK has always been the same S60 FP1.

    What is the next workaround/magic that needs to be done?

    Thanks,
    Sherman

    Quote Originally Posted by scalado-bjorna
    Hello,

    I can add some information, as I am having the same problem as Martin Malek. I have found that it may be related to the Carbide.c++ project importing.

    Please let me explain:
    1. A new Carbide.c++ 1.1 DEV project was created in a brand new workspace area for Carbide 1.1. This project builds just fine. S60 3 SDK was used.

    2. Now, as in most software development projects, our team uses source revision control software, and our development projects must be able to be placed on any area of the filesystem, for example: Doing feature development on a trunk checkout, while bugfixing on a release branch checkout.

    3. Each developer in the team handled this in Carbide.c++ 1.0 by importing the currently active carbide project into his workspace using the "import from existing project" function.

    4. When i create a copy the created project mentioned in (1) and import it into a different workspace in Carbide.c++ 1.1 DEV, it causes the above mentioned problems with the *.rsc compilation. Same thing happens if i import it directly from the original workspace.

    Anybody seen this, or have any ideas?

    BR
    Björn

Similar Threads

  1. Error 1 file I/O fault when i upgraded to carbide express 1.1
    By seamus_rooney in forum Symbian Tools & SDKs
    Replies: 8
    Last Post: 2008-07-01, 22:16
  2. Migrating from Carbide C++ 1.0 to 1.1
    By patrickfrei in forum Symbian
    Replies: 1
    Last Post: 2006-12-13, 16:39
  3. Post-Build tried in Express 1.0 and Developer 1.1
    By AlexeiPi in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 6
    Last Post: 2006-10-06, 17:36
  4. Carbide or NDS 1.1 with S60 2nd Ed FP1 SDK?
    By dsreich in forum Symbian Tools & SDKs
    Replies: 1
    Last Post: 2005-11-08, 07:40

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×