×

Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Dec 2004
    Location
    Palmas - TO - Brazil
    Posts
    8

    Switching back to Series 60 SDK v1.2, Builder X

    Hi there,

    I have Borland Builder X v1.5 and SDK Series 60 v2.1.
    Its working fine, but now I want to code for older devices like 7650 and 3650. How can I install the older 1.2 SDK, keeping the 2.1 and switching between them ?

  2. #2
    Regular Contributor
    Join Date
    Mar 2004
    Location
    Mobile Village - IN
    Posts
    78
    How to manage development for multiple device types
    A single development machine can have multiple Symbian OS development kits installed. The devices command allows you to specify which Symbian OS device to develop for, and configures the required environment settings according. The command was introduced at v7.0. You need to set a device using the commands explained below in order to use the build and other tools.

    A single kit can itself have an emulator and tools for more than one type of Symbian OS phone\device. A device in a particular kit can therefore be fully specified with an identifier in the form kitname:devicename. You can get a list of all the installed devices by just using the devices command without any switches.

    Because the kitname:devicename form can be quite long, the devices command, for convenience, also allows you to choose an alias name for the device.

    There are a number of levels at which you can set the device that you want to work with.

    default: the default device is assumed for the current session, and for all new sessions, unless you specify otherwise. To set the default device, use the command:

    > devices -setdefault @device-identifier

    per session override: you can change the device used in a particular Windows Command Prompt session by setting in that session the environment variable EPOCDEVICE to the device to use, i.e.

    > set EPOCDEVICE=device-identifier

    per command override: you can override both the default and per session setting for a particular command by specifying the device (prefixed by an @ character) as part of the normal command parameters. For example,

    > bldmake bldfiles @device-identifier

    Example
    The following command-line session:

    lists the available devices

    creates an alias tview for the device os7.00604:com.symbian.techview

    sets the default device to be tview

    displays the default device (confirming what has just been set)

    C:\>devices
    os7.00604:com.symbian.techview
    C:\>devices -setalias tview @os7.00604:com.symbian.techview
    C:\>devices -setdefault @tview
    C:\>devices -default
    Default device: os7.00604:com.symbian.techview (alias tview)
    EPOCROOT compatibility
    Previous to v7.0, the active development kit was set by the user setting the environment variable EPOCROOT. You no longer have to do this: EPOCROOT is set automatically, based on the default device setting and any specified overrides.

    To maintain backward compatibility, however, if EPOCROOT is set by the user, then a stub will not override it with the default device.

    If EPOCROOT is set when a per session or per command device override is attempted, the stub asks you to choose between the conflicting settings.

    Use with pre-v7.0 kits
    Only v7.0 and later kits automatically update the device list when they are installed. If you also want to use the devices command to manage earlier kits, you can add them to the list yourself using the command devices -add, specifying the location of the kit's epoc32\ (the directory that contains the release\ sub-directory) and epoc32\tools\ directories.

    For example, the following command adds a v6.0 SDK which has its epoc32 tree at C:\symbian\6.0\nokiacpp\, and its epoc32\tools tree at C:\symbian\6.0\shared\.

    > devices -add C:\symbian\6.0\nokiacpp\ C:\symbian\6.0\shared\ @v60:com.nokia.cpp

    The device identifier (here v60:com.nokia.cpp) should be descriptive of the kit, but doesn't have to correspond to a particular directory name.

    Use of the devices command is supported for all kits from v6.0.

  3. #3
    Registered User
    Join Date
    Dec 2004
    Location
    Palmas - TO - Brazil
    Posts
    8
    yeah I know about this. but dont works, Im trying to compile a simple helloworld example from the 6.1 SDK, just got this:

    bldmake -v bldfiles
    Can't locate E32env.pm in @INC (@INC contains: E:\SYMBIAN\6.1\SERIES60\EPOC32\TOOLS\ E:/Perl/lib E:/Perl/site/lib .) at E:\Symbian\6.1\Series60\epoc32\tools/bldmake.pl line 31.
    abld -v export
    External process exited with error code : 1
    abld -v makefile WINSB
    External process exited with error code : 1
    abld -v resource WINSB UDEB
    External process exited with error code : 1
    abld -v library WINSB
    External process exited with error code : 1
    Compile finished
    abld -v target WINSB UDEB
    External process exited with error code : 1
    abld -v final WINSB UDEB
    External process exited with error code : 1
    abld -c build WINSB UDEB
    External process exited with error code : 1
    abld -w build WINSB UDEB
    External process exited with error code : 1

Posting Permissions

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