Lines Matching refs:files

14     * Input files description & format
107 Emugen input files - protocol specification
109 The protocol generated by emugen consists of two input files:
113 from c/c++ header files or similar.
116 the files that are generated for this protocol.  A line in the .in
140 This files describes the types that are described by the API. A type
156 Encoder generated code files 
158 In order to generate the encoder files, one should run the ‘emugen’
161 emugen -i <input directory> -E <encoder files output directory> <basename>
163 	<input directory> containes the api specification files  (basename.in + basename.attrib)
164 	<encoder directory> - a directory name to generate the encoder output files
167 Assuming the basename is ‘api’, The following files are generated:
196 Decoder generated files
198 In order to generate the decoder files, one should run the ‘emugen’
200 emugen -i <input directory> -D <decoder files output directory> basename
202 	<input directory> containes the api specification files  (basename.in + basename.attrib)
203 	<decoder directory> - a directory name to generate the decoder output files
207 files:
224 Wrapper generated files
226 In order to generate a wrapper library files, one should run the
229 emugen -i <input directory> -W <wrapper files output directory> basename
231 	<input directory> containes the api specification files  (basename.in + basename.attrib)
232 	<wrapper directory> - a directory name to generate the wrapper output files
236 files: