10:34 p.m.
my apologies for cross-posting but I wasn't getting any response in
Inkscape-User so I thought I might have posted to the wrong list.
I tried to install the latest autopackage of Inkscape but it seems my glibc
is too old (Requires GLIBC_2.4 - I have GLIBC_2.3.6 ... is it possible to
release a GLIBC_2.3.6 autopackage?) and the package suggested I install from
sources. When I try to compile the source, i get an error -
ui/dialog/ocaldialogs.h:247: error: expected class-name before '{' token
ui/dialog/ocaldialogs.h: In constructor
'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&, Gtk::Button&)':
ui/dialog/ocaldialogs.h:250: error: class
'Inkscape::UI::Dialog::FileListViewText' does not have any field named
'ListViewText'
I use Debian Etch (stable) so it seems compiling myself is my best option
but I have tried with about 5 different source packages and the result is
always the same (the package which created this error was 16060 but it is
still there in 16148).
Thanks,
Tony
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a12940589
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
3:18 a.m.
Docsonic wrote:
my apologies for cross-posting but I wasn't getting any response
in
Inkscape-User so I thought I might have posted to the wrong list.
I tried to install the latest autopackage of Inkscape but it seems my glibc
is too old (Requires GLIBC_2.4 - I have GLIBC_2.3.6 ... is it possible to
release a GLIBC_2.3.6 autopackage?) and the package suggested I install from
sources. When I try to compile the source, i get an error -
Yes, it should be possible. I've been a bit distracted lately and
haven't put as much time into managing the deps for the autopackages.
One thing that would certainly help is to get someone running a
GLIBC_2.3 system to make the packages. Are you interested in learning
how to do it?
ui/dialog/ocaldialogs.h:247: error: expected class-name before
'{' token
ui/dialog/ocaldialogs.h: In constructor
'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&, Gtk::Button&)':
ui/dialog/ocaldialogs.h:250: error: class
'Inkscape::UI::Dialog::FileListViewText' does not have any field named
'ListViewText'
I use Debian Etch (stable) so it seems compiling myself is my best option
but I have tried with about 5 different source packages and the result is
always the same (the package which created this error was 16060 but it is
still there in 16148).
It appears we are using a widget from GTK2.10 even though I don't think
we officially require 2.10 yet. Does anyone remember where we were on
pushing to require newer GTK versions? (I'm waiting on a feature from
GTK 2.12 :-) )
Aaron Spike
3:49 a.m.
>Docsonic wrote:
> my apologies for cross-posting but I wasn't getting any response in
*clipped*
> sources. When I try to compile the source, i get an error -
Yes, it should be possible. I've been a bit distracted lately and
haven't put as much time into managing the deps for the autopackages.
One thing that would certainly help is to get someone running a
GLIBC_2.3 system to make the packages. Are you interested in learning
how to do it?
I would have no problem compiling the autopackages (I compile .deb files for
another package on sf so I am not a complete noob at that :-) ) but I do see
a problem looming.
Firstly, I would have to compile at work so it would definately not be a
daily thing, probably not even weekly - irregular at best.
> ui/dialog/ocaldialogs.h:247: error: expected class-name before
'{' token
*clipped*
> still there in 16148).
It appears we are using a widget from GTK2.10 even though I don't
think
we officially require 2.10 yet. Does anyone remember where we were on
pushing to require newer GTK versions? (I'm waiting on a feature from
GTK 2.12 :-) )
Aaron Spike
Secondly (and probably more importantly) I am going to have to sort out the
GTK problems first. I am fully up-to-date on the 'Etch' packages and my GTK
setup is too old. This means that every other Etch user out there has the
same problem. I understand the reasons for going for unstable or testing to
get the up-to-date libraries but, unfortunately, the machine in question is
our mailserver and I am not willing to go off stable for that. Having said
that, I will see what backports are available for GTK and if need be, look
into compiling from sources.
I will let you know what happens.
Thanks,
Tony
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a12946437
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
4:12 a.m.
Docsonic wrote:
Firstly, I would have to compile at work so it would definately not
be a
daily thing, probably not even weekly - irregular at best.
I haven't been very regular at building packages lately. But perhaps if
there were two of us working together we could do a better job. I bet
life would be much better if we built the official release packages on
an older system like etch too.
Secondly (and probably more importantly) I am going to have to sort
out the
GTK problems first. I am fully up-to-date on the 'Etch' packages and my GTK
setup is too old. This means that every other Etch user out there has the
same problem. I understand the reasons for going for unstable or testing to
get the up-to-date libraries but, unfortunately, the machine in question is
our mailserver and I am not willing to go off stable for that. Having said
that, I will see what backports are available for GTK and if need be, look
into compiling from sources.
Actually I think the GTK thing may need to be resolved on the Inkscape
end. If we haven't moved as a project to start using 2.10 then this is
an important bug to fix. I just don't remember what our plan was. I'd
have to go digging through the list archives to find the final word.
Aaron Spike
4:41 a.m.
I haven't been very regular at building packages lately. But
perhaps if
there were two of us working together we could do a better job. I bet
life would be much better if we built the official release packages on
an older system like etch too.
Probably true - Debian is not the most up-to-date flavour of Linux but it is
fairly popular and it is very stable - and if it works on Etch it will
probably be ok on most distros for dependencies. I also have an Etch system
at home so there is another possiblity there - we bought a house last year
so renovations take up most of my time.
Actually I think the GTK thing may need to be resolved on the
Inkscape
end. If we haven't moved as a project to start using 2.10 then this is
an important bug to fix. I just don't remember what our plan was. I'd
have to go digging through the list archives to find the final word.
Aaron Spike
That is interesting - I have looked and there are no backports I can see so
it would be sources. I have the neccessary files and I will see how Etch
handles the compiles on a virtual machine first. That will probably take a
few days :-) I am sure Inkscape will be on GTK 2.10 before Debian upgrades
again (Lenny has 2.10.13 already) so this will probably have to be looked at
anyway if Debian users aren't to be perpetually 2-3 versions behind. (The
current Etch .deb is 0.44-1-.1 so it HAS to be autopackages!)
Thanks for all your help,
Tony
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a12947220
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
1 a.m.
Update....
I installed the relevant gtk et al files from sources on a virtual machine
and it made no difference - I still get exactly the same errors at the same
point in the build. Any other ideas Aaron?
Thanks,
Tony
Docsonic wrote:
>I haven't been very regular at building packages lately. But perhaps if
>there were two of us working together we could do a better job. I bet
>life would be much better if we built the official release packages on
>an older system like etch too.
Probably true - Debian is not the most up-to-date flavour of Linux but it
is fairly popular and it is very stable - and if it works on Etch it will
probably be ok on most distros for dependencies. I also have an Etch
system at home so there is another possiblity there - we bought a house
last year so renovations take up most of my time.
>Actually I think the GTK thing may need to be resolved on the Inkscape
>end. If we haven't moved as a project to start using 2.10 then this is
>an important bug to fix. I just don't remember what our plan was. I'd
>have to go digging through the list archives to find the final word.
>
>Aaron Spike
That is interesting - I have looked and there are no backports I can see
so it would be sources. I have the neccessary files and I will see how
Etch handles the compiles on a virtual machine first. That will probably
take a few days :-) I am sure Inkscape will be on GTK 2.10 before Debian
upgrades again (Lenny has 2.10.13 already) so this will probably have to
be looked at anyway if Debian users aren't to be perpetually 2-3 versions
behind. (The current Etch .deb is 0.44-1-.1 so it HAS to be autopackages!)
Thanks for all your help,
Tony
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a13138876
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
10:59 a.m.
On Fri, Sep 28, 2007 at 02:12:12PM -0500, Aaron Spike wrote:
> Secondly (and probably more importantly) I am going to have to
sort out the
> GTK problems first. I am fully up-to-date on the 'Etch' packages and my GTK
> setup is too old. This means that every other Etch user out there has the
> same problem. I understand the reasons for going for unstable or testing to
> get the up-to-date libraries but, unfortunately, the machine in question is
> our mailserver and I am not willing to go off stable for that. Having said
> that, I will see what backports are available for GTK and if need be, look
> into compiling from sources.
Actually I think the GTK thing may need to be resolved on the Inkscape
end. If we haven't moved as a project to start using 2.10 then this is
an important bug to fix. I just don't remember what our plan was. I'd
have to go digging through the list archives to find the final word.
Hi, I reported this a couple weeks ago, and Bruno Dilly was going to
remove the helper widget so GTK 2.10 was not required. I haven't heard
if this happened yet.
-Mason
12:32 p.m.
On Sep 28, 2007, at 11:18 AM, Aaron Spike wrote:
It appears we are using a widget from GTK2.10 even though I don't
think
we officially require 2.10 yet. Does anyone remember where we were on
pushing to require newer GTK versions? (I'm waiting on a feature from
GTK 2.12 :-) )
DarwinPorts is maxed out at 2.10.14. So I think that's a hard upper
limit for a while.
6:23 p.m.
By the way, the --with-python option has been broken
recently, because somone changed the vars without asking
anyone. It says something like LIBPY or LIBPL. It -should-
say LIBDIR.
bob
3:06 p.m.
New subject: Compiling on Linux - still error in ocaldialog
On Fri, Sep 28, 2007 at 01:18:41PM -0500, Aaron Spike wrote:
Docsonic wrote:
> ui/dialog/ocaldialogs.h:247: error: expected class-name before '{' token
> ui/dialog/ocaldialogs.h: In constructor
> 'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
> Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&, Gtk::Button&)':
> ui/dialog/ocaldialogs.h:250: error: class
> 'Inkscape::UI::Dialog::FileListViewText' does not have any field named
> 'ListViewText'
>
> I use Debian Etch (stable) so it seems compiling myself is my best option
> but I have tried with about 5 different source packages and the result is
> always the same (the package which created this error was 16060 but it is
> still there in 16148).
It appears we are using a widget from GTK2.10 even though I don't think
we officially require 2.10 yet. Does anyone remember where we were on
pushing to require newer GTK versions? (I'm waiting on a feature from
GTK 2.12 :-) )
Aaron Spike
The exact same error still occurs in revision 16411. If GTK 2.10 is
required, shouldn't that show up in the configure (or perhaps
autogen.sh) script? Otherwise, is there an option to not compile the
ocaldialog, or a way to backtrack to a dependency < GTK 2.10?
-Mason
9:50 p.m.
New subject: Compiling on Linux - still error in ocaldialog
As an update to this - I installed cairo 1.2.6, atk 1.9.0, glib 2.14.2, gtk+
2.12.1, and pango 1.19.0 and tried building inkscape 16409 but I still have
the same problem. I am a long way from being experienced enough with
building Linux sources to be able to attempt to solve this but if anyone has
any suggestions (with instructions) of anything I can test or check then I
would be delighted to try it.
Thanks,
Tony
Mason Thomas wrote:
On Fri, Sep 28, 2007 at 01:18:41PM -0500, Aaron Spike wrote:
> Docsonic wrote:
>
> > ui/dialog/ocaldialogs.h:247: error: expected class-name before '{'
> token
> > ui/dialog/ocaldialogs.h: In constructor
> > 'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
> > Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&, Gtk::Button&)':
> > ui/dialog/ocaldialogs.h:250: error: class
> > 'Inkscape::UI::Dialog::FileListViewText' does not have any field named
> > 'ListViewText'
> >
> > I use Debian Etch (stable) so it seems compiling myself is my best
> option
> > but I have tried with about 5 different source packages and the result
> is
> > always the same (the package which created this error was 16060 but it
> is
> > still there in 16148).
>
> It appears we are using a widget from GTK2.10 even though I don't think
> we officially require 2.10 yet. Does anyone remember where we were on
> pushing to require newer GTK versions? (I'm waiting on a feature from
> GTK 2.12 :-) )
>
> Aaron Spike
The exact same error still occurs in revision 16411. If GTK 2.10 is
required, shouldn't that show up in the configure (or perhaps
autogen.sh) script? Otherwise, is there an option to not compile the
ocaldialog, or a way to backtrack to a dependency < GTK 2.10?
-Mason
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a13586186
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
4:19 p.m.
New subject: Compiling on Linux - still error in ocaldialog
On Mon, Nov 05, 2007 at 04:50:02AM -0800, Docsonic wrote:
As an update to this - I installed cairo 1.2.6, atk 1.9.0, glib 2.14.2, gtk+
2.12.1, and pango 1.19.0 and tried building inkscape 16409 but I still have
the same problem. I am a long way from being experienced enough with
building Linux sources to be able to attempt to solve this but if anyone has
any suggestions (with instructions) of anything I can test or check then I
would be delighted to try it.
Thanks,
Tony
I believe you need gtkmm >= 2.10.
-Mason
midnight
New subject: Compiling on Linux - still error in ocaldialog
Thanks a million Mason - It worked!
Ok, to recap, I installed -
atk-1.9.0
cairo-1.2.6
cairomm-1.2.4
glib-2.14.2
glibmm-2.14.2
gtk+-2.12.1
gtkmm-2.12.3
pango-1.19.0
and that allowed me to install inkscape-16479
So, Aaron, you wanted to know if I was interested in making autopackages for
a GLIBC-2.3 system - I am now I can compile properly :-)
When I have time I will experiment a little but if you have a cheat sheet
that is specific for Inkscape, that may speed things up a lot.
Thanks to all who helped in this,
Tony
Mason Thomas wrote:
On Mon, Nov 05, 2007 at 04:50:02AM -0800, Docsonic wrote:
>
> As an update to this - I installed cairo 1.2.6, atk 1.9.0, glib 2.14.2,
> gtk+
> 2.12.1, and pango 1.19.0 and tried building inkscape 16409 but I still
> have
> the same problem. I am a long way from being experienced enough with
> building Linux sources to be able to attempt to solve this but if anyone
> has
> any suggestions (with instructions) of anything I can test or check then
> I
> would be delighted to try it.
>
> Thanks,
>
> Tony
>
I believe you need gtkmm >= 2.10.
-Mason
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
--
View this message in context:
http://www.nabble.com/Compiling-on-Linux-tf4534516.html#a13706894
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
12:42 a.m.
New subject: Compiling on Linux - still error in ocaldialog
Docsonic wrote:
So, Aaron, you wanted to know if I was interested in making
autopackages for
a GLIBC-2.3 system - I am now I can compile properly :-)
Fantastic! Building packages on a GLIBC-2.3 system should create
packages that are able to run well on many linux distros.
When I have time I will experiment a little but if you have a cheat
sheet
that is specific for Inkscape, that may speed things up a lot.
The now out-of-date cheat sheet live at:
http://wiki.inkscape.org/wiki/index.php/CompilingAutopackage
We can correct it as we go. I've got a shell script that I use when I
build packages. Things have been extraordinarily busy for me lately and
I haven't been keeping up on building autopackages. But we should be
able to get things straightened out in a short time.
Thanks very much for your interest. I would really really appreciate the
help.
Aaron Spike
4:28 p.m.
New subject: Patch to check for appropriate gtkmm
On Fri, Nov 02, 2007 at 11:06:19PM -0700, Mason Thomas wrote:
On Fri, Sep 28, 2007 at 01:18:41PM -0500, Aaron Spike wrote:
> Docsonic wrote:
>
> > ui/dialog/ocaldialogs.h:247: error: expected class-name before '{'
token
> > ui/dialog/ocaldialogs.h: In constructor
> > 'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
> > Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&, Gtk::Button&)':
> > ui/dialog/ocaldialogs.h:250: error: class
> > 'Inkscape::UI::Dialog::FileListViewText' does not have any field named
> > 'ListViewText'
> >
> > I use Debian Etch (stable) so it seems compiling myself is my best option
> > but I have tried with about 5 different source packages and the result is
> > always the same (the package which created this error was 16060 but it is
> > still there in 16148).
>
> It appears we are using a widget from GTK2.10 even though I don't think
> we officially require 2.10 yet. Does anyone remember where we were on
> pushing to require newer GTK versions? (I'm waiting on a feature from
> GTK 2.12 :-) )
>
> Aaron Spike
The exact same error still occurs in revision 16411. If GTK 2.10 is
required, shouldn't that show up in the configure (or perhaps
autogen.sh) script? Otherwise, is there an option to not compile the
ocaldialog, or a way to backtrack to a dependency < GTK 2.10?
-Mason
Nobody else seems to be bothered by this (perhaps everyone already has
the most up-to-date libraries?), so if Inkscape is going to require
gtkmm at least 2.10 just to support "ListViewText", at least the
configure script should be updated to require that. Will requiring gtkmm
= 2.10 lock out users unnecessarily?
Anyway, following is a patch to check for a gtkmm >=2.10.
-Mason
Index: configure.ac
===================================================================
--- configure.ac (revision 16450)
+++ configure.ac (working copy)
@@ -584,7 +584,7 @@
else
min_sigc_version=2.0.11
fi
-PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 gtk+-2.0 >= 2.8.0
libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= $min_sigc_version
$ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
+PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0 >=
2.8.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >=
$min_sigc_version $ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
# Check for some boost header files
AC_CHECK_HEADERS([boost/concept_check.hpp], [], AC_MSG_ERROR([You need the boost package
(e.g. libboost-dev)]))
4:30 p.m.
New subject: Patch to check for appropriate gtkmm
OK, well, I presume everyone is happy to now require gtkmm version at
least 2.10, so I added the patch below to the sourceforge tracker.
-Mason
On Fri, Nov 09, 2007 at 11:28:16PM -0800, Mason Thomas wrote:
On Fri, Nov 02, 2007 at 11:06:19PM -0700, Mason Thomas wrote:
> On Fri, Sep 28, 2007 at 01:18:41PM -0500, Aaron Spike wrote:
> > Docsonic wrote:
> >
> > > ui/dialog/ocaldialogs.h:247: error: expected class-name before '{'
token
> > > ui/dialog/ocaldialogs.h: In constructor
> > > 'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
> > > Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&,
Gtk::Button&)':
> > > ui/dialog/ocaldialogs.h:250: error: class
> > > 'Inkscape::UI::Dialog::FileListViewText' does not have any field
named
> > > 'ListViewText'
> > >
> > > I use Debian Etch (stable) so it seems compiling myself is my best option
> > > but I have tried with about 5 different source packages and the result is
> > > always the same (the package which created this error was 16060 but it is
> > > still there in 16148).
> >
> > It appears we are using a widget from GTK2.10 even though I don't think
> > we officially require 2.10 yet. Does anyone remember where we were on
> > pushing to require newer GTK versions? (I'm waiting on a feature from
> > GTK 2.12 :-) )
> >
> > Aaron Spike
>
> The exact same error still occurs in revision 16411. If GTK 2.10 is
> required, shouldn't that show up in the configure (or perhaps
> autogen.sh) script? Otherwise, is there an option to not compile the
> ocaldialog, or a way to backtrack to a dependency < GTK 2.10?
>
> -Mason
>
Nobody else seems to be bothered by this (perhaps everyone already has
the most up-to-date libraries?), so if Inkscape is going to require
gtkmm at least 2.10 just to support "ListViewText", at least the
configure script should be updated to require that. Will requiring gtkmm
>= 2.10 lock out users unnecessarily?
Anyway, following is a patch to check for a gtkmm >=2.10.
-Mason
Index: configure.ac
===================================================================
--- configure.ac (revision 16450)
+++ configure.ac (working copy)
@@ -584,7 +584,7 @@
else
min_sigc_version=2.0.11
fi
-PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 gtk+-2.0 >= 2.8.0
libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= $min_sigc_version
$ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
+PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0
>= 2.8.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >=
$min_sigc_version $ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
# Check for some boost header files
AC_CHECK_HEADERS([boost/concept_check.hpp], [], AC_MSG_ERROR([You need the boost package
(e.g. libboost-dev)]))
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
1:44 a.m.
New subject: Patch to check for appropriate gtkmm
Kees,
2.10 is what you need for the print dialog, right?
--Ted
On Wed, 2007-11-14 at 23:30 -0800, Mason Thomas wrote:
OK, well, I presume everyone is happy to now require gtkmm version
at
least 2.10, so I added the patch below to the sourceforge tracker.
-Mason
On Fri, Nov 09, 2007 at 11:28:16PM -0800, Mason Thomas wrote:
> On Fri, Nov 02, 2007 at 11:06:19PM -0700, Mason Thomas wrote:
> > On Fri, Sep 28, 2007 at 01:18:41PM -0500, Aaron Spike wrote:
> > > Docsonic wrote:
> > >
> > > > ui/dialog/ocaldialogs.h:247: error: expected class-name before
'{' token
> > > > ui/dialog/ocaldialogs.h: In constructor
> > > > 'Inkscape::UI::Dialog::FileListViewText::FileListViewText(guint,
> > > > Inkscape::UI::Dialog::SVGPreview&, Gtk::Label&,
Gtk::Button&)':
> > > > ui/dialog/ocaldialogs.h:250: error: class
> > > > 'Inkscape::UI::Dialog::FileListViewText' does not have any
field named
> > > > 'ListViewText'
> > > >
> > > > I use Debian Etch (stable) so it seems compiling myself is my best
option
> > > > but I have tried with about 5 different source packages and the
result is
> > > > always the same (the package which created this error was 16060 but
it is
> > > > still there in 16148).
> > >
> > > It appears we are using a widget from GTK2.10 even though I don't
think
> > > we officially require 2.10 yet. Does anyone remember where we were on
> > > pushing to require newer GTK versions? (I'm waiting on a feature from
> > > GTK 2.12 :-) )
> > >
> > > Aaron Spike
> >
> > The exact same error still occurs in revision 16411. If GTK 2.10 is
> > required, shouldn't that show up in the configure (or perhaps
> > autogen.sh) script? Otherwise, is there an option to not compile the
> > ocaldialog, or a way to backtrack to a dependency < GTK 2.10?
> >
> > -Mason
> >
>
> Nobody else seems to be bothered by this (perhaps everyone already has
> the most up-to-date libraries?), so if Inkscape is going to require
> gtkmm at least 2.10 just to support "ListViewText", at least the
> configure script should be updated to require that. Will requiring gtkmm
> >= 2.10 lock out users unnecessarily?
>
> Anyway, following is a patch to check for a gtkmm >=2.10.
>
> -Mason
>
>
> Index: configure.ac
> ===================================================================
> --- configure.ac (revision 16450)
> +++ configure.ac (working copy)
> @@ -584,7 +584,7 @@
> else
> min_sigc_version=2.0.11
> fi
> -PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 gtk+-2.0 >= 2.8.0
libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= $min_sigc_version
$ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
> +PKG_CHECK_MODULES(INKSCAPE, gdkmm-2.4 glibmm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0
>= 2.8.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >=
$min_sigc_version $ink_spell_pkg gthread-2.0 >= 2.0 libpng >= 1.2)
>
> # Check for some boost header files
> AC_CHECK_HEADERS([boost/concept_check.hpp], [], AC_MSG_ERROR([You need the boost
package (e.g. libboost-dev)]))
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
5678
days inactive
5726
days old
inkscape-devel@lists.inkscape.org
18 comments
6 participants
participants (6)
-
Aaron Spike -
Bob Jamison -
Docsonic -
Jon A. Cruz -
Mason Thomas -
Ted Gould