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

make analyzer running separated from command generation #19

Closed
rizsotto opened this issue Aug 29, 2014 · 1 comment
Closed

make analyzer running separated from command generation #19

rizsotto opened this issue Aug 29, 2014 · 1 comment

Comments

@rizsotto
Copy link
Owner

the driver module currently is taking a compilation command and generates analysis command (parse, filter, etc..) then it executes it. would it be better to divide this two steps?

then 'beye' would generate a compilation database (with a help from 'bear'). then from a compilation database would generate a list of commands (cmd + cwd) to run the analyzer. then those commands can be run and generate report files. then from those report files it would generate the final report.

this intermediate steps would give more insights what's going on. (easier to understand) would be easier to test. and maybe reuse some parts would be also easier.

@rizsotto
Copy link
Owner Author

rizsotto commented Sep 1, 2014

it made things more visible, what's going on.

@rizsotto rizsotto closed this as completed Sep 1, 2014
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