Changes between Version 61 and Version 62 of BuildSystem


Ignore:
Timestamp:
12/15/12 16:59:11 (7 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildSystem

    v61 v62  
    126126 * `ant run` to compile and run the project 
    127127 
    128 == Creating your own Java project == 
     128== Creating your own project == 
    129129[=#directorylayout] 
    130130The build system assumes the following directory layout: 
    131131{{{ 
    132132yourproject/build.xml                 (ant build file) 
    133 yourproject/ivy.xml                   (specification of jar dependencies) 
     133yourproject/ivy.xml                   (specification of dependencies) 
    134134yourproject/build.properties          (build properties) 
    135135yourproject/src                       (source directory) 
    136136yourproject/generatedsrc              (source code generated by a source code generation tool (e.g. protoc)) 
    137 yourproject/lib                       (directory for resolved jars (auto filled, do not add custom jars here, nor commit to git)) 
    138 yourproject/lib.local directory       (directory for custom jars for your project) 
     137yourproject/lib                       (directory for resolved jars (auto filled, do not add custom libraries here, nor commit to git)) 
     138yourproject/lib.local directory       (directory for custom libraries for your project) 
    139139yourproject/resource                  (directory for data resources for your project) 
    140140yourproject/privateprops              (private properties for your project, e.g. selected main class, should not be committed to git) 
     
    144144yourproject/test/ivy.xml              (specification of test specific jar dependencies) 
    145145yourproject/test/src                  (test sources) 
    146 yourproject/test/lib                  (directory for resolved test jars (auto filled, do not add custom jars here)) 
     146yourproject/test/lib                  (directory for resolved test libraries (auto filled, do not add custom jars here)) 
    147147yourproject/test/resource             (test specific data) 
    148148}}} 
    149 To use the build system with your own Java project, you'll need to set up a build.xml, build.properties and ivy.xml file. The build.xml file provides the project name and normally simply refers to the default build.xml in hmibuild: 
     149To use the build system with your own project, you'll need to set up a build.xml, build.properties and ivy.xml file. The build.xml file provides the project name and normally simply refers to the default build.xml in hmibuild: 
    150150e.g.: 
    151151{{{ 
     
    189189The build.properties file specifies several build and run options. For example resource path and runtime arguments for the jvm: 
    190190{{{ 
     191language=java 
    191192resolve.status=beta 
    192193resource.path=${shared.resources}/DefaultShaders/resource;${shared.resources}/LogbackConfigs/resource;${shared.resources}/HmiHumanoidEmbodimentArmandia/resource; 
    193194run.jvmargs= -Xms128m -Xmx512m  -Xss5M -Dlogback.configurationFile=LogbackConfigs/warnlogstdout.xml 
    194195}}} 
     196 
     197Multiple programming languages are supported, including java, python, cpp (C++), scripts (simply releases everything in the scripts dir), none (for top-level projects that manage other projects using multiple programming language) and zipresource (for projects containing only data). 
    195198 
    196199== Use cases ==