Multi-platform development
with CDT
Graeme Johnson (IBM Ottawa Lab)
Gabriel Gastro (IBM Ottawa Lab)
© 2007 by «Author»; made available under the EPL v1.0 | Date | Other Information, if necessary

J9 == IBM’s Java Virtual Machine
J9 everywhere
●
Runs on phones & mainframes ...
●
50+ configurations in between …
●
More platforms than people …
●
One code-base …
●
Write-once … runs everywhere …
●
Write-once … breaks everything …
●
Sanity == Tooling + Automation
2 Multi-platform development with CDT | © 2007 by Graeme Johnson & Gabriel Castro; made available under the EPL v1.0

J9: Some assembly required !=
 3 million LOC is too big for a single CDT project.
 Split by component into 30+ projects.
●
examples: GC, JIT, Harmony Support.
 Team project sets make loading easy. 
 Multi-platform source confuses CDT indexer. 
●
Both paths of conditional compilation are ‘live’.
●
Cannot define a single set of include paths / #defines.
●
Not perfect, but CDT is pretty resilient.
3 Multi-platform development with CDT | © 2007 by Graeme Johnson & Gabriel Castro; made available under the EPL v1.0

J9DT: Recipe for VM Construction !=
 Each J9 configuration is an xml file that specifies:
●
flags: compile-time settings that control code shape. (#ifdef)
●
components: a list of CDT projects to include.
 J9DT provides configuration editors & specialized builders.
4 Multi-platform development with CDT | © 2007 by Graeme Johnson & Gabriel Castro; made available under the EPL v1.0

We stop here Upload (ftp/scp/sftp)
today
J9DT in a nutshell
Configuration 1
change update
…
Compile (ssh)
workspace == master source
Configuration n
Test (ssh)
analyze output
Create Warning/Error Markers
5 Multi-platform development with CDT | © 2007 by Graeme Johnson & Gabriel Castro; made available under the EPL v1.0