Hi All,
I've added a configuration option for this. By default deprecated symbol usage is forbidden. Two alternative options are available:
# Use very strict deprecation checks that will cause builds to fail. This is useful for hunting down problems that will arise in future --enable-strict-build=high
# Don't check for deprecated symbol usage. This is useful for releases. --disable-strict-build
If anyone thinks we should do this differently, please speak up!
AV
On 22 February 2013 01:37, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/2/13 Alex Valavanis <valavanisalex@...400...>:
- Add a configuration flag for developers' use (something like
"--enable-strict-build") that introduces the deprecation checks. My preferred option... but would people actually use it?
This is the only workable solution, but the option should have the opposite sense, e.g. it should *disable* the checks. This way configuring without any options will enable these checks by default, while the release manager will run configure with a "--release" option and disable them when generating the tarball.
I think a similar option may already exist - if it does, disabling the checks could be hooked up to the existing option.
Regards, Krzysztof