A
andrew.may
Guest
Peter, We have (source-project == OEA-project) i.e. a single project in source control is a single project in OEA/PDSOE A typical OE project might look like Project Root src directory bin directory resources directory build.files directory wrk directory lib directory RunConfigurations directory build.xml file ivy.xml file build.properties file project-specific.ini file Where the directories are used as follows: src is the source folder bin is where the .r code is put when built by PDSOE/OEA resources is where we put files that need to be distributed with the built project (e.g. icon files) build.files is where we put files that are used by the build script (& the build artifacts are put in a subdir of this) wrk is used as the working directory when running the project (to keep it tidy) lib is where Ivy will put any dependencies that it pulls in (e.g. pre-built .pl files of library projects) RunConfigurations is where we put the PDSOE/OEA .launch files that we use to run the project's application(s) And the magic files are: build.xml - Ant build script ivy.xml - Details of Ivy dependencies build.properties - properties used by build.xml project-specific.ini - used when running & building the project (e,g, to ensure that fonts/colours are standardised) Of the directories: the bin, lib & wrk folders (& their contents) are excluded from source control as they are generated by the build script or at runtime. The src folder is the only folder that PDSOE/OEA has marked as a "source" folder & it is set to compile into bin All the files I mentioned are in source control Some of this is fairly arbitrary, but it has been very popular with Devs, as they can just pull a project & instantly start working on it without any manual setup.
Continue reading...
Continue reading...