Changes between Version 39 and Version 40 of Developer/Projects/Open/TraceTool


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

Legend:

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

    v39 v40  
    1414
    1515
    16   Usage: ./rtems_trace.py -m generate -g path to where the wrapping code should be saved
    17          ./rtems_trace.py --mode=generate --genpath=path to where the wrapping code should be saved
     16  Usage: ./rtems_trace.py -m generate
     17                          -g path to where the wrapping code should be saved
     18         ./rtems_trace.py --mode=generate
     19                          --genpath=path to where the wrapping code should be saved
    1820
    1921Using 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:
     
    2325
    2426 
    25    Usage: ./rtems_trace.py -m compile -i name of the compiler -g path to the wrapping code
     27   Usage: ./rtems_trace.py -m compile
     28                           -i name of the compiler
     29                           -g path to the wrapping code
    2630                           -o path to where the compiled wrapping code should be saved
    2731                           -l path to where the RTEMS libraries were installed
    28           ./rtems_trace.py --mode=compile --compiler=name of the compiler 
     32          ./rtems_trace.py --mode=compile
     33                           --compiler=name of the compiler 
    2934                           --genpath=path to the wrapping code
    3035                           --objpath=path to where the compiled wrapping code should be saved
     36                           --lib=path to where the RTEMS libraries were installed
    3137
    3238Using 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/''.
     
    3945
    4046
    41    Usage: ./rtems
     47   Usage: ./rtems_trace.py -m link
     48                           -i name of the compiler
     49                           -b RTEMS build path
     50                           -o path to the compiled wrapping code
     51                           -  list of comma separated
     52                           -l path to where the RTEMS libraries were installed
     53          ./rtems_trace.py --mode=link
     54                           --compiler name of the compiler   
     55                           --build=RTEMS build path
     56                           --trace-obj=
     57
     58                           --lib path to where the RTEMS libraries were installed
    4259= Decode mode =
    4360