https://deepjava.org/ 2026-04-10T15:56:33+00:00 https://deepjava.org/ https://deepjava.org/lib/tpl/deepjava-tpl/images/favicon.ico text/html 2016-02-25T13:33:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/configuration_syntax?rev=1456403585&do=diff Syntax for Configuration Files Config = MetaBlock { ConstantsBlock | MemoryMapBlock | RegisterMapBlock | TargetConfigurationBlock | RegInitBlock | ProjectBlock | OperatingSystemBlock | SysConstBlock } . MetaBlock = "meta" "{" VersionAssigment FileDescAssigment [ImportAssigment] "}" . ConstantsBlock = "constants" "{" {VarAssigment} "}" . MemoryMapBlock … text/html 2022-11-15T13:46:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/configuration?rev=1668516405&do=diff Configuration CPUs, boards, programmers and runtime systems are described by configuration files. These files must be put into the directory config in the target library. Within config there are 5 subdirectories: base, arch, cpus, boards, operatingsystems text/html 2022-12-20T15:54:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/eclipse_debugger?rev=1671548082&do=diff Deep Eclipse Debugger FIXME Translate, upgrade to version 1.0 Der Debugger wurde als eigenständiges Plugin implementiert, welches das Deep Plugin verwendet. Es wurde darauf geachtet, keine Abhängigkeiten zur Hardware einzubauen. Die Implementierungen der einzelnen Komponenten sind im Package org.deepjava.debug.eclipse untergebracht. Einzige Ausnahmen sind die Dateien MANIFEST.MF welche im Ordner META-INF ist, plugin.xml und build.properties. Diese müssen auf der obersten Ebene sein. text/html 2022-12-20T15:54:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/eclipse_integration?rev=1671548052&do=diff Eclipse Integration The project deep contains an integration into eclipse as plugin. Though the compiler and linker are not dependent on eclipse and can run standalone, see Launcher. All configuration details are given in the configuration files (see Configuration). These files must be parsed for the various eclipse wizards and dialogues and changes must be stored back to those files. It is possible to work without eclipse at all. text/html 2022-12-20T15:53:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/file_formats?rev=1671548023&do=diff deep File Formats We translate all necessary Classfiles directly into executable target code. There is no need for object files. However, we use files to specify the target configuration (Configuration), to run target commands (Target Commands) and for the target image. All file formats start with a 8 byte keyword. text/html 2022-12-20T11:26:19+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/hstring?rev=1671531979&do=diff HString deep was developed with efficiency and speed in mind. String handling in Java is not very efficient. However, strings are widely used in a compiler. Therefore, we don't use regular Java strings (java.lang.String) but implement an more efficient version ( text/html 2022-02-24T13:34:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/installation_for_developers?rev=1645706082&do=diff Installation for Developers Setup the development environment according to the following steps. * Make sure you have the JDK and eclipse installed as described in Download and Installation. eclipse must have plug-in development environment (PDE) installed. * Checkout from GIT repositories from text/html 2022-11-16T11:40:22+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/launcher?rev=1668595222&do=diff Launcher Launching is done in two steps. The first step starts launching with three different options, while the second step comprises the the actual launcher. * Step * Eclipse Launcher: In Eclipse it possible to define run configurations and perform a run. This event is handled by the text/html 2022-12-20T11:29:18+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/logging?rev=1671532158&do=diff Logging and Error Reporting Logging The class StdStreams in the package org.deepjava.host defines three output streams. * log: is used for normal logging (e.g. successful compilation) * vrb: for debugging purposes * err: for errors Assertions text/html 2022-12-20T11:30:23+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/start?rev=1671532223&do=diff Project deep Under the name of deep a cross development platform for Java was created. The project was initiated and is maintained by the Institut for Computer Science at the Eastern Switzerland University of Applied Sciences, OST, Buchs, Switzerland. text/html 2022-08-22T11:33:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://deepjava.org/dev/zynq7000pl?rev=1661160787&do=diff PL Configuration on the Zynq7000 * Use Xilinx Vivado to create a new configuration for the programmable logic part of the Zynq7000 (PL) according to <https://flink-project.ch/flink_vhdl#building>. Result is a bit-file, e.g. flink2.bit. * Using Vivado, create a new Zynq7000 project following the instructions in