×

Discussion Board

Page 1 of 2 12 LastLast
Results 1 to 15 of 22

Thread: GCCE build

  1. #1
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    GCCE build

    Hello,

    I followed the instructions on the document to build my project for real devices. However, I couldn't find the option "Phone Debug(GCCE)" or "Phone Release(GCCE)" in the build configurations of Carbide C++. The only option is for ARMV5, but I couldn't successfully build the project with ARMV5 as well. Did I miss anything when installing Qt for S60? Thank you.

    haining

  2. #2
    Regular Contributor
    Join Date
    Mar 2009
    Posts
    430

    Re: GCCE build

    It sounds like you have not installed the Qt Libraries in the SDK. This was necessary for the second last version of Qt (Garden). However, with Temple you should only have to run the installer and everything should be set up.

    You have to buy the ARMV5-compiler, it does not come with the SDK, to this approach cannot work.

    Can you compile other projects fine? Because the S60 SDK asks you wether you want to install the CSL ARM toolchain. You have to do this in order to get gcce.

    Can you build your project on the command line?

  3. #3
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Actually, I am using "tower". I downloaded the binary package, and just executed the file to install the SDK. And I am sure CSL ARM toolchain was installed. Should I do something more in order to get the GCCE complier?

    I can see the GCCE compile option in a Symbian C++ project, but not in the Qt project. This is really weird.

    Can you give me some hints for compiling the project on command line? I tried to compile the project in my project directory with the command "make release-gcce". But it didn't worked at all.

    Thank you!

  4. #4
    Regular Contributor
    Join Date
    Mar 2009
    Posts
    430

    Re: GCCE build

    Hi,
    yes, make release-gcce should do it. What is the error message? Remember to use the Qt command prompt from the start menu. Also you have to include the bin-directory of the Qt installation to PATH and execute that bat-file from the start menu somewhere in the nokia stuff to add some more environment variables.

  5. #5
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Quote Originally Posted by axeljaeger View Post
    Hi,
    yes, make release-gcce should do it. What is the error message? Remember to use the Qt command prompt from the start menu. Also you have to include the bin-directory of the Qt installation to PATH and execute that bat-file from the start menu somewhere in the nokia stuff to add some more environment variables.
    Do you mean I need to start the Qt command from the start menu, and then change the directory to my project folder and then just type "make release-gcce" under my project folder?

  6. #6
    Regular Contributor
    Join Date
    Mar 2009
    Posts
    430

    Re: GCCE build

    Yes, that is exactly what I am suggesting.

  7. #7
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Quote Originally Posted by hainingwu View Post
    Do you mean I need to start the Qt command from the start menu, and then change the directory to my project folder and then just type "make release-gcce" under my project folder?
    I got the same error:

    ABLD ERROR: "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\workspace\MobileCaddy\GCCE.make" not yet created

  8. #8
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Quote Originally Posted by hainingwu View Post
    I got the same error:

    ABLD ERROR: "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\workspace\MobileCaddy\GCCE.make" not yet created
    After I manually set the environment variable EPOCROOT to my Symbian SDK path, the error above disappeared and it seemed like doing something. But still it's not like a successful compilation. I only found a .exe file under "C:\S60\devices\S60_3rd_FP2_SDK_v1.1\epoc32\release\gcce\urel". I have no idea where the .sis file should be. The compiling message is:

    Code:
    ABLD.BAT build gcce urel
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\EXPORT.make" EXPORT VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    Nothing to do
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\GCCE.make" MAKEFILE VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    make -s  -C \Symbian\Carbide\workspace\MobileCaddy -f "MAKEFILE_0XEAC342AD.MK" T
    O_ROOT=..\..\..\.. EPOCBLD=..\..\..\..\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\B
    UILD\Symbian\Carbide\workspace\MobileCaddy\MAKEFILE_0XEAC342AD\GCCE TO_BLDINF=..
    \..\..\..\Symbian\Carbide\workspace\MobileCaddy PLATFORM=GCCE MAKMAKE
    perl -S makmake.pl  -D \Symbian\Carbide\workspace\MobileCaddy\MOBILECADDY_0XEAC3
    42AD GCCE
            perl -S ecopyfile.pl "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Sym
    bian\Carbide\workspace\MobileCaddy\MOBILECADDY_0XEAC342AD\GCCE\MobileCaddy.rsg"
    "\S60\devices\S60_3rd_FP2_SDK_v1.1\epoc32\include\MobileCaddy.rsg"
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\GCCE.make" LIBRARY VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    make -s  -C \Symbian\Carbide\workspace\MobileCaddy -f "MAKEFILE_0XEAC342AD.MK" T
    O_ROOT=..\..\..\.. EPOCBLD=..\..\..\..\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\B
    UILD\Symbian\Carbide\workspace\MobileCaddy\MAKEFILE_0XEAC342AD\GCCE TO_BLDINF=..
    \..\..\..\Symbian\Carbide\workspace\MobileCaddy PLATFORM=GCCE LIB
    make -s  -r -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\w
    orkspace\MobileCaddy\MOBILECADDY_0XEAC342AD\GCCE\MOBILECADDY_0XEAC342AD.GCCE" LI
    BRARY
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\GCCE.make" RESOURCE CFG=UREL VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    make -s  -C \Symbian\Carbide\workspace\MobileCaddy -f "MAKEFILE_0XEAC342AD.MK" T
    O_ROOT=..\..\..\.. EPOCBLD=..\..\..\..\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\B
    UILD\Symbian\Carbide\workspace\MobileCaddy\MAKEFILE_0XEAC342AD\GCCE TO_BLDINF=..
    \..\..\..\Symbian\Carbide\workspace\MobileCaddy PLATFORM=GCCE CFG=UREL RESOURCE
    make -s  -r -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\w
    orkspace\MobileCaddy\MOBILECADDY_0XEAC342AD\GCCE\MOBILECADDY_0XEAC342AD.GCCE" RE
    SOURCEUREL
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\GCCE.make" TARGET CFG=UREL VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    make -s  -C \Symbian\Carbide\workspace\MobileCaddy -f "MAKEFILE_0XEAC342AD.MK" T
    O_ROOT=..\..\..\.. EPOCBLD=..\..\..\..\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\B
    UILD\Symbian\Carbide\workspace\MobileCaddy\MAKEFILE_0XEAC342AD\GCCE TO_BLDINF=..
    \..\..\..\Symbian\Carbide\workspace\MobileCaddy PLATFORM=GCCE CFG=UREL BLD
    make -s  -r -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\w
    orkspace\MobileCaddy\MOBILECADDY_0XEAC342AD\GCCE\MOBILECADDY_0XEAC342AD.GCCE" UR
    EL
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'
      make -r  -f "\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\BUILD\Symbian\Carbide\wo
    rkspace\MobileCaddy\GCCE.make" FINAL CFG=UREL VERBOSE=-s
    make[1]: Entering directory `C:/Symbian/Carbide/workspace/MobileCaddy'
    make -s  -C \Symbian\Carbide\workspace\MobileCaddy -f "MAKEFILE_0XEAC342AD.MK" T
    O_ROOT=..\..\..\.. EPOCBLD=..\..\..\..\S60\devices\S60_3rd_FP2_SDK_v1.1\EPOC32\B
    UILD\Symbian\Carbide\workspace\MobileCaddy\MAKEFILE_0XEAC342AD\GCCE TO_BLDINF=..
    \..\..\..\Symbian\Carbide\workspace\MobileCaddy PLATFORM=GCCE CFG=UREL FINAL
    make[1]: Leaving directory `C:/Symbian/Carbide/workspace/MobileCaddy'

  9. #9
    Super Contributor
    Join Date
    Oct 2007
    Location
    જુનાગઢ - India
    Posts
    3,034

    Re: GCCE build

    Quote Originally Posted by hainingwu View Post
    I followed the instructions on the document to build my project for real devices. However, I couldn't find the option "Phone Debug(GCCE)" or "Phone Release(GCCE)" in the build configurations of Carbide C++. The only option is for ARMV5, but I couldn't successfully build the project with ARMV5 as well. Did I miss anything when installing Qt for S60?
    Me and my friends also noticed that problem. However after unchecking "Filter build configuration option" (You get this option during creating new project)we get option of building application for Phone Release(GCCE). Check if this is the case for u also.

    Attached Images Attached Images

  10. #10
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Quote Originally Posted by savaj View Post
    Me and my friends also noticed that problem. However after unchecking "Filter build configuration option" (You get this option during creating new project)we get option of building application for Phone Release(GCCE). Check if this is the case for u also.

    Yes!! It worked on my machine! Thanks!!!

  11. #11
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Ok, thanks all you guys, finally I created the .sis file and installed the application on my E65. Then when I execute the program, there's a message saying something like "The function is not supported." (Sorry, I have to translate the message from Chinese. ) I have installed everything necessary for running Qt for S60 on real devices, but I couldn't run the demo as well. I doubt that E65 support Qt for S60?

    haining

  12. #12
    Regular Contributor
    Join Date
    Mar 2009
    Posts
    430

    Re: GCCE build

    Do you have both the temple-Qt-libs installed on your device as well as openc beta?

  13. #13
    Registered User
    Join Date
    Jul 2009
    Posts
    34

    Re: GCCE build

    Quote Originally Posted by axeljaeger View Post
    Do you have both the temple-Qt-libs installed on your device as well as openc beta?
    I installed the following files on my device:

    openc_ssl_s60_1_5_5b.sis
    pips_s60_1_5_5b.sis
    stdcpp_s60_1_5_5b.sis
    qt_libs.sis

    I am not sure what version of qt_libs.sis is. I assume this is the latest "tower" one.

  14. #14
    Regular Contributor
    Join Date
    Mar 2009
    Posts
    430

    Re: GCCE build

    See http://pepper.troll.no/s60prereleases/patches/

    Looks like there are 2 openc-packages: OpenC and OpenC++

  15. #15
    Super Contributor
    Join Date
    Oct 2007
    Location
    જુનાગઢ - India
    Posts
    3,034

    Re: GCCE build

    Quote Originally Posted by hainingwu View Post
    I doubt that E65 support Qt for S60?
    Yes, E65 supports Qt S60. However E65 is S60 SDK 3rd Edition FP1 device, it require special updates, which is available here. Check point 3 and 4 on that page.

Similar Threads

  1. Build GCCE with Carbide C++ 2.0 (S60 3rd FP1) on Vista
    By jeffw2003 in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 6
    Last Post: 2009-05-27, 10:11
  2. Build problem on ARMV5 and GCCE with Carbide c++ 2.0 (S60 3rd Edition FP1)
    By pinkhardlionel in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 10
    Last Post: 2009-01-14, 09:02
  3. Replies: 3
    Last Post: 2008-12-30, 15:46
  4. Problem with GCCE build in Carbide.vs
    By raffaelbechara in forum Symbian
    Replies: 6
    Last Post: 2008-10-20, 16:06

Posting Permissions

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