Changes between Version 35 and Version 36 of Developer/Projects/Open/TraceTool

Timestamp:

08/10/09 17:46:10 (15 years ago)

Author:

Cocanlucian

Comment:

Developer/Projects/Open/TraceTool

@@ -17 +17 @@
          ./rtems_trace.py --mode=generate --genpath=path to where the wrapping code should be saved
 
-Using this mode the user will generate the wrapping code which is a set of files corresponding to the functions that he specified in the configuration file.
-If the --mode option it's not specified then the default mode chosen by the tool will be ''generate''. So if the user wants to generate and save the wrapping code in a directory named "wrappers" from the current working directory (cwd) which is the default path, the user can simply do this:
+Using this mode the user will generate the wrapping code, which is a set of files corresponding to the functions that he specified in the configuration file. If the --mode option it's not specified then the default mode chosen by the tool will be ''generate''. So if the user wants to generate and save the wrapping code in a directory named ''wrappers'' from the current working directory (cwd) which is the default path, then he can simply do this:
 
    ./rtems_trace.py 
+= Compile mode =
 
- *  compile mode
- *  link mode
- *  decode mode 
+  
+   Usage: ./rtems_trace.py -m compile -i name of the compiler -g path to the wrapping code 
+                           -o path to where the compiled wrapping code should be saved
+                           -l path to where the RTEMS libraries were installed
+          ./rtems_trace.py --mode=compile --compiler=name of the compiler  
+                           --genpath=path to the wrapping code
+                           --objpath=path to where the compiled wrapping code should be saved
+
+Using this mode the user can compile all the .c files from a directory (usually the .c files from the wrapping code directory) and save the resulted files (.o files) in the directory specified by the -o option. If the -g and -o options are not specified then the rtems_trace tool will look in the ''wrappers'' directory located in cwd and save the .o files in a directory named ''objects'' also from cwd. Also, if the -l option it's not specified than the tool will choose this path by default: ''/opt/rtems-4.10/i386-rtems4.10/pc386/lib/''
+
+   ./rtems_trace.py --mode=compile --compiler=i386-rtems4.10-gcc
+
+will compile all the .c files from the cwd/wrappers using the gcc compiler for the i386 BSP and the 4.10 rtems version. The .o files will be saved in cwd/objects.
+= Link mode =
+= Decode mode =
+
 = Configuration files =