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

API for controlling modules from outside the compiler #4

Closed
schrnz opened this issue Jul 21, 2017 · 1 comment
Closed

API for controlling modules from outside the compiler #4

schrnz opened this issue Jul 21, 2017 · 1 comment

Comments

@schrnz
Copy link
Member

schrnz commented Jul 21, 2017

Currently, the artist modules used are determined at compile-time by hardwiring them in optimizing_compiler.cc.

A better approach is to allow for activation and deactivation without requiring recompilation of ARTist by, e.g., controlling modules through either configurations (files?) or command line arguments to the compiler.

@schrnz schrnz changed the title Controlling modules from outside API for controlling modules from outside the compiler Jul 21, 2017
@schrnz
Copy link
Member Author

schrnz commented Sep 29, 2017

Moved to Project-ARTist/meta#4

@schrnz schrnz closed this as completed Sep 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant