This is the web site of System Designer and DSPE

System Designer is a software framework for developing domain-specific languages based on model-driven code-generation techniques.

The Digital Stream-Processing Environment (DSPE) is a development environment featuring a visual domain-specific language for designing and implementing stream-processing and signal-processing applications. DSPE has been developed with System Designer and supports multi-core processors and hardware accelerators.


Preference page for DSPE dependencies:

IMPORTANT: version 1.1.1 Beta of DSPE introduced a new solution to manage external dependencies. It is now possible to specify them through the preference page named “Dependencies” located at Window->Preferences->System Designer. By using the preference page, it is possible to specify the location of libraries and source code required to compile the generated applications. You may therefore avoid configuring the dependencies manually, as described below.

You have to take care of following dependencies:

  • If the threading system you are using is PThreads, DSPE has to be aware of the location of its libraries and header files. You therefore either have to use the default location or to specify where they are located. If the threading system is instead Windows Threads, there is no need for this information.
  • If you want to use the DSPE generator for Graphical User Interfaces (using WxWidgets), You have to provide the required paths. On Linux, you may use wx-config to solve the dependencies. DSPE currently support the ANSI build mode for WxWidgets.
  • Further dependencies are sometime needed by the Audio n-Genie’s components and may be managed through “Requirements” at the DSPE model level. To be able to run applications inside Eclipse, you therefore occasionally have to put their dynamically linked libraries on the PATH. On a system where the dynamically linked libraries are not on the PATH, don’t forget to put them in the same folder of the executable, if you want to run the applications outside Eclipse.

Installation with setup utilities:

IMPORTANT: if you installed the DSPE through the setup utility available on SourceForge, all the dependencies’ settings are done automatically at installation time. Default directories are used on Windows:

  • PThreads is installed together with MinGW in the Eclipse folder,
  • WxWidgets is available in the Eclipse folder and has already been compiled in three different forms (MinGW, VC++ 32 and VC++ 64) to support compilation inside Eclipse and Visual C++.
  • There’s a folder named “onPath” inside the Eclipse folder, which is put on the PATH by a .bat file when DSPE is launched. Audio n-Genie’s dependencies are put inside the onPath folder by their installer. You may further use the folder to manage your own dependencies.

Manual configuration of dependencies:

DSPE generates C and C++ source code that may depend on some open source libraries and frameworks. It may for instance use PThreads to execute concurrent tasks. If you generate code that depends on it, it is therefore necessary to put PThreads on the PATH environment variable.

If you design GUIApplications, WxWidgets is used as a widgets framework. The same as above therefore applies.

On Windows, a shortcut to configure all the needed environment variables on-the-fly, is by using a .bat file to launch Eclipse. This is an example of its contents:

@echo off
set Path=%~dp0onPath;%~dp0mingwbin;%Path%
set LIBRARY_PATH=%~dp0wxWidgets-2.8.10libgcc_lib;%LIBRARY_PATH%
set CPATH=%~dp0wxWidgets-2.8.10include;%~dp0wxWidgets-2.8.10contribinclude;%~dp0wxWidgets-2.8.10libgcc_libmswd;%CPATH%
start /d”%~dp0″ eclipse.exe

In the sample .bat file some dependencies are contained in the sub-folder “/onPath”, in the “/bin” directory of MinGW and in some folders for wxWidgets. To work correctly, the .bat file has to be installede in the same directory of the eclipse.exe file (root folder of Eclipse).