| 361 |
dpurdie |
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
2 |
<html>
|
|
|
3 |
|
|
|
4 |
<head>
|
|
|
5 |
<title>Welcome to JATS</title>
|
|
|
6 |
<link rel="stylesheet" href="Jats.css" type="text/css" />
|
|
|
7 |
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
|
|
8 |
</head>
|
|
|
9 |
|
|
|
10 |
|
|
|
11 |
<body>
|
|
|
12 |
<h1>Welcome to JATS</h1>
|
|
|
13 |
<h2>Purpose</h2>
|
|
|
14 |
|
|
|
15 |
The purpose of this WEB page-set is to provide a WEB
|
|
|
16 |
based document of the the Utilities provided by JATS.
|
|
|
17 |
|
|
|
18 |
The information provided in these pages is available
|
|
|
19 |
through the JATS command line help system. The web
|
|
|
20 |
version may provide an easier reference to the JATS
|
|
|
21 |
Utility Documentation.
|
|
|
22 |
|
|
|
23 |
<h2>Scope</h2>
|
|
|
24 |
The scope of this WEB is the Command Line Utilities that
|
|
|
25 |
are provided with JATS.
|
|
|
26 |
|
|
|
27 |
Specifically this documentation set does not document
|
|
|
28 |
the 'build' and 'make' directives that are the heart of
|
|
|
29 |
the JATS build system. These are provided in "MASS-00166
|
|
|
30 |
JATS Reference Manual".
|
|
|
31 |
|
|
|
32 |
<h2>Overview</h2>
|
| 5710 |
dpurdie |
33 |
JATS is the name of the VIX build tool. It is
|
| 361 |
dpurdie |
34 |
instantiated as a command line program, which is really
|
|
|
35 |
a wrapper for a collection of tools and utilities. JATS
|
|
|
36 |
can be used to:
|
|
|
37 |
|
|
|
38 |
<ul>
|
|
|
39 |
<li>Extract files from Version Control
|
|
|
40 |
<li>Build a package
|
|
|
41 |
<li>Place a label on Files under version control
|
|
|
42 |
<li>Transfer the build artifacts into the package repository
|
| 5710 |
dpurdie |
43 |
<li>General support the VIX Software Development Process
|
| 361 |
dpurdie |
44 |
</ul>
|
|
|
45 |
|
|
|
46 |
JATS is machine agnostic. It should work the same on Windows, Solaris and Linux.
|
|
|
47 |
|
|
|
48 |
JATS is a build system with the following goals:
|
|
|
49 |
<ul>
|
|
|
50 |
<li> Simplify the specification of the build system<br>The
|
|
|
51 |
mechanism by with the user specifies the build
|
|
|
52 |
requirements should be described in a high-level
|
|
|
53 |
language that is simple to read. Instead of writing
|
|
|
54 |
makefiles manually, the programmer populates a template
|
|
|
55 |
and lets the build system setup the environment,
|
|
|
56 |
generate the makefile and build the application
|
|
|
57 |
automatically
|
|
|
58 |
|
|
|
59 |
<li> Decouple the build specification from the
|
|
|
60 |
implementation.
|
|
|
61 |
<br>The build specification should not be
|
|
|
62 |
cluttered with the details of the build process. The
|
|
|
63 |
user specifies that a library is created from a set of
|
|
|
64 |
source files without the need for knowing how this
|
|
|
65 |
operation occurs.
|
|
|
66 |
|
|
|
67 |
<li> Multi platform support
|
|
|
68 |
<br>Builds can be supported on multiple platforms.
|
|
|
69 |
<br>Some components may need to be produced for
|
|
|
70 |
Solaris, Windows and various embedded environments.
|
|
|
71 |
|
|
|
72 |
<li> Multi compiler support
|
|
|
73 |
In an embedded environment, many target compilers will
|
|
|
74 |
need to be supported. This process should be abstracted
|
|
|
75 |
such that the user does not need to know the details of
|
|
|
76 |
the operation.
|
|
|
77 |
|
|
|
78 |
<li>Simplify the development process
|
|
|
79 |
|
|
|
80 |
<li>Uniform build mechanism that allows a package to be
|
|
|
81 |
built without any specialised knowledge. This allows:
|
|
|
82 |
<ul>
|
|
|
83 |
|
|
|
84 |
<li>Any developer to pick up and build any component.
|
|
|
85 |
|
|
|
86 |
<li>Automation of the build process.
|
|
|
87 |
</ul>
|
|
|
88 |
|
|
|
89 |
</ul>
|
|
|
90 |
|
|
|
91 |
<h2>References</h2>
|
|
|
92 |
The following materials are to be used in conjunction with or are referenced by this document.
|
| 373 |
dpurdie |
93 |
|
|
|
94 |
<br>
|
| 361 |
dpurdie |
95 |
<ul>
|
| 373 |
dpurdie |
96 |
<li>Reference
|
|
|
97 |
<ul>
|
|
|
98 |
<li> MASS-00166 JATS Reference Manual
|
|
|
99 |
<li> MASS-00164 Installing and Using JATS
|
|
|
100 |
<li> MASS-00165 JATS configuration files
|
|
|
101 |
<li> DPG-00397 Building and Releasing Packages with JATS
|
|
|
102 |
<li> MASS-00113 Deploylib Reference Manual
|
|
|
103 |
<li> TECHGP-00181 ANT Build Environment
|
| 361 |
dpurdie |
104 |
</ul>
|
| 373 |
dpurdie |
105 |
<li>Tutorials
|
|
|
106 |
<ul>
|
| 1447 |
dpurdie |
107 |
<li> Clearcase
|
| 373 |
dpurdie |
108 |
<li> MASS-00230 Basic JATS Tutorial
|
|
|
109 |
<li> TECHGP-00259 Basic JATS Tutorial with SVN
|
|
|
110 |
<li> MASS-00231 Basic JATS Development Environment Tutorial
|
| 1447 |
dpurdie |
111 |
<li> Subversion
|
|
|
112 |
<li> TECHGP-00259 Basic JATS Tutorial with Subversion
|
|
|
113 |
<li> TECHGP-00289 Basic JATS Development Environment Tutorial with Subversion
|
|
|
114 |
<li> TECHGP-00290 Branching and Merging with Subversion Tutorial
|
|
|
115 |
<li> General
|
| 373 |
dpurdie |
116 |
<li> MASS-00196 Jats sandbox - Multi Package Development Tutorial
|
| 1447 |
dpurdie |
117 |
|
| 373 |
dpurdie |
118 |
</ul>
|
|
|
119 |
<li>Misc
|
|
|
120 |
<ul>
|
|
|
121 |
<li> MASS-00099 Generating MUG files with JATS
|
|
|
122 |
<li> MASS-00232 Format of the Linux App Upgrade Manifest File
|
|
|
123 |
<li> MASS-00246 Creating a Debian Package
|
|
|
124 |
<li> TECHGP-00180 Metrics gathering within the Build Environment
|
| 5710 |
dpurdie |
125 |
<li> TECHGP-00210 VIX Software Build Overview
|
| 373 |
dpurdie |
126 |
<li> TECHGP-00250 Subversion support within JATS
|
| 1447 |
dpurdie |
127 |
<li> TECHGP-00291 Subversion Best Practices
|
|
|
128 |
<li> TECHGP-00299 TechNote - Changes to the use of Subversion
|
| 373 |
dpurdie |
129 |
<li> TECHGP-00253 Creating NSIS Based Windows Installers
|
|
|
130 |
<li> TECHGP-00254 Jats Integration of ZendGuard
|
|
|
131 |
<li> TECHGP-00255 Building Visual Studio Solutions with JATS
|
|
|
132 |
</ul>
|
|
|
133 |
</ul>
|
| 361 |
dpurdie |
134 |
</body>
|
|
|
135 |
</html>
|