You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until the 3.0 version, the toolbox installs a monolithic mex function generated by linking all the blocks with the toolbox utilities (BlockInformation, RobotInterface, Configuration, Log, ...) and the toolbox.cpp S-function.
Considering the experimental automatic code generation support #82, generating different components by splitting the library in the following way might be helfulp:
WBToolboxLibrary: all the classes for having Blocks and WB-Blocks fully functioning
WBToolbox.mex: the WBToolboxLibrary plus simulink-related stuff (SimulinkBlockInformation, toolbox.cpp, and Matlab's libraries)
WBToolboxCoder: the WBToolboxLibrary plus simulink-coder-related stuff (Other issues)
In this way, the WBToolboxLibrary becomes a real shared library that is compiled against either simulink libraries (and this would require Matlab installed) or the driver of the generated code (Matlab-independent).
The text was updated successfully, but these errors were encountered:
Until the
3.0
version, the toolbox installs a monolithicmex
function generated by linking all the blocks with the toolbox utilities (BlockInformation
,RobotInterface
,Configuration
,Log
, ...) and thetoolbox.cpp
S-function.Considering the experimental automatic code generation support #82, generating different components by splitting the library in the following way might be helfulp:
WBToolboxLibrary
: all the classes for havingBlock
s andWB-Block
s fully functioningWBToolbox.mex
: theWBToolboxLibrary
plus simulink-related stuff (SimulinkBlockInformation
,toolbox.cpp
, and Matlab's libraries)WBToolboxCoder
: theWBToolboxLibrary
plus simulink-coder-related stuff (Other issues)In this way, the
WBToolboxLibrary
becomes a real shared library that is compiled against either simulink libraries (and this would require Matlab installed) or the driver of the generated code (Matlab-independent).The text was updated successfully, but these errors were encountered: