-
Notifications
You must be signed in to change notification settings - Fork 285
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
Replace DEBUG with EXIV2_DEBUG_MESSAGES #938
Conversation
Codecov Report
@@ Coverage Diff @@
## 0.27-maintenance #938 +/- ##
=================================================
Coverage 63.03% 63.03%
=================================================
Files 156 156
Lines 21628 21628
=================================================
Hits 13634 13634
Misses 7994 7994
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a surprise. I've already tagged and built 0.27.2-RC2. I would like to avoid code changes between 0.27.2-RC2 and 0.27.2. We could integrate this tonight, and either:
- Delete tag 0.27.2-RC2 and rebuild/publish/retag on Saturday.
- Integrate this and tag as 0.27.2-RC3 build/publish/tag on Saturday.
- Slipstream this into 0.27.2 in a couple of weeks.
What do you think about adding EXIV2_DEBUG_MESSAGES to CMakeLists.txt?
In the past, I've used CXXFLAGS=-DDEBUG to switch on those messages. I don't want them enabled everywhere because (as the user mentioned) it generate a lot of output from parts of the code that are not being investigate. So, I prefer to switch it on to rebuild selected files:
$ touch ../src/voo.cpp ; make CXXFLAGS=-DDEBUG
Or, define it in the code while debugging (and remove before commit).
// foo.cpp
#ifndef DEBUG
#define DEBUG
#endif
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'm in favour of this AND don't make it an option in CMakeLists.txt. It makes it very clear that this code is for team/feature debugging.
So, I'm happy to approve this after we've discussed what to do about the tag I've already created for v0.27.2-RC2.
My feeling is that we should go to v0.27.2-RC3 which will require updating release notes.txt and the platform/ReadMe.txt files (almost painless).
@piponazo We've had a change of plan. #940 (comment) Can you merge this onto 0.27-maintenance by Sunday afternoon (2019-07-14)? |
Sure! I'll rebase, push and merge once the CI is green 😉 |
7e2522b
to
c351765
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please cherry-pick the commits that went into master, as this still has the original inconsistencies in the docs.
c351765
to
a1d4398
Compare
a1d4398
to
02facf9
Compare
Don't spend time on README.md. The version of that on 'master' and '0.27-maintenance' have diverged substantially. I'll make sure that the version on 0.27-maintenance is good. And fix 'master' when we arrive at 0.28-RC1 (maybe September 2020). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for backporting this!
Fixes #926