deep

a Cross Development Platform for Java

User Tools

Site Tools


dev:configuration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dev:configuration [2016/02/25 13:33] – created - external edit 127.0.0.1dev:configuration [2022/11/15 13:46] (current) – [Build] ursgraf
Line 99: Line 99:
 When eclipse is used part of the configuration must be read already when a new project is created or of projects properties are changed. This is for the wizards to be able to list the various options in the combo boxes. When eclipse is used part of the configuration must be read already when a new project is created or of projects properties are changed. This is for the wizards to be able to list the various options in the combo boxes.
 \\ \\ \\ \\
-Part of the configuration is used by the kernel in the runtime system. This information has to go into several interface classes. If the configuration changes in this respect you have to newly create those interface files with <code Java>public static void createInterfaceFiles(String libraryPath)</code>. The following files are created:+Part of the configuration is used by the kernel in the runtime system. This information has to go into several interface classes. If the configuration changes in this respect you have to newly create those interface files with <code Java>public static void createInterfaceFiles(String libraryPath)</code> 
 + 
 +You can call the TestLauncher with the option //--interface-files-path//, see [[dev:launcher#TestLauncher|TestLauncher]]. 
 +The following files are created:
   * IdeepCompilerConstants (for system constants)   * IdeepCompilerConstants (for system constants)
   * Architecture specific interface files, e.g. Ippc32. The actual architecture (defined in the actual project) will be taken.   * Architecture specific interface files, e.g. Ippc32. The actual architecture (defined in the actual project) will be taken.
   * Board specific interface file (system constants of the board and the CPU, registers of the CPU), e.g. IntbMpc555HB. The actual board (defined in the actual project) will be taken.   * Board specific interface file (system constants of the board and the CPU, registers of the CPU), e.g. IntbMpc555HB. The actual board (defined in the actual project) will be taken.
 For changes in the configuration all this interface files might change as well and should be rebuilded before the runtime system can be used together with the new configuration. For changes in the configuration all this interface files might change as well and should be rebuilded before the runtime system can be used together with the new configuration.
dev/configuration.1456403585.txt.gz · Last modified: 2016/02/25 13:33 by 127.0.0.1