The 'Build' page enables you to enter commands to build your project. You can use Enterprise Architect Local Paths and environment variables in composing your command line(s). You can choose to create your own build script, entering various shell commands. You can also choose to simply run an external program or batch file such as an Ant script.
On the Execution Analyzer window, either:
- Locate and double-click on the required script and select the 'Build > Build' page or
- Click on in the window Toolbar, select the Package in which to create a new script, and select the 'Build > Build' page
Develop > Source Code > Execution Analyzer > Edit Analyzer Scripts
Execute > Tools > Analyzer
Analyzer Context Menu
Write your script in this text box, using the windows shell commands; the format and content of this section depends on the actual compiler you use to build your project. If the path or arguments contain spaces, surround them with quotes; for example: "c:\program files (x86)\java\bin\javac.exe".
Here are some examples:
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com" /Rebuild Debug RentalSystem.sln
Visual Studio using a Local Path:
"%VsCompPath%\devenv.exe" /build Debug Subway.sln
C:\Program Files (x86)\Java\jdk1.6.0_22\bin\javac.exe" -g -cp "%classpath%;." %r*.java
Java using a Local Path:
"%JAVA%\bin\javac.exe" -g -cp "%classpath%;." %r*.java
Wildcard Java Builds (%r) - Source files in sub-folders can be built using the %r token. The token has the effect of causing a recursive execution of the same command on any files in all sub-folders, as shown in the example.
Execute Command as
Click on the drop down arrow and select the mode of executing the script:
- Batch File - Use this option to execute a shell script in a system command window; environment variables can be accessed by commands in this script
- Process - Use this option to execute the command as a single program; the command should specify the path to the program, plus any command line arguments
Browse for or type in the default directory path in which the build script process will run.
Click on the drop-down arrow and select a method for automatically parsing the compiler output.
If you select this option, output from the script is logged in the System Output window; Enterprise Architect parses the output according to the syntax you specify.
Type in the ID of the remote host system and its port; for example, mypc01:7777.
If you set this property to #SYSTEMHOST#, the script is sent to the Windows Satellite Service when running on Windows, and the Linux Satellite Service when running under Wine. The service IDs and Ports are defined in the 'Private Options - Services' section of the Analyzer Scripts Editor.
Deploy after Build
Check this box to cause the Deploy script to be executed immediately after this Build script completes.
To execute the Build script, click on the Package in the Browser window and either:
- Right-click on any Toolbar and select 'Analyzer Toolbars | Build', or
- Press or
- Select the 'Execute > Source > Build > Build' ribbon option