On this page:
slice2cpp Command-Line Options
The Slice-to-C++ compiler,
slice2cpp, offers the following command-line options in addition to the standard options.
Changes the file extension for the generated header files from the default
h to the extension specified by
You can also change the header file extension with a global metadata directive:
Only one such directive can appear in each source file. If you specify a header extension on both the command line and with a metadata directive, the metadata directive takes precedence. This ensures that included Slice files that were compiled separately get the correct header extension (provided that the included Slice files contain a corresponding metadata directive). For example:
Compiling this file with
example.hpp, but the
#include directive in that file is for
BuiltinSequences.ice contains the metadata directive
You normally will not need to use this metadata directive. The directive is necessary only if:
#includea Slice file in one of your own Slice files.
- The included Slice file is part of a library you link against.
- The library ships with the included Slice file's header.
- The library header uses a different header extension than your own code.
For example, if the library uses
.hpp as the header extension, but your own code uses
.h, the library's Slice file should contain a
[["cpp:header?ext:hpp"]] directive. (If the directive is missing, you can add it to the library's Slice file.)
Changes the file extension for the generated source files from the default
cpp to the extension specified by
This option adds an include directive for the specified header at the beginning of the generated source file (preceding any other include directives). If
GUARD is specified, the include directive is protected by the specified guard. For example,
--add-header precompiled.h,__PRECOMPILED_H__ results in the following directives at the beginning of the generated source file:
The option can be repeated to create include directives for several files.
As suggested by the preceding example, this option is useful mainly to integrate the generated code with a compiler's precompiled header mechanism.
#include directives in source files to prepend the path name of each header file with the directory
Generate sample implementation files for the C++11 mapping. This option will not overwrite an existing file.
Generate sample implementation files for the C++98 mapping. This option will not overwrite an existing file.
Generate checksums for Slice definitions.
#include directives generated by the Slice-to-C++ compiler can be a source of confusion if the semantics governing their generation are not well-understood. The generation of
#include directives is influenced by the command-line options
--include-dir; these options are discussed in more detail below. The
--output-dir option directs the translator to place all generated files in a particular directory, but has no impact on the contents of the generated code.
Given that the
#include directives in header files and source files are generated using different semantics, we describe them in separate sections.
In most cases, the compiler generates the appropriate
#include directives by default. As an example, suppose file
B.ice using the following statement:
Assuming both files are in the current working directory, we run the compiler as shown below:
The generated file
A.h contains this
If the proper include paths are specified to the C++ compiler, everything should compile correctly.
Similarly, consider the common case where
B.ice from a subdirectory:
Assuming both files are in the
inc subdirectory, we run the compiler as shown below:
The default output of the compiler produces this
#include directive in
Again, it is the user's responsibility to ensure that the C++ compiler is configured to find
inc/B.h during compilation.
Now let us consider a more complex example, in which we do not want the
#include directive in the header file to match that of the Slice file. This can be necessary when the organizational structure of the Slice files does not match the application's C++ code. In such a case, the user may need to relocate the generated files from the directory in which they were created, and the
#include directives must be aligned with the new structure.
For example, let us assume that
B.ice is located in the subdirectory
However, we do not want the
slice subdirectory to appear in the
#include directive generated in the header file, therefore we specify the additional compiler option
The generated code demonstrates the impact of this extra option:
As you can see, the
#include directives generated in header files are affected by the include paths that you specify when running the compiler. Specifically, the include paths are used to abbreviate the path name in generated
When translating an
#include directive from a Slice file to a header file, the compiler compares each of the include paths against the path of the included file. If an include path matches the leading portion of the included file, the compiler removes that leading portion when generating the
#include directive in the header file. If more than one include path matches, the compiler selects the one that results in the shortest path for the included file.
For example, suppose we had used the following options when compiling
In this case, the compiler compares all of the include paths against the included file
slice/inc/B.ice and generates the following directive:
-Islice/inc produces the shortest result, therefore the default path for the included file (
slice/inc/B.h) is replaced with
In general, the
-I option plays two roles: it enables the preprocessor to locate included Slice files, and it provides you with a certain amount of control over the generated
#include directives. In the last example above, the preprocessor locates
slice/inc/B.ice using the include path specified by the
-I. option. The remaining
-I options do not help the preprocessor locate included files; they are simply hints to the compiler.
Finally, we recommend using caution when specifying include paths. If the preprocessor is able to locate an included file via multiple include paths, it always uses the first include path that successfully locates the file. If you intend to modify the generated
#include directives by specifying extra
-I options, you must ensure that your include path hints match the include path selected by the preprocessor to locate the included file. As a general rule, you should avoid specifying include paths that enable the preprocessor to locate a file in multiple ways.
By default, the compiler generates
#include directives in source files using only the base name of the included file. This behavior is usually appropriate when the source file and header file reside in the same directory.
For example, suppose
B.ice from a subdirectory, as shown in the following snippet of
We generate the source file using this command:
Upon examination, we see that the source file contains the following
However, suppose that we wish to enforce a particular standard for generated
#include directives so that they are compatible with our C++ compiler's existing include path settings. In this case, we use the
--include-dir option to modify the generated code. For example, consider the compiler command shown below:
The source file now contains the following
Any leading path in the included file is discarded as usual, and the value of the
--include-dir option is prepended.