Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #127

Closed
Open
Created May 08, 2017 by Sebastian Eichelbaum@ebaumMaintainer

-RM-296-MR-Support loading of arbitrary extensions from toolkit libraries.

When building your own toolboxes, you where only able to load them when having at least one module in it. But it might be useful to have toolkit libs being loaded even if they do not contain a module to support registration of additional extensions. A very pratical example:

  • you write your own postrocessor in a stand-alone toolbox -> how to register it?

(from redmine: created on 2013-08-01, closed on 2013-08-05)

Assignee
Assign to
OpenWalnut 1.4
Milestone
OpenWalnut 1.4
Assign milestone
Time tracking