Gtk+ backend target
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
AV
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
@Tavmjong - Your problem occurs because the GTK_CHECK_BACKEND macro is only available when Gtk+ 3 development libraries are installed. I've put a guard for this in r12249
@suv - Your problem occurs because I'm an idiot... equality operators need something on the right hand side! Fix on its way!
On 26 March 2013 17:48, ~suv <suv-sf@...58...> wrote:
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>:
Hi All,
Why do we explicitly check for the Gtk+ backend target in configure.ac? The resulting $gtk_backend_target variable isn't used anywhere except for deciding whether to link the -lX11 library or not.
In fact, this seems unnecessary too, because gtk+ reports whether it needs -lX11 via pkg-config so we should pick up the dependency automatically.
Our method of checking the backend target isn't supported by gtk+ 3 in any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
The test for X11 in Gtk+ 2 should be fixed in r12250
AV
On 26 March 2013 18:47, Alex Valavanis <valavanisalex@...400...> wrote:
@Tavmjong - Your problem occurs because the GTK_CHECK_BACKEND macro is only available when Gtk+ 3 development libraries are installed. I've put a guard for this in r12249
@suv - Your problem occurs because I'm an idiot... equality operators need something on the right hand side! Fix on its way!
On 26 March 2013 17:48, ~suv <suv-sf@...58...> wrote:
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>: > > Hi All, > > Why do we explicitly check for the Gtk+ backend target in > configure.ac? The resulting $gtk_backend_target variable isn't used > anywhere except for deciding whether to link the -lX11 library or not. > > In fact, this seems unnecessary too, because gtk+ reports whether it > needs -lX11 via pkg-config so we should pick up the dependency > automatically. > > Our method of checking the backend target isn't supported by gtk+ 3 in > any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thanks for the quick fix! Happy, happy!
On Tue, 2013-03-26 at 18:47 +0000, Alex Valavanis wrote:
@Tavmjong - Your problem occurs because the GTK_CHECK_BACKEND macro is only available when Gtk+ 3 development libraries are installed. I've put a guard for this in r12249
@suv - Your problem occurs because I'm an idiot... equality operators need something on the right hand side! Fix on its way!
On 26 March 2013 17:48, ~suv <suv-sf@...58...> wrote:
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>: > > Hi All, > > Why do we explicitly check for the Gtk+ backend target in > configure.ac? The resulting $gtk_backend_target variable isn't used > anywhere except for deciding whether to link the -lX11 library or not. > > In fact, this seems unnecessary too, because gtk+ reports whether it > needs -lX11 via pkg-config so we should pick up the dependency > automatically. > > Our method of checking the backend target isn't supported by gtk+ 3 in > any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Configure and make on OS X 10.7.5 for GTK+/Quartz (as well as for GTK+/X11) succeeds with r12250 - thx :-)
(side note: I have to admit that having configure tell me at the end which GTK+ backend is used was quite convenient on systems like OS X where two different backends of GTK+ are available ;) )
On 2013-03-26 19:47 +0100, Alex Valavanis wrote:
@Tavmjong - Your problem occurs because the GTK_CHECK_BACKEND macro is only available when Gtk+ 3 development libraries are installed. I've put a guard for this in r12249
@suv - Your problem occurs because I'm an idiot... equality operators need something on the right hand side! Fix on its way!
On 26 March 2013 17:48, ~suv <suv-sf@...58...> wrote:
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/3/25 Alex Valavanis <valavanisalex@...400...>: > > Hi All, > > Why do we explicitly check for the Gtk+ backend target in > configure.ac? The resulting $gtk_backend_target variable isn't used > anywhere except for deciding whether to link the -lX11 library or not. > > In fact, this seems unnecessary too, because gtk+ reports whether it > needs -lX11 via pkg-config so we should pick up the dependency > automatically. > > Our method of checking the backend target isn't supported by gtk+ 3 in > any case, so can we get rid of the test?
Yes, it should be safe to remove - it's probably just another piece of leftover configure voodoo like the gcc > 3 check.
Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
(side note: I have to admit that having configure tell me at the end which GTK+ backend is used was quite convenient on systems like OS X where two different backends of GTK+ are available ;) )
I agree that it would be a useful thing to have, but unfortunately there doesn't seem to be a convenient means of testing for this with Gtk+ 3. I guess it would be possible to put in a loop to check through all known backends.
On 26 March 2013 23:31, ~suv <suv-sf@...58...> wrote:
Configure and make on OS X 10.7.5 for GTK+/Quartz (as well as for GTK+/X11) succeeds with r12250 - thx :-)
(side note: I have to admit that having configure tell me at the end which GTK+ backend is used was quite convenient on systems like OS X where two different backends of GTK+ are available ;) )
On 2013-03-26 19:47 +0100, Alex Valavanis wrote:
@Tavmjong - Your problem occurs because the GTK_CHECK_BACKEND macro is only available when Gtk+ 3 development libraries are installed. I've put a guard for this in r12249
@suv - Your problem occurs because I'm an idiot... equality operators need something on the right hand side! Fix on its way!
On 26 March 2013 17:48, ~suv <suv-sf@...58...> wrote:
r12247 fails to configure on OS X 10.7.5 with GTK+/Quartz 2.24.17 (wrongly detects X11 backend (backend is Quartz), and then fails to find a package 'x11'):
checking if Gtk+ 2.0 is using the X11 backend target... yes checking for X11... no configure: error: Package requirements (x11) were not met:
No package 'x11' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1
On 2013-03-26 17:55 +0100, Tavmjong Bah wrote:
Getting an error during configure:
checking for IMAGEMAGICK... yes ./configure: line 21342: syntax error near unexpected token `x11,' ./configure: line 21342: ` GTK_CHECK_BACKEND(x11, , have_x11=yes, have_x11=no)'
On Tue, 2013-03-26 at 16:07 +0000, Alex Valavanis wrote:
It turns out that we *did* need to explicitly link to -lX11 because we use the X11 library directly (not just as the Gtk+ backend). I've restored the test in r12247 for Gtk+ 2 builds, and added a new test for Gtk+ 3 builds.
On 25 March 2013 19:50, Alex Valavanis <valavanisalex@...400...> wrote:
OK... done in r12244. The only real disadvantage, I guess, is that we no longer have a handy variable for debugging purposes. However, it's not Gtk+ 3 compatible, so it was only of limited usefulness.
AV
On 25 March 2013 19:21, Krzysztof Kosiński <tweenk.pl@...400...> wrote: > > > 2013/3/25 Alex Valavanis <valavanisalex@...400...>: >> >> >> Hi All, >> >> Why do we explicitly check for the Gtk+ backend target in >> configure.ac? The resulting $gtk_backend_target variable isn't used >> anywhere except for deciding whether to link the -lX11 library or >> not. >> >> In fact, this seems unnecessary too, because gtk+ reports whether it >> needs -lX11 via pkg-config so we should pick up the dependency >> automatically. >> >> Our method of checking the backend target isn't supported by gtk+ 3 >> in >> any case, so can we get rid of the test? > > > > Yes, it should be safe to remove - it's probably just another piece > of > leftover configure voodoo like the gcc > 3 check. > > Regards, Krzysztof
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (4)
-
Alex Valavanis -
Krzysztof Kosiński -
Tavmjong Bah -
~suv