![]() Shorthand for 0-dim host mdarray (scalar). Using raft :: host_scalar = host_mdarray > # Using raft :: host_vector = host_mdarray, LayoutPolicy > # Using raft :: host_matrix = host_mdarray, LayoutPolicy > # Handle – raft handle for managing expensive cuda resourcesĪuto raft :: make_device_scalar ( raft :: resources const & handle, ElementType const & v ) #Ĭreate a device scalar from v. N_cols – number of columns in matrixĪuto raft :: make_device_vector ( raft :: resources const & handle, IndexType n ) #Ĭreate a 1-dim device mdarray. Handle – raft handle for managing expensive resources Template Parameters :ĮlementType – the data type of the scalar elementĪuto raft :: make_device_matrix ( raft :: resources const & handle, IndexType n_rows, IndexType n_cols ) #Ĭreate a 2-dim c-contiguous device mdarray. Using raft :: device_scalar = device_mdarray > # Template Parameters :ĮlementType – the data type of the vector elements Using raft :: device_vector = device_mdarray, LayoutPolicy > # LayoutPolicy – policy for strides and layout ordering The statements in the file are case-sensitive. The file may contain tabs and newlines for formatting purposes. IndexType – the index type of the extents Configuration Format A configuration file is a free-form ASCII text file with a structure that is similar to that of a Makefile, with the default name Doxyfile. Template Parameters :ĮlementType – the data type of the matrix elements Shorthand for c-contiguous device matrix. ![]() Using raft :: device_matrix = device_mdarray, LayoutPolicy > # LayoutPolicy – policy for indexing strides and layout orderingĬontainerPolicy – storage and accessor policy Mdarray with device container policy Template Parameters :ĮlementType – the data type of the elements Using raft :: device_mdarray = mdarray > # # DoxygenLayout.Doxygenstruct: Cannot find class “raft::is_array_interface” in doxygen xml output for project “RAFT” from directory. # Note that if you run doxygen from a directory containing a file called # will be used as the name of the layout file. # optionally specify a file name after the option, if omitted DoxygenLayout.xml # that represents doxygen's defaults, run doxygen with the -l option. # output files in an output format independent way. The layout file controls the global structure of the generated The documentation for the layoutfile implies that it should work independently from the used output: # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed This works perfectly fine for chm and html output, but unfortunatly seems to be completely ignored for the latex and docbook output, which could be used to generate pdf. The layout definition looks pretty much like in this simplified example: In other words, we completely disable the standard structure and define our own. Second comes the API documentation, which is structured into the different languages. ![]() Languages, we call this part "user manual". First come a few pages of descriptive text, that applies to all.In order to achieve this we customized the document structure using a DoxygenLayout.xml file in the following way: We want to document all these languages in one single document, but structure it by language. We are using doxygen to generate sourcecode documentation for a C API, which is also wrapped using C++, C# and Java. If this is by design, is there any other way I could go starting from doxygen, resulting in a customized pdf document? Here are the details: My primary question is, is this restriction by design or am i missing something? I'm already doing this for html and chm output, but for pdf it does not work. I'm trying to customize the pdf document structure generated by doxygen. Before I'm going into the details, short brief first:
0 Comments
Leave a Reply. |