db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Trivial Update of "RunningTheApacheDerbyTestSuiteOnPhoneMeAdvanced" by OleSolberg
Date Tue, 12 May 2009 13:05:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by OleSolberg:
http://wiki.apache.org/db-derby/RunningTheApacheDerbyTestSuiteOnPhoneMeAdvanced

------------------------------------------------------------------------------
  #format wiki
  #language en
  
- == Running the Apache Derby test suite on phoneME Advanced ==
+ = Running the Apache Derby test suite on phoneME Advanced =
  
  Since phoneME b96 (r17519) it is possible to run the Derby testsuite (....suites.All) on
the phoneME Advanced(aka cdc) virtual machine (cvm) for '''Linux X86''' without having to
locally modify the phoneME source or build script.
  
@@ -16, +16 @@

  
  The following describes how to build a variant of phoneME Advanced that is able to run the
Derby testsuite (....suites.All).
  
- === Download phoneME Advanced ===
+ == Download phoneME Advanced ==
  Create a directory to hold the PhoneME Advanced source:{{{
    PHONE_ME_SRC=${SOME_WHERE}/phoneme-advanced # your choice...
    mkdir -p ${PHONE_ME_SRC}
@@ -30, +30 @@

  The following is not required for doing the build.{{{
    svn checkout https://phoneme.dev.java.net/svn/phoneme/trunk phoneme --username <your
java.net user name> }}}
  
- === Build phoneME Advanced ===
+ == Build phoneME Advanced ==
  {{{
    cd ${PHONE_ME_SRC}/cdc/build/linux-x86-generic/}}}
  
@@ -44, +44 @@

    MK_WITHOUT_JSR169="JDK_HOME=${SDK14_HOME}/ CVM_JAVA_TOOLS_PREFIX=${SDK14_HOME}/bin/ CVM_JIT=false
CVM_MP_SAFE=false J2ME_CLASSLIB=foundation ${SETAFFINITY}" }}}
  In this case you will have to run {{{cvm}}} with {{{"-Xbootclasspath/a:..../jsr169.jar"}}}
for a pre-built {{{jsr169}}}.
  
- ==== Build plain phoneME Advanced ====
+ === Build plain phoneME Advanced ===
  Then build ''without including'' jsr169:{{{
    echo ${MK_WITHOUT_JSR169}
    make ${MK_WITHOUT_JSR169} clean
@@ -54, +54 @@

  The {{{cvm}}} virtual machine is then located in{{{
    CVM=${PHONE_ME_SRC}/cdc/build/linux-x86-generic/bin/cvm}}}
  
- ==== Build phoneME with jsr169 included ====
+ === Build phoneME with jsr169 included ===
  Alternatively, if you want to build ''with'' {{{jsr169}}} included, add this:{{{
    JSR169=${SOME_WHERE}/jsr169 # Where you have downloaded JSR169...
    MK_WITH_JSR169="${MK_WITHOUT_JSR169} USE_JDBC=true JDBC_DIR=${JSR169}/jdbc_cdc1.0/cdcfoundation"}}}
@@ -72, +72 @@

  The {{{cvm}}} virtual machine is still located in {{{
    CVM=${PHONE_ME_SRC}/cdc/build/linux-x86-generic/bin/cvm}}}
  
- === Testing the build ===
+ == Testing the build ==
  Show which options was used when building {{{cvm}}}: {{{
    ${CVM} -XshowBuildOptions}}}
  
@@ -81, +81 @@

  
  Observe that to run Derby on phoneME Advanced / {{{cvm}}}, Derby must be built with Foundation
Profile 1.1. See A.2.
  
- ==== Testing Derby on the build ====
+ === Testing Derby on the build ===
  For initial testing of Derby on {{{cvm}}} do:
  Specify where your Derby jars are located, e.g. {{{
    DERBY_JARS=${SOME_WHERE}/Apache/Derby/trunk/jars/insane}}}
@@ -96, +96 @@

    JDBCOp=jsr169
    ${CVM} -Xbootclasspath/a:${JSR169_CLASSES}/${JDBCOp}.jar -jar ${DERBY_JARS}/derbyrun.jar
sysinfo}}}
  
- === Running the Apache Derby test suite on the build ===
+ == Running the Apache Derby test suite on the build ==
  You should now be ready to run the Derby test suite(s) on {{{cvm}}}:
  If you are running without {{{jsr169}}} built into {{{cvm}}} set {{{
    BOOTCP="-Xbootclasspath/a:${JSR169_CLASSES}/${JDBCOp}.jar"}}}

Mime
View raw message