Software Development Tools
From oacwiki
You can browse all pages related to development tools in the Software Development Tools wiki category.
Contents |
1 OpenAccess Database Browser and Debugger
Si2's Si2oaD OpenAccess database browser and debugger lets you see inside your OpenAccess database using a web browser or even a debugger.
2 Scripting Languages
The oaScript OpenAccess Scripting Language Bindings allow you to prototype or develop EDA applications using your choice of languages: C#, Perl, Python, Ruby and Tcl.
3 OpenAccess Database Comparison Tool
The Si2dff OpenAccess database comparison tool from Si2 examines two OpenAccess designs and reports the differences. OpenAccess developers use this tool in regression test suites to check against a known good result.
4 Debuggers with OpenAccess Wrapper Scripts
Debugging applications supplied with OpenAccess on UNIX can be difficult because each OpenAccess application is run within a wrapper script. Running Debuggers with OpenAccess presents a technique for debugging applications within a wrapper script.
Note that on Windows the executables are launched directly—no wrapper script is used.
5 Microsoft Visual Studio IDE
5.1 Visual Studio 2005
Cadence uses the Visual Studio 2005 IDE on Windows to develop OpenAccess. Visual Studio 2005 project files are included in the OpenAccess source code.
5.2 Visual Studio 2008
It is straightforward to upgrade and use the OpenAccess Visual Studio 2005 project files on Visual Studio 2008.
5.3 Visual Studio 2010
It is not straightforward to upgrade to Visual Studio 2010. If you know how, please share it with us here.
5.3.1 Windows Debug Libraries Require Visual Studio 2005
In order to load the OpenAccess debug mode libraries in C:\path\to\openaccess\bin\win32\dbg, you must have Visual Studio 2005 installed. If not, the DLLs for your application will not load, and the reason why will be unapparent.
Cadence uses Visual Studio 2005 to compile OpenAccess. The debug mode libraries require library Microsoft.VC80.DebugCRT, which ships only with Visual Studio 2005. Therefore you have these alternatives:
- The simplest is to use only the OpenAccess optimized libraries with your choice of Visual Studio versions. You just will not be able to step into OpenAccess with the debugger.
- Install Visual Studio 2005 and use any of the pre-compiled libraries in the OpenAccess major release
- Compile OpenAccess and your application all on your favorite version of Visual Studio and do whatever you like
Credit for finding the cause of this murky problem goes to Kyle Patterson of Texas Instruments.
6 Eclipse IDE
John McGehee's article Eclipse IDE with OpenAccess shows how to set up and use Eclipse with OpenAccess.
7 CMake
A publicly available CMake module for OpenAccess exists. The oasCSharp C# binding for OpenAccess builds on both Linux and Windows using CMake module amd-init/cmake/modules/FindOpenAccess.cmake. If you want to build OpenAccess applications using CMake, please coordinate with John McGehee of Voom, Inc. to make this CMake module a general solution for all OpenAccess developers.
