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


Ignore:
Timestamp:
Aug 10, 2009, 5:46:10 PM (10 years ago)
Author:
Cocanlucian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/TraceTool

    v35 v36  
    1717         ./rtems_trace.py --mode=generate --genpath=path to where the wrapping code should be saved
    1818
    19 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.
    20 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:
     19Using 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:
    2120
    2221   ./rtems_trace.py
     22= Compile mode =
    2323
    24  *  compile mode
    25  *  link mode
    26  *  decode mode
     24 
     25   Usage: ./rtems_trace.py -m compile -i name of the compiler -g path to the wrapping code
     26                           -o path to where the compiled wrapping code should be saved
     27                           -l path to where the RTEMS libraries were installed
     28          ./rtems_trace.py --mode=compile --compiler=name of the compiler 
     29                           --genpath=path to the wrapping code
     30                           --objpath=path to where the compiled wrapping code should be saved
     31
     32Using 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/''
     33
     34   ./rtems_trace.py --mode=compile --compiler=i386-rtems4.10-gcc
     35
     36will 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.
     37= Link mode =
     38= Decode mode =
     39
    2740= Configuration files =
    2841