How to use STEPcode in an application
- Use SC_IS_SUBBUILD and SC_BUILD_SCHEMAS
- SC_SDAI_ADDITIONAL_EXES_SRCS can be used to have SC build single-file executables (similar to p21read)
- this will not work for applications with more than one source code file or that need to link other libs.
See also: STEPcode CMake variables
- Minimal Part 21 C++ example
- doxygen documentation of apps using STEPcode
- sc/src/express/test - tests executables for the express parser
- sc/test/cpp/ - tests written in c++; these can be built when ENABLE_TESTING is set to ON, but are excluded from 'make all'
- sc/src/test - tests written by NIST; all are up-to-date, but p21read is the most frequently used. See the README in sc/src/test for more.
- sc/src/clprobe-ui - remnants of a UI known as dataProbe; requires the InterViews toolkit, which predates X windows. An attempt has been made to resurrect it, but without success.
- TODO: Example using lazy loading code. For now, see lazy_test.cc in the repo.
C++ applications that are not in the GitHub repository
Laurent Bauer's SCView
- describe use of lazy loading code
- create a page with a small Part 21 file, with description of format and links to relevant classes - SDAI_Application_instance, STEPcomplex, generated code (?)
- run doxygen on parts of STEPcode (libexpress + exppp + fedex_plus, fedex_python, cllazyfile, cleditor, clstepcore + cldai + clutils + base ) and automate doxygen with a script