Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split the components of the toolbox #83

Closed
diegoferigo opened this issue Feb 24, 2018 · 1 comment
Closed

Split the components of the toolbox #83

diegoferigo opened this issue Feb 24, 2018 · 1 comment

Comments

@diegoferigo
Copy link
Member

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).

@diegoferigo
Copy link
Member Author

diegoferigo commented May 8, 2018

Fixed by 47a920c.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment