Output File Naming Conventions
In the compact mode, the name of the CAP file, export file, and the Java Card
Assembly file must be the last portion of the package name followed by the
extensions.cap
, .exp
, and .jca
,
respectively. In the extended mode, the name of the CAP file is the value of the
CAP_name
field defined in the JSON configuration file followed by
the .cap
extension. For the export files and Java Card Assembly files
generated in this mode, the same rules as in the compact mode apply.
By default, the files output from the Converter are written to a directory called
javacard
. This is a subdirectory of the input package's directory
for the compact mode, or a subdirectory of the CAP name directory for the extended
mode.
In the above -classdir
example, by default, the output files are written
to the directory
[ /home/mywork/java/lang/javacard |
C:\mywork\java\lang\javacard ]
In the above baseDir
example, assume that if the
CAP_name
field has the "hellosample" value, by default, the
output files are written to the directory [
/home/mywork/hellosample/javacard |
C:\mywork\hellosample\javacard ]
.
The -d
flag or the outputDir
field enable you to specify a different root directory for the output.
In the above example, if you use the -d
flag or the
outputDir
field to specify the root directory for the output to be
[/home/myoutput | C:\myoutput ]
, the Converter
writes the output files to the directory
[/home/myoutput/java/lang/javacard |
C:\myoutput\java\lang\javacard ]
or
[/home/myoutput/hellosample/javacard |
C:\myoutput\hellosample\javacard ]
, respectively.
When generating a CAP file, the Converter creates one or more Java Card Assembly files in the output directory as an intermediate result. If you don't want a Java Card Assembly file to be produced, omit the option -out JCA
in the compact mode or set the JCA field to false
for the respective package in the JSON configuration file in the extended mode. The Converter deletes the Java Card Assembly files at the end of the conversion.