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

Migrate away from gnome-common deprecated vars and macros #1245

Merged
merged 2 commits into from Sep 2, 2016

Conversation

maxyz
Copy link
Contributor

@maxyz maxyz commented Aug 2, 2016

gnome-common is deprecating some vars and macros, listed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829932

This change follows the gnome recommendations from:
https://wiki.gnome.org/Projects/GnomeCommon/Migration

gnome-common is deprecating some vars and macros, listed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829932

This change follows the gnome recommendations from:
https://wiki.gnome.org/Projects/GnomeCommon/Migration
@clefebvre
Copy link
Member

dpkg-buildpackage fails with this PR. It looks like warnings are considered errors:

eel-canvas.c:2230:47: error: redundant redeclaration of ‘eel_canvas_accessible_init’ [-Werror=redundant-decls]
G_DEFINE_TYPE_WITH_CODE (EelCanvasAccessible, eel_canvas_accessible, GTK_TYPE_ACCESSIBLE,
^

@maxyz
Copy link
Contributor Author

maxyz commented Aug 17, 2016

¡Hola Clement!

El 2016-08-17 a las 02:31 -0700, Clement Lefebvre escribió:

dpkg-buildpackage fails with this PR. It looks like warnings are considered
errors:

eel-canvas.c:2230:47: error: redundant redeclaration of
‘eel_canvas_accessible_init’ [-Werror=redundant-decls]
G_DEFINE_TYPE_WITH_CODE (EelCanvasAccessible, eel_canvas_accessible,
GTK_TYPE_ACCESSIBLE,
^

Indeed, that's the AX_IS_RELEASE([git-directory]) doing, afaik. So, if you
build it in the git directory it means that you are working in the code and
could take care of the warnings.

If you don't have a .git directory, then your build is considered from a
release and then the warnings are still warnings.

The autoconf documentation about these macros can be found:
https://www.gnu.org/software/autoconf-archive/ax_is_release.html
https://www.gnu.org/software/autoconf-archive/ax_compiler_flags.html

You can still use the configure parameter: --enable-compile-warnings=yes to
avoid this. But I would prefer, recommend to fix these warnings/errors.

Happy hacking,

"The first 90% of the code accounts for the first 90% of the development time.
The remaining 10% of the code accounts for the other 90% of the development
time."
-- Tom Cargill
Saludos //\ /\ >< `/

@clefebvre
Copy link
Member

Ah cool, it does fix the issue.

Can you add this to your PRs in debian/rules?

We often fix warnings, but it shouldn't stop us from compiling. It's a continuous effort, it's not urgent and shouldn't hold the rest of the work though.

With the addition of AX_IS_RELEASE([git-directory]) in the configure.ac,
warnings are treated as errors when build from a git worktree. This is a
nice feature, but it creates too many show stoppers for the package
building.

Adding --enable-compile-warnings=yes avoids this.
@maxyz
Copy link
Contributor Author

maxyz commented Sep 1, 2016

Done

Sorry that it took me so long.

Happy hacking,

@clefebvre clefebvre merged commit 6037322 into linuxmint:master Sep 2, 2016
@clefebvre
Copy link
Member

Thanks :)

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

Successfully merging this pull request may close these issues.

None yet

2 participants