$(blockpoint)
The $(blockpoint) command manages user-added code by extracting or injecting code between BLOCK and POINT tags in a generated file.
Syntax
$(blockpoint) [arguments] <source_input_files>
- arguments are described in Table 1.
- filename is the generated file(s) separated by a space.
Arguments
Argument | Description |
---|---|
-extract |
Extracts the user code from the input file (the difference between filename and the generated part of the filename.code file. |
-inject |
Inject the diff part of filename.code in the filename. |
-commentStart |
Start block comment syntax. For
example, */ for C language. |
-commentStart2 |
Line comment syntax. For example,
*/ for C language. |
-commentEnd |
End block comment syntax. For
example, */ for C language. |
-code [.code file
path] |
User-modified code file path;
specifies the name of the .code file. If there is only one generated
source file , the .code file uses (by default) the same name as the
input file, otherwise -code is mandatory. |
-line |
Line number (integer) of the codefile tag in the generated source file. |
-storeGenerated |
Flag to update the code file (inject only). |
Usage
The $(blockpoint) command is used in build rules for generated
programs. Predefined node variables can be used in the
command.
$(blockpoint) -code "$(InputDir)/$(InputBaseName).code"
-extract "$(InputDir)/$(InputBaseName).java"
$(blockpoint) -storeGenerated -code "$(InputDir)/$(InputBaseName).code"
-inject "$(InputDir)/$(InputBaseName).java"