Changes between Version 6 and Version 7 of OSSIEListFAQ

Show
Ignore:
Timestamp:
04/15/09 11:14:37 (4 years ago)
Author:
cdietric
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OSSIEListFAQ

    v6 v7  
    152152The skeleton code that needs to be generated by the script is very minimal, 5-10 lines in each file, including XML, CPP, H and makefiles. 
    153153 
    154 Further, how difficult would it be to install a custom defined device into the OSSIE environment so that it could be used in the OEF as part of a waveform application? 
     154=== Further, how difficult would it be to install a custom defined device into the OSSIE environment so that it could be used in the OEF as part of a waveform application? === 
    155155 
    156156Currently, the legacy OSSIE Waveform Developer (OWD) allows creation of new nodes or node configurations (each “node” consists of a directory, by default located under /sdr/nodes/.  Each node directory contains device manager XML files that specify the set of devices available at that node).  OWD can be used to create nodes that use existing devices (this would include new devices that you develop, once they are built and the binary and XML files are installed in the appropriate directories under /sdr/).  Lab 7 provides an example of creating and using a new node configuration.  We are adding this feature to OEF.