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 ccdep.pl more resilient to compiler warnings #5

Closed
pts opened this issue Sep 4, 2017 · 2 comments
Closed

make ccdep.pl more resilient to compiler warnings #5

pts opened this issue Sep 4, 2017 · 2 comments

Comments

@pts
Copy link
Owner

pts commented Sep 4, 2017

The current situation: ./configure ... runs make Makedep, which runs perl -x -S ./ccdep.pl --FAL=assert,no,yes,checker g++, which runs g++ to analyze the dependencies between .cpp files, and analyzes the error and warning messages printed by g++. Newer versions of g++ (and clang++, which is typically run instead of g++ on macOS) tend to print more warnings, which ccdep.pl doesn't understand, and fails.

For example, the most recent message was in #4:

./ccdep.pl: invalid depret: [StdAfx.cpp:5:10: warning: non-portable path to file '"StdAfx.h"'; specified path differs in case from file name on disk [-Wnonportable-include-path]]

Previous, one-by-one fixes to ccdep.pl can be found by running git log -p -- ccdep.pl.

Earliest commit for such a fix is cd9eb51.

Ideas how to improve it:

  • Make ccdep.pl ignore warnings, i.e. make it not never fail with invalid depret.
  • Make ccdep.pl get the dependency information it needs from other outputs of g++ (rather than warning and error messages). For example, g++ -E plus g++ -M -MG could work, with the former changing #warning to $warning, to make it show up in the output of -E.
@pts
Copy link
Owner Author

pts commented Sep 4, 2017

The commit 6e93c43 has made ccdep.pl much more resilient.

@pts
Copy link
Owner Author

pts commented Sep 5, 2017

Closing this until it turns out that the $warning solution is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant