ForSPOT

ThumbOrNoThumb

BuildingSquawkForOtherMCUs

BuildingSquawkForOtherCPUs

-Xplat does not appear to work in the main squawk branch. Browse the cvs for a SunSPOT orientated release which appears to support (amongst other things) these build.properties :

# PLATFORM TYPE may be one of:
# BARE_METAL - Squawk runs on the bare metal, implenting inetrrupts, timers, etc.
# DELEGATING - Squawk delagates all IO to another JVM, via JNI
# NATIVE - Squawk runs on an OS, and calls native OS routines for IO, etc.
# SOCKET - Squawk delagates all IO to another JVM, via a socket
#
# The builder will synthesize definitions of four additional properties: PLATFORM_TYPE_BARE_METAL,
# PLATFORM_TYPE_DELEGATING, PLATFORM_TYPE_NATIVE, and PLATFORM_TYPE_SOCKET, which can be used
# by the Java and C preprocessors to conditionally compile code.
# Uncomment one of the following definitions:
#PLATFORM_TYPE=BARE_METAL
#PLATFORM_TYPE=DELEGATING
PLATFORM_TYPE=NATIVE
#PLATFORM_TYPE=SOCKET

-- Main.khumalo - 06 Oct 2008

Building Squawk

General

Building Squawk for Desktop

OnWindows

OnMac

OnLinux

Building Squawk for Devices

OnSPOT

Squawk Build Options

Squawk Builder Properties

• ASSERTIONS_ENABLED Enables use of com.sun.squawk.util.Assert (and defines Klass.ASSERTIONS_ENABLED)
• DEBUG_CODE_ENABLED Set true to enable miscellaneous debug code (and define Klass.DEBUG_CODE_ENABLED)
• FLOATS Floating point support. NOTE: FLOATS=false is currently broken due to phoneme code that we are inheriting
• FLASH_MEMORY This is a heavily overloaded flag that means "has flash memory", "runs on bare metal (no OS)", "run on SPOT"
• ENABLE_DYNAMIC_CLASSLOADING When false, can only load classes from suite. This should be false when FLASH_MEMORY is true
• ENABLE_SDA_DEBUGGER Enable JPDA debugger agent support. Most debugger code is in debugger module, but some support routines are in base Squawk.

Squawk Executable Build Options

• d build-options rom rom-options module more modules

The build-options primarily affect the C compilation of the system, except for the first two listed. Here is a list of commonly used build-options:

    -verbose            verbose builder output
    -Dname=value      sets a builder property
    -Xplat:name         the platform to cross-compile to. Platform drives default C compiler.
                        (default is host platform))
    -comp:name          the C compiler used to build native executables
                        Supported: 'msc', 'gcc' or 'cc' or 'gcc-macosx' (any
                        other value disables C compilaton)
    -nocomp             disables C compilation (but not C file preprocessing)
    -cflags:opts        extra C compiler options (e.g. '-cflags:-g')
    -o1                 optimize C compilation/linking for minimal size
    -o2                 optimize C compilation/linking for speed
    -o3                 optimize C compilation/linking for max speed
    -prod               build the production version of the VM
    -mac                build the interpreter loop using fast macros
    -tracing            enable tracing in the VM
    -profiling          enable profiling in the VM
    -assume             enable assertions in the VM

    -prod -mac -o2    

The rom-options affect the generation of the suite. The commonly used rom-options are:

    -metadata           create matching metadata suite
    -exclude:file       excludes classes that match the class names or packages
                        in file ('.exclude' is used implicitly)
    -strip:t            strip symbolic information according to :
                           'd' - debug: retain all symbolic info
                           'a' - application: discard all symbolic info
                           'l' - library (default): discard symbolic info
                                 for private/package-private fields and methods
                           'e' - extendable library: discard symbolic info
                                 for private fields and methods
    -lnt                retain line number tables
    -lvt                retain local variable tables
    -v                  verbose romizer output

A module is a directory that has a 'j2meclasses' subdirectory or a jar/zip file. More than one suite can be created by separating the modules for each suite with '--'.

-- Main.derek_white - 10 Jul 2008