You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(22) |
Sep
(33) |
Oct
(1) |
Nov
(7) |
Dec
(19) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(12) |
Feb
(9) |
Mar
(11) |
Apr
(6) |
May
(3) |
Jun
(8) |
Jul
(9) |
Aug
(4) |
Sep
(12) |
Oct
(8) |
Nov
(9) |
Dec
(3) |
2010 |
Jan
(6) |
Feb
|
Mar
|
Apr
(4) |
May
(19) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(3) |
Oct
(4) |
Nov
|
Dec
(13) |
2011 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(18) |
Dec
(1) |
2012 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
From: Bob H. <ra...@ba...> - 2010-07-07 07:31:55
|
On Thu, 2010-06-24 at 10:18 +0100, Bob Ham wrote: > Would it be possible for you put the (latest) dbus-c++ > documentation online so that search engines find your web space rather > than mine? *Shrug* the documentation in my web space is gone. -- Bob Ham <ra...@ba...> for (;;) { ++pancakes; } |
From: Bob H. <ra...@ba...> - 2010-06-24 14:15:36
|
Hi there, I created the doxygen documentation for dbus-c++ some time ago and put it on a web server so that I could view it at a remote location: http://pkl.net/~node/teasel/dbus-cpp/ Unfortunately, it is now the primary (only?) source of dbus-c++ documentation on the Internet. See the attached log, which is is one of 47, stretching back to June 2009. I don't want to deprive people of documentation if they need it but it's also not my responsibility to host documentation for dbus-c++. Would it be possible for you put the (latest) dbus-c++ documentation online so that search engines find your web space rather than mine? Thanks, Bob Ham -- Bob Ham <ra...@ba...> for (;;) { ++pancakes; } |
From: Andreas V. <li...@br...> - 2010-06-19 09:35:10
|
Am Mon, 31 May 2010 17:49:26 +0800 schrieb Mat: > Hi, Hello Mat, > My situations is , I got error "program too big to fit in memory" when > execute automake, and got hanged when execute autoconf. > ( I tested it on winxp and windows7, which memories are bigger than > 1G. ) > > The program I downloaded is from mingw site: > https://sourceforge.net/projects/mingw/files/ Last time I developed windows software It worked well with mingw if I remember correct. > version is: > automake1.11-1.11-1-mingw32-bin.tar.lzma > autoconf2.5-2.64-1-mingw32-bin.tar.lzma > > My build/test environment is setup via kde-windows' emerge > http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge > > kde-windows doesn't support autotools well currently, so I download > mingw/msys and setup manually to use it. Hm, I used a clean system with a Mingw/Msys installation without something KDE specific. Maybe mixing environments doesn't work here. > Would you like to share how your build suite is ( like urls, or > reference pages.. )? > Different build suite usually cause different result. So, it will be > great help for reduce > win32 porting via autools. As I said, I've no more win32 suite here as I don't develop open source windows software at the moment. Last time I provided a win32 binary I used a Linux cross compiler. That worked good. Is it possible for use to use a cross compiler setup? Maybe I could help you with this. > Cmake is just an working option for now, so please feel free to leave > patches of cmake aside temporarily, if it's not suitable for dbus-c++ > developing.. Let's keep trying to find out other solutions :-) I'm no big fan of providing two build systems. As long as there's no official release I would propose to not include it into the GIT repo for now. regards Andreas |
From: Andreas V. <li...@br...> - 2010-06-19 09:25:10
|
Am Tue, 08 Jun 2010 12:39:47 +0530 schrieb Joe Steeve: > Hello Andreas, > > Access to the link listed on > > http://www.freedesktop.org/wiki/Software/dbus-c++ > > requests for sf.net authentication (even for reading). Hello Joe, thanks for reporting. I used a wrong link. The problem is fixed now. regards Andreas |
From: Joe S. <js...@hi...> - 2010-06-08 07:37:37
|
Hello Andreas, Access to the link listed on http://www.freedesktop.org/wiki/Software/dbus-c++ requests for sf.net authentication (even for reading). Regards, Joe -- Joe Steeve HiPro IT Solutions Pvt. Ltd. http://hipro.co.in/ |
From: Joe S. <js...@hi...> - 2010-06-02 12:55:39
|
On Fri, 2010-05-28 at 18:39 +0200, Andreas Volz wrote: > To be honest, I'm not sure. Currently I'm not that happy with GIT in > this project. Maybe I need to give it more time... > > My idea is to work on current patches and later decide about a SVN > move. For this little project I've not yet seen the advantage of GIT. I'd be really happy if you stick to 'git' :D Git (or any other DVCS for that matter) is really convenient when we've to maintain changes which are not necessarily on the main repo. -- Joe Steeve HiPro IT Solutions Pvt. Ltd. http://hipro.co.in/ |
From: Mat <mat...@gm...> - 2010-05-31 09:49:54
|
Hi, My situations is , I got error "program too big to fit in memory" when execute automake, and got hanged when execute autoconf. ( I tested it on winxp and windows7, which memories are bigger than 1G. ) The program I downloaded is from mingw site: https://sourceforge.net/projects/mingw/files/ version is: automake1.11-1.11-1-mingw32-bin.tar.lzma autoconf2.5-2.64-1-mingw32-bin.tar.lzma My build/test environment is setup via kde-windows' emerge http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge kde-windows doesn't support autotools well currently, so I download mingw/msys and setup manually to use it. Would you like to share how your build suite is ( like urls, or reference pages.. )? Different build suite usually cause different result. So, it will be great help for reduce win32 porting via autools. Cmake is just an working option for now, so please feel free to leave patches of cmake aside temporarily, if it's not suitable for dbus-c++ developing.. Let's keep trying to find out other solutions :-) sincerely, Mat On Sun, May 30, 2010 at 4:18 PM, Andreas Volz <li...@br...> wrote: > Am Sun, 30 May 2010 06:42:38 +0800 schrieb Mat: > > Hello Mat, > > really? Which problems did you have with autotools on win32. With other > projects I never had bigger problems with the mingw/msys suite. Maybe we > could solve the problems instead of using a second build system. > > regards > Andreas > >> Hi~ >> >> I got some progress on adding cmake support on win32 , here is the >> patch: >> >> https://sourceforge.net/tracker/?func=detail&aid=3009067&group_id=236997&atid=1101684 >> >> The cmake files are designed for win32 only, aim to provide better >> win32 build support for dbus-c++ . ( Because automake, autoconf, ... >> have problem on win32 ) >> >> Hope it helps :-) >> >> sincerely, Mat. >> >> >> On Sat, May 29, 2010 at 10:24 PM, Mat <mat...@gm...> wrote: >> > On Sat, May 29, 2010 at 12:39 AM, Andreas Volz >> > <li...@br...> wrote: >> >> Am Thu, 27 May 2010 01:58:15 +0800 schrieb Mat: >> >> >> >> To be honest, I'm not sure. Currently I'm not that happy with GIT >> >> in this project. Maybe I need to give it more time... >> >> >> >> My idea is to work on current patches and later decide about a SVN >> >> move. For this little project I've not yet seen the advantage of >> >> GIT. >> > >> > No problem, I will propose my commits with patches first. >> > >> > p.s. You use git, I use git; you use svn, I use svn :-) >> > >> > sincerely, Mat. >> >> >> >> regards >> >> Andreas >> >> >> >>> No problem. I just add a bug report in the sourceforge: >> >>> >> >>> https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 >> >>> >> >>> I am happy to see that bugs/reports were taken care of, great job >> >>> and thank you!! >> >>> >> >>> sincerely, mat. >> >>> >> >>> p.s., I am learning gitorious in these days. If gitorious is >> >>> prefered, please info me, I can also push patches via gitorious >> >>> and propose merge there, too. >> >>> >> >>> On Wed, May 26, 2010 at 11:04 PM, Andreas Volz >> >>> <li...@br...> wrote: >> >>> > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: >> >>> > >> >>> > Hello Mat, >> >>> > >> >>> > nice to hear that it works with win32. >> >>> > >> >>> > Could you add your patches here: >> >>> > >> >>> > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 >> >>> > >> >>> > Yes I know many not applied patches there, but at least they're >> >>> > not lost. :-) >> >>> > >> >>> > I'll apply as fast as possible... >> >>> > >> >>> > regards >> >>> > Andreas >> >>> > >> >>> >> ---------- Forwarded message ---------- >> >>> >> From: Mat <mat...@gm...> >> >>> >> Date: Tue, May 18, 2010 at 2:56 AM >> >>> >> Subject: Patch for dbus-c++ win32 porting >> >>> >> To: kde...@kd... >> >>> >> >> >>> >> >> >>> >> Hi All, >> >>> >> I use dbus-c++ library in my programs and found that it's >> >>> >> great for c++ based projects. >> >>> >> >> >>> >> I tried to port dbus-c++ to win32, and have some progress >> >>> >> these days. The libdbusc++ can now work on my winxp :-) >> >>> >> ( for some simple examples, not yet try some real program, >> >>> >> like inkboard,...etc ) >> >>> >> >> >>> >> Patches are as attachment: >> >>> >> dbus-c++-src-commit.patch is for import into emerge dir. >> >>> >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ >> >>> >> works_for_win32.patch is a patch for dbus-c++-src[1] source >> >>> >> code >> >>> >> >> >>> >> Could you help to review these works and give me some advice >> >>> >> to push the works go furthur? >> >>> >> >> >>> >> Thank you very much. >> >>> >> >> >>> >> sincerely, Mat. >> >>> >> >> >>> >> [1]. http://gitorious.org/dbus-cplusplus >> >>> >> [2]. dbus-c++-src-commit.patch >> >>> >> [3]. dbus-1.pc >> >>> >> [4]. works_for_win32.patch >> >>> > >> >>> > ------------------------------------------------------------------------------ >> >>> > >> >>> > _______________________________________________ >> >>> > dbus-cplusplus-devel mailing list >> >>> > dbu...@li... >> >>> > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel >> >>> > >> >>> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> >> dbus-cplusplus-devel mailing list >> >> dbu...@li... >> >> https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel >> >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > dbus-cplusplus-devel mailing list > dbu...@li... > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > |
From: Andreas V. <li...@br...> - 2010-05-30 08:20:10
|
Am Sun, 30 May 2010 06:42:38 +0800 schrieb Mat: Hello Mat, really? Which problems did you have with autotools on win32. With other projects I never had bigger problems with the mingw/msys suite. Maybe we could solve the problems instead of using a second build system. regards Andreas > Hi~ > > I got some progress on adding cmake support on win32 , here is the > patch: > > https://sourceforge.net/tracker/?func=detail&aid=3009067&group_id=236997&atid=1101684 > > The cmake files are designed for win32 only, aim to provide better > win32 build support for dbus-c++ . ( Because automake, autoconf, ... > have problem on win32 ) > > Hope it helps :-) > > sincerely, Mat. > > > On Sat, May 29, 2010 at 10:24 PM, Mat <mat...@gm...> wrote: > > On Sat, May 29, 2010 at 12:39 AM, Andreas Volz > > <li...@br...> wrote: > >> Am Thu, 27 May 2010 01:58:15 +0800 schrieb Mat: > >> > >> To be honest, I'm not sure. Currently I'm not that happy with GIT > >> in this project. Maybe I need to give it more time... > >> > >> My idea is to work on current patches and later decide about a SVN > >> move. For this little project I've not yet seen the advantage of > >> GIT. > > > > No problem, I will propose my commits with patches first. > > > > p.s. You use git, I use git; you use svn, I use svn :-) > > > > sincerely, Mat. > >> > >> regards > >> Andreas > >> > >>> No problem. I just add a bug report in the sourceforge: > >>> > >>> https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 > >>> > >>> I am happy to see that bugs/reports were taken care of, great job > >>> and thank you!! > >>> > >>> sincerely, mat. > >>> > >>> p.s., I am learning gitorious in these days. If gitorious is > >>> prefered, please info me, I can also push patches via gitorious > >>> and propose merge there, too. > >>> > >>> On Wed, May 26, 2010 at 11:04 PM, Andreas Volz > >>> <li...@br...> wrote: > >>> > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: > >>> > > >>> > Hello Mat, > >>> > > >>> > nice to hear that it works with win32. > >>> > > >>> > Could you add your patches here: > >>> > > >>> > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 > >>> > > >>> > Yes I know many not applied patches there, but at least they're > >>> > not lost. :-) > >>> > > >>> > I'll apply as fast as possible... > >>> > > >>> > regards > >>> > Andreas > >>> > > >>> >> ---------- Forwarded message ---------- > >>> >> From: Mat <mat...@gm...> > >>> >> Date: Tue, May 18, 2010 at 2:56 AM > >>> >> Subject: Patch for dbus-c++ win32 porting > >>> >> To: kde...@kd... > >>> >> > >>> >> > >>> >> Hi All, > >>> >> I use dbus-c++ library in my programs and found that it's > >>> >> great for c++ based projects. > >>> >> > >>> >> I tried to port dbus-c++ to win32, and have some progress > >>> >> these days. The libdbusc++ can now work on my winxp :-) > >>> >> ( for some simple examples, not yet try some real program, > >>> >> like inkboard,...etc ) > >>> >> > >>> >> Patches are as attachment: > >>> >> dbus-c++-src-commit.patch is for import into emerge dir. > >>> >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ > >>> >> works_for_win32.patch is a patch for dbus-c++-src[1] source > >>> >> code > >>> >> > >>> >> Could you help to review these works and give me some advice > >>> >> to push the works go furthur? > >>> >> > >>> >> Thank you very much. > >>> >> > >>> >> sincerely, Mat. > >>> >> > >>> >> [1]. http://gitorious.org/dbus-cplusplus > >>> >> [2]. dbus-c++-src-commit.patch > >>> >> [3]. dbus-1.pc > >>> >> [4]. works_for_win32.patch > >>> > > >>> > ------------------------------------------------------------------------------ > >>> > > >>> > _______________________________________________ > >>> > dbus-cplusplus-devel mailing list > >>> > dbu...@li... > >>> > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > >>> > > >>> > >> > >> ------------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> dbus-cplusplus-devel mailing list > >> dbu...@li... > >> https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > >> > > |
From: Mat <mat...@gm...> - 2010-05-29 22:43:05
|
Hi~ I got some progress on adding cmake support on win32 , here is the patch: https://sourceforge.net/tracker/?func=detail&aid=3009067&group_id=236997&atid=1101684 The cmake files are designed for win32 only, aim to provide better win32 build support for dbus-c++ . ( Because automake, autoconf, ... have problem on win32 ) Hope it helps :-) sincerely, Mat. On Sat, May 29, 2010 at 10:24 PM, Mat <mat...@gm...> wrote: > On Sat, May 29, 2010 at 12:39 AM, Andreas Volz <li...@br...> wrote: >> Am Thu, 27 May 2010 01:58:15 +0800 schrieb Mat: >> >> To be honest, I'm not sure. Currently I'm not that happy with GIT in >> this project. Maybe I need to give it more time... >> >> My idea is to work on current patches and later decide about a SVN >> move. For this little project I've not yet seen the advantage of GIT. > > No problem, I will propose my commits with patches first. > > p.s. You use git, I use git; you use svn, I use svn :-) > > sincerely, Mat. >> >> regards >> Andreas >> >>> No problem. I just add a bug report in the sourceforge: >>> >>> https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 >>> >>> I am happy to see that bugs/reports were taken care of, great job and >>> thank you!! >>> >>> sincerely, mat. >>> >>> p.s., I am learning gitorious in these days. If gitorious is prefered, >>> please info me, I can also push patches via gitorious and propose >>> merge there, too. >>> >>> On Wed, May 26, 2010 at 11:04 PM, Andreas Volz <li...@br...> >>> wrote: >>> > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: >>> > >>> > Hello Mat, >>> > >>> > nice to hear that it works with win32. >>> > >>> > Could you add your patches here: >>> > >>> > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 >>> > >>> > Yes I know many not applied patches there, but at least they're not >>> > lost. :-) >>> > >>> > I'll apply as fast as possible... >>> > >>> > regards >>> > Andreas >>> > >>> >> ---------- Forwarded message ---------- >>> >> From: Mat <mat...@gm...> >>> >> Date: Tue, May 18, 2010 at 2:56 AM >>> >> Subject: Patch for dbus-c++ win32 porting >>> >> To: kde...@kd... >>> >> >>> >> >>> >> Hi All, >>> >> I use dbus-c++ library in my programs and found that it's great >>> >> for c++ based projects. >>> >> >>> >> I tried to port dbus-c++ to win32, and have some progress these >>> >> days. The libdbusc++ can now work on my winxp :-) >>> >> ( for some simple examples, not yet try some real program, like >>> >> inkboard,...etc ) >>> >> >>> >> Patches are as attachment: >>> >> dbus-c++-src-commit.patch is for import into emerge dir. >>> >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ >>> >> works_for_win32.patch is a patch for dbus-c++-src[1] source code >>> >> >>> >> Could you help to review these works and give me some advice to >>> >> push the works go furthur? >>> >> >>> >> Thank you very much. >>> >> >>> >> sincerely, Mat. >>> >> >>> >> [1]. http://gitorious.org/dbus-cplusplus >>> >> [2]. dbus-c++-src-commit.patch >>> >> [3]. dbus-1.pc >>> >> [4]. works_for_win32.patch >>> > >>> > ------------------------------------------------------------------------------ >>> > >>> > _______________________________________________ >>> > dbus-cplusplus-devel mailing list >>> > dbu...@li... >>> > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel >>> > >>> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> dbus-cplusplus-devel mailing list >> dbu...@li... >> https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel >> > |
From: Mat <mat...@gm...> - 2010-05-29 14:25:18
|
On Sat, May 29, 2010 at 12:39 AM, Andreas Volz <li...@br...> wrote: > Am Thu, 27 May 2010 01:58:15 +0800 schrieb Mat: > > To be honest, I'm not sure. Currently I'm not that happy with GIT in > this project. Maybe I need to give it more time... > > My idea is to work on current patches and later decide about a SVN > move. For this little project I've not yet seen the advantage of GIT. No problem, I will propose my commits with patches first. p.s. You use git, I use git; you use svn, I use svn :-) sincerely, Mat. > > regards > Andreas > >> No problem. I just add a bug report in the sourceforge: >> >> https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 >> >> I am happy to see that bugs/reports were taken care of, great job and >> thank you!! >> >> sincerely, mat. >> >> p.s., I am learning gitorious in these days. If gitorious is prefered, >> please info me, I can also push patches via gitorious and propose >> merge there, too. >> >> On Wed, May 26, 2010 at 11:04 PM, Andreas Volz <li...@br...> >> wrote: >> > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: >> > >> > Hello Mat, >> > >> > nice to hear that it works with win32. >> > >> > Could you add your patches here: >> > >> > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 >> > >> > Yes I know many not applied patches there, but at least they're not >> > lost. :-) >> > >> > I'll apply as fast as possible... >> > >> > regards >> > Andreas >> > >> >> ---------- Forwarded message ---------- >> >> From: Mat <mat...@gm...> >> >> Date: Tue, May 18, 2010 at 2:56 AM >> >> Subject: Patch for dbus-c++ win32 porting >> >> To: kde...@kd... >> >> >> >> >> >> Hi All, >> >> I use dbus-c++ library in my programs and found that it's great >> >> for c++ based projects. >> >> >> >> I tried to port dbus-c++ to win32, and have some progress these >> >> days. The libdbusc++ can now work on my winxp :-) >> >> ( for some simple examples, not yet try some real program, like >> >> inkboard,...etc ) >> >> >> >> Patches are as attachment: >> >> dbus-c++-src-commit.patch is for import into emerge dir. >> >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ >> >> works_for_win32.patch is a patch for dbus-c++-src[1] source code >> >> >> >> Could you help to review these works and give me some advice to >> >> push the works go furthur? >> >> >> >> Thank you very much. >> >> >> >> sincerely, Mat. >> >> >> >> [1]. http://gitorious.org/dbus-cplusplus >> >> [2]. dbus-c++-src-commit.patch >> >> [3]. dbus-1.pc >> >> [4]. works_for_win32.patch >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > dbus-cplusplus-devel mailing list >> > dbu...@li... >> > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel >> > >> > > ------------------------------------------------------------------------------ > > _______________________________________________ > dbus-cplusplus-devel mailing list > dbu...@li... > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > |
From: Andreas V. <li...@br...> - 2010-05-28 16:40:13
|
Am Thu, 27 May 2010 01:58:15 +0800 schrieb Mat: To be honest, I'm not sure. Currently I'm not that happy with GIT in this project. Maybe I need to give it more time... My idea is to work on current patches and later decide about a SVN move. For this little project I've not yet seen the advantage of GIT. regards Andreas > No problem. I just add a bug report in the sourceforge: > > https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 > > I am happy to see that bugs/reports were taken care of, great job and > thank you!! > > sincerely, mat. > > p.s., I am learning gitorious in these days. If gitorious is prefered, > please info me, I can also push patches via gitorious and propose > merge there, too. > > On Wed, May 26, 2010 at 11:04 PM, Andreas Volz <li...@br...> > wrote: > > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: > > > > Hello Mat, > > > > nice to hear that it works with win32. > > > > Could you add your patches here: > > > > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 > > > > Yes I know many not applied patches there, but at least they're not > > lost. :-) > > > > I'll apply as fast as possible... > > > > regards > > Andreas > > > >> ---------- Forwarded message ---------- > >> From: Mat <mat...@gm...> > >> Date: Tue, May 18, 2010 at 2:56 AM > >> Subject: Patch for dbus-c++ win32 porting > >> To: kde...@kd... > >> > >> > >> Hi All, > >> I use dbus-c++ library in my programs and found that it's great > >> for c++ based projects. > >> > >> I tried to port dbus-c++ to win32, and have some progress these > >> days. The libdbusc++ can now work on my winxp :-) > >> ( for some simple examples, not yet try some real program, like > >> inkboard,...etc ) > >> > >> Patches are as attachment: > >> dbus-c++-src-commit.patch is for import into emerge dir. > >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ > >> works_for_win32.patch is a patch for dbus-c++-src[1] source code > >> > >> Could you help to review these works and give me some advice to > >> push the works go furthur? > >> > >> Thank you very much. > >> > >> sincerely, Mat. > >> > >> [1]. http://gitorious.org/dbus-cplusplus > >> [2]. dbus-c++-src-commit.patch > >> [3]. dbus-1.pc > >> [4]. works_for_win32.patch > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > dbus-cplusplus-devel mailing list > > dbu...@li... > > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > > > |
From: Mat <mat...@gm...> - 2010-05-26 17:58:42
|
No problem. I just add a bug report in the sourceforge: https://sourceforge.net/tracker/?func=detail&aid=3007491&group_id=236997&atid=1101684 I am happy to see that bugs/reports were taken care of, great job and thank you!! sincerely, mat. p.s., I am learning gitorious in these days. If gitorious is prefered, please info me, I can also push patches via gitorious and propose merge there, too. On Wed, May 26, 2010 at 11:04 PM, Andreas Volz <li...@br...> wrote: > Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: > > Hello Mat, > > nice to hear that it works with win32. > > Could you add your patches here: > > http://sourceforge.net/tracker/?group_id=236997&atid=1101684 > > Yes I know many not applied patches there, but at least they're not > lost. :-) > > I'll apply as fast as possible... > > regards > Andreas > >> ---------- Forwarded message ---------- >> From: Mat <mat...@gm...> >> Date: Tue, May 18, 2010 at 2:56 AM >> Subject: Patch for dbus-c++ win32 porting >> To: kde...@kd... >> >> >> Hi All, >> I use dbus-c++ library in my programs and found that it's great for >> c++ based projects. >> >> I tried to port dbus-c++ to win32, and have some progress these days. >> The libdbusc++ can now work on my winxp :-) >> ( for some simple examples, not yet try some real program, like >> inkboard,...etc ) >> >> Patches are as attachment: >> dbus-c++-src-commit.patch is for import into emerge dir. >> dbus-1.pc is for c:\kderoot\lib\pkgconfig\ >> works_for_win32.patch is a patch for dbus-c++-src[1] source code >> >> Could you help to review these works and give me some advice to push >> the works go furthur? >> >> Thank you very much. >> >> sincerely, Mat. >> >> [1]. http://gitorious.org/dbus-cplusplus >> [2]. dbus-c++-src-commit.patch >> [3]. dbus-1.pc >> [4]. works_for_win32.patch > > ------------------------------------------------------------------------------ > > _______________________________________________ > dbus-cplusplus-devel mailing list > dbu...@li... > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > |
From: Mat <mat...@gm...> - 2010-05-26 17:36:26
|
Thank you! I just find the gentoo related bug report and made a slight update. http://bugs.gentoo.org/show_bug.cgi?id=220767#c6 The ebuild detail is here: http://bugs.gentoo.org/attachment.cgi?id=233031 Please info me , if there is something need be refined, like homepage, urls...etc. :-) sincerely, Mat. On Wed, May 26, 2010 at 10:54 PM, Andreas Volz <li...@br...> wrote: > Am Sat, 1 May 2010 18:27:29 +0800 schrieb Mat: > >> Hi, >> >> I just made a simple gentoo package ( ebuild ) for dbus-c++. ( as >> attachment ) hope it bring some convenience >> :-) >> >> sincerely, Mat. > > Hello Mat, > > as I know from my old Gentoo days the Gentoo ebuilds are maintained in > the distribution repository. So thanks for posting here, but you should > open a bug report for new packages in Gentoo. > > regards > Andreas > > ------------------------------------------------------------------------------ > > _______________________________________________ > dbus-cplusplus-devel mailing list > dbu...@li... > https://lists.sourceforge.net/lists/listinfo/dbus-cplusplus-devel > |
From: Andreas V. <li...@br...> - 2010-05-26 15:10:15
|
Am Sat, 01 May 2010 15:15:34 -0700 schrieb Dana Goyette: Hello Dana, I also played around with bluez some month ago and had no problems so far. As far as I remember I got a phone book list from the mobile. This use cases worked. Which use case did you try? Could you please add this bug here: https://sourceforge.net/tracker/?group_id=236997&atid=1101682 regards Andreas > I'm trying to use the DBus-C++ libraries to talk to bluez, and I'm > finding that the dbus-c++ library keeps hanging on some futex even > after strace shows it successfully receiving all expected data. > Sometimes it hangs on calling DBus::ObjectProxy()... and other times > it hangs on calling GetProperties() for an object that was just > constructed. > > I have attached a log of gdb and strace -- however, due to the > "Heisenbug" behavior under gdb and strace, the two logs do not show > the exact same hang. Most notably, strace itself seems to sometimes > fix the behavior. > > Device::Device(DBus::Connection* connection, const ::DBus::Path& > path, Adapter* adapter, Manager * manager, map < string, > DBus::Variant> properties) > : ::org::bluez::Device_proxy() > , DBus::ObjectProxy(*connection, path, "org.bluez") <-- this is > device.cpp, line 22. > > If anyone has any advice for how to fix this hang, I would greatly > appreciate it. My libdbus-c++ package version is 0~20090907-1 on > 64-bit Ubuntu Lucid -- but I've now also manually built and installed > the "Unofficial GIT Variant" at > git://gitorious.org/dbus-cplusplus/mainline.git . > > Additionally, does anyone know how to set a shorter timeout for > method calls? The only "set" method I can find takes an > undocumented, private "Timeout::Internal" class. > > Thanks for any help you can give. > -- Dana > |
From: Andreas V. <li...@br...> - 2010-05-26 15:05:11
|
Am Tue, 18 May 2010 02:58:55 +0800 schrieb Mat: Hello Mat, nice to hear that it works with win32. Could you add your patches here: http://sourceforge.net/tracker/?group_id=236997&atid=1101684 Yes I know many not applied patches there, but at least they're not lost. :-) I'll apply as fast as possible... regards Andreas > ---------- Forwarded message ---------- > From: Mat <mat...@gm...> > Date: Tue, May 18, 2010 at 2:56 AM > Subject: Patch for dbus-c++ win32 porting > To: kde...@kd... > > > Hi All, > I use dbus-c++ library in my programs and found that it's great for > c++ based projects. > > I tried to port dbus-c++ to win32, and have some progress these days. > The libdbusc++ can now work on my winxp :-) > ( for some simple examples, not yet try some real program, like > inkboard,...etc ) > > Patches are as attachment: > dbus-c++-src-commit.patch is for import into emerge dir. > dbus-1.pc is for c:\kderoot\lib\pkgconfig\ > works_for_win32.patch is a patch for dbus-c++-src[1] source code > > Could you help to review these works and give me some advice to push > the works go furthur? > > Thank you very much. > > sincerely, Mat. > > [1]. http://gitorious.org/dbus-cplusplus > [2]. dbus-c++-src-commit.patch > [3]. dbus-1.pc > [4]. works_for_win32.patch |
From: Andreas V. <li...@br...> - 2010-05-26 14:55:10
|
Am Sat, 1 May 2010 18:27:29 +0800 schrieb Mat: > Hi, > > I just made a simple gentoo package ( ebuild ) for dbus-c++. ( as > attachment ) hope it bring some convenience > :-) > > sincerely, Mat. Hello Mat, as I know from my old Gentoo days the Gentoo ebuilds are maintained in the distribution repository. So thanks for posting here, but you should open a bug report for new packages in Gentoo. regards Andreas |
From: Mat <mat...@gm...> - 2010-05-17 18:59:24
|
---------- Forwarded message ---------- From: Mat <mat...@gm...> Date: Tue, May 18, 2010 at 2:56 AM Subject: Patch for dbus-c++ win32 porting To: kde...@kd... Hi All, I use dbus-c++ library in my programs and found that it's great for c++ based projects. I tried to port dbus-c++ to win32, and have some progress these days. The libdbusc++ can now work on my winxp :-) ( for some simple examples, not yet try some real program, like inkboard,...etc ) Patches are as attachment: dbus-c++-src-commit.patch is for import into emerge dir. dbus-1.pc is for c:\kderoot\lib\pkgconfig\ works_for_win32.patch is a patch for dbus-c++-src[1] source code Could you help to review these works and give me some advice to push the works go furthur? Thank you very much. sincerely, Mat. [1]. http://gitorious.org/dbus-cplusplus [2]. dbus-c++-src-commit.patch [3]. dbus-1.pc [4]. works_for_win32.patch |
From: Andreas V. <li...@br...> - 2010-05-08 15:40:08
|
Hello together, I like to announce the relaunch of the dbus-c++ wiki: https://sourceforge.net/apps/mediawiki/dbus-cplusplus/index.php From now on the old project hosting on freedesktop.org isn't used any longer. The GIT repository there still exists, but is requested for removal. I had some problems to upload my new ssh keys to freedesktop. The original author didn't respond for a long time and I decided to continue on SourceForge. The GIT repository is still on Gitourous, but I thought about moving to SourceForge services (SVN) also for this. The old freedesktop branch will be commited to a new repository on sf.net in future for history references. But anyway, the difference between both branches is only the code generator and I don't expect it to have much problems. Maybe it needs some more testing in areas where I don't use it. Please do any bug reports and patches in future only on the repository stated on the wiki page (currently Gitorious, later maybe sf.net). I hope now with this decision my motivation is bigger to maintain dbus-c++. And it's also easier for me to add new developers to the project. The help I need at most is someone integrating a good unit testing framework and writing some tests. Currently I'm in fear of changing areas in the generator that I don't use in my applications. I never know if I don't kill any ones functionality. :-P The project is still alive! regards Andreas |
From: Mat <mat...@gm...> - 2010-05-05 10:01:44
|
I just surveyed the dbus's windows implementations. I found that dbus has a poll wrapper: _dbus_poll() The code details is show below: http://cgit.freedesktop.org/dbus/dbus/tree/dbus/dbus-sysdeps-win.c?h=dbus-1.2.4permissive I guess sys/poll.h could not be solved via some convenient header, and have to have a win32 wrapper implementation for it. On Tue, May 4, 2010 at 6:34 PM, Mat <mat...@gm...> wrote: > The related code blocks seems to be: > > src/eventloop.cpp's => DefaultMainLoop::dispatch() > src/eventloop-integration.cpp's => BusWatch::BusWatch() > src/eventloop-integration.cpp's => BusDispatcher::watch_ready() > > > On Tue, May 4, 2010 at 4:55 PM, Mat <mat...@gm...> wrote: >> Now I encountered another compilation error caused by missing "sys/poll.h" >> >> The error message is like: >> =================== >> /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src >> -I.. -Ic:/kderoot/include >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include >> -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT >> eventloop.lo -MD -MP -MF .deps/eventloop.Tpo -c -o eventloop.lo >> /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp >> libtool: compile: g++ -DHAVE_CONFIG_H -I. >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src >> -I.. -Ic:/kderoot/include >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include >> -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT >> eventloop.lo -MD -MP -MF .deps/eventloop.Tpo -c >> /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp >> -DDLL_EXPORT -DPIC -o .libs/eventloop.o >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:39:22: >> error: sys/poll.h: No such file or directory >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp: >> In member function 'virtual void DBus::DefaultMainLoop::dispatch()': >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:165: >> error: 'pollfd' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:165: >> error: expected ';' before 'fds' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:173: >> error: 'fds' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:182: >> error: 'fds' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: >> error: 'POLLIN' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: >> error: 'POLLOUT' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: >> error: 'POLLPRI' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:208: >> error: 'fds' was not declared in this scope >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:208: >> error: 'poll' was not declared in this scope >> make[2]: *** [eventloop.lo] Error 1 >> make[2]: Leaving directory >> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory >> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' >> make: *** [all] Error 2 >> =================== >> ( details are in attachments ) >> >> Would somebody like to help to solve this problem or some advice for >> this problem? >> Thank you very much. >> >> sincerely, Mat. >> >> >> On Tue, May 4, 2010 at 4:49 PM, Mat <mat...@gm...> wrote: >>> I found this problem was caused by "interface" reserved word. >>> >>> http://article.gmane.org/gmane.comp.gnu.mingw.announce/1820 >>> >>> ============= >>>>Comment By: Danny Smith (dannysmith) >>> Date: 2009-01-15 19:41 >>> >>> Message: >>> Hello Alexandr >>> Thanks for the test case. >>> I believe the bug is cause by the preprocessor definition of the >>> identifier "interface" as "struct" in the w32api header basetype.h (see >>> defs starting at line 43). >>> >>> Try adding >>> #undef interface >>> to qfutureinterface.h >>> >>> Danny >>> ============= >>> >>> I made a dirty hack to add "#undef interface" on the header of every >>> src/*.cpp, and it did solve the compilation error. >>> >>> sincerely, Mat. >>> >>> >>> On Sun, May 2, 2010 at 3:31 PM, Mat <mat...@gm...> wrote: >>>> BTW, The source I use is the unofficial variant: >>>> >>>> http://gitorious.org/dbus-cplusplus >>>> >>>> >>>> On Sun, May 2, 2010 at 3:28 PM, Mat <mat...@gm...> wrote: >>>>> Hi all, >>>>> >>>>> I am trying to port dbus-c++-0.5.0 to kde-windows ( via kde-windows' emerge ). >>>>> After some works, I got some problem of compilation like... >>>>> >>>>> === >>>>> libtool: compile: g++ -DHAVE_CONFIG_H -I. >>>>> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src >>>>> -I.. -Ic:/kderoot/include >>>>> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include >>>>> -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT >>>>> object.lo -MD -MP -MF .deps/object.Tpo -c >>>>> /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp >>>>> -DDLL_EXPORT -DPIC -o .libs/object.o >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >>>>> In member function 'virtual bool >>>>> DBus::ObjectAdaptor::handle_message(const DBus::Message&)': >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >>>>> error: expected unqualified-id before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >>>>> error: expected initializer before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:205: >>>>> error: expected primary-expression before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:207: >>>>> error: expected primary-expression before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >>>>> In member function 'virtual bool >>>>> DBus::ObjectProxy::handle_message(const DBus::Message&)': >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >>>>> error: expected unqualified-id before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >>>>> error: expected initializer before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:360: >>>>> error: expected primary-expression before 'struct' >>>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:362: >>>>> error: expected primary-expression before 'struct' >>>>> make[2]: *** [object.lo] Error 1 >>>>> make[2]: Leaving directory >>>>> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' >>>>> make[1]: *** [all-recursive] Error 1 >>>>> make[1]: Leaving directory >>>>> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' >>>>> make: *** [all] Error >>>>> ==== >>>>> ( details are in attachments ) >>>>> >>>>> Would somebody like to help me to solve this problem or some advice >>>>> for this problem? >>>>> >>>>> Thank you very much. >>>>> >>>>> sincerely, Mat. >>>>> >>>> >>> >> > |
From: Mat <mat...@gm...> - 2010-05-04 10:35:06
|
The related code blocks seems to be: src/eventloop.cpp's => DefaultMainLoop::dispatch() src/eventloop-integration.cpp's => BusWatch::BusWatch() src/eventloop-integration.cpp's => BusDispatcher::watch_ready() On Tue, May 4, 2010 at 4:55 PM, Mat <mat...@gm...> wrote: > Now I encountered another compilation error caused by missing "sys/poll.h" > > The error message is like: > =================== > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src > -I.. -Ic:/kderoot/include > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include > -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT > eventloop.lo -MD -MP -MF .deps/eventloop.Tpo -c -o eventloop.lo > /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src > -I.. -Ic:/kderoot/include > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include > -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT > eventloop.lo -MD -MP -MF .deps/eventloop.Tpo -c > /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp > -DDLL_EXPORT -DPIC -o .libs/eventloop.o > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:39:22: > error: sys/poll.h: No such file or directory > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp: > In member function 'virtual void DBus::DefaultMainLoop::dispatch()': > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:165: > error: 'pollfd' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:165: > error: expected ';' before 'fds' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:173: > error: 'fds' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:182: > error: 'fds' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: > error: 'POLLIN' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: > error: 'POLLOUT' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:183: > error: 'POLLPRI' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:208: > error: 'fds' was not declared in this scope > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/eventloop.cpp:208: > error: 'poll' was not declared in this scope > make[2]: *** [eventloop.lo] Error 1 > make[2]: Leaving directory > `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' > make: *** [all] Error 2 > =================== > ( details are in attachments ) > > Would somebody like to help to solve this problem or some advice for > this problem? > Thank you very much. > > sincerely, Mat. > > > On Tue, May 4, 2010 at 4:49 PM, Mat <mat...@gm...> wrote: >> I found this problem was caused by "interface" reserved word. >> >> http://article.gmane.org/gmane.comp.gnu.mingw.announce/1820 >> >> ============= >>>Comment By: Danny Smith (dannysmith) >> Date: 2009-01-15 19:41 >> >> Message: >> Hello Alexandr >> Thanks for the test case. >> I believe the bug is cause by the preprocessor definition of the >> identifier "interface" as "struct" in the w32api header basetype.h (see >> defs starting at line 43). >> >> Try adding >> #undef interface >> to qfutureinterface.h >> >> Danny >> ============= >> >> I made a dirty hack to add "#undef interface" on the header of every >> src/*.cpp, and it did solve the compilation error. >> >> sincerely, Mat. >> >> >> On Sun, May 2, 2010 at 3:31 PM, Mat <mat...@gm...> wrote: >>> BTW, The source I use is the unofficial variant: >>> >>> http://gitorious.org/dbus-cplusplus >>> >>> >>> On Sun, May 2, 2010 at 3:28 PM, Mat <mat...@gm...> wrote: >>>> Hi all, >>>> >>>> I am trying to port dbus-c++-0.5.0 to kde-windows ( via kde-windows' emerge ). >>>> After some works, I got some problem of compilation like... >>>> >>>> === >>>> libtool: compile: g++ -DHAVE_CONFIG_H -I. >>>> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src >>>> -I.. -Ic:/kderoot/include >>>> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include >>>> -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT >>>> object.lo -MD -MP -MF .deps/object.Tpo -c >>>> /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp >>>> -DDLL_EXPORT -DPIC -o .libs/object.o >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >>>> In member function 'virtual bool >>>> DBus::ObjectAdaptor::handle_message(const DBus::Message&)': >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >>>> error: expected unqualified-id before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >>>> error: expected initializer before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:205: >>>> error: expected primary-expression before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:207: >>>> error: expected primary-expression before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >>>> In member function 'virtual bool >>>> DBus::ObjectProxy::handle_message(const DBus::Message&)': >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >>>> error: expected unqualified-id before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >>>> error: expected initializer before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:360: >>>> error: expected primary-expression before 'struct' >>>> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:362: >>>> error: expected primary-expression before 'struct' >>>> make[2]: *** [object.lo] Error 1 >>>> make[2]: Leaving directory >>>> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' >>>> make[1]: *** [all-recursive] Error 1 >>>> make[1]: Leaving directory >>>> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' >>>> make: *** [all] Error >>>> ==== >>>> ( details are in attachments ) >>>> >>>> Would somebody like to help me to solve this problem or some advice >>>> for this problem? >>>> >>>> Thank you very much. >>>> >>>> sincerely, Mat. >>>> >>> >> > |
From: Mat <mat...@gm...> - 2010-05-04 08:49:57
|
I found this problem was caused by "interface" reserved word. http://article.gmane.org/gmane.comp.gnu.mingw.announce/1820 ============= >Comment By: Danny Smith (dannysmith) Date: 2009-01-15 19:41 Message: Hello Alexandr Thanks for the test case. I believe the bug is cause by the preprocessor definition of the identifier "interface" as "struct" in the w32api header basetype.h (see defs starting at line 43). Try adding #undef interface to qfutureinterface.h Danny ============= I made a dirty hack to add "#undef interface" on the header of every src/*.cpp, and it did solve the compilation error. sincerely, Mat. On Sun, May 2, 2010 at 3:31 PM, Mat <mat...@gm...> wrote: > BTW, The source I use is the unofficial variant: > > http://gitorious.org/dbus-cplusplus > > > On Sun, May 2, 2010 at 3:28 PM, Mat <mat...@gm...> wrote: >> Hi all, >> >> I am trying to port dbus-c++-0.5.0 to kde-windows ( via kde-windows' emerge ). >> After some works, I got some problem of compilation like... >> >> === >> libtool: compile: g++ -DHAVE_CONFIG_H -I. >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src >> -I.. -Ic:/kderoot/include >> -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include >> -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT >> object.lo -MD -MP -MF .deps/object.Tpo -c >> /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp >> -DDLL_EXPORT -DPIC -o .libs/object.o >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >> In member function 'virtual bool >> DBus::ObjectAdaptor::handle_message(const DBus::Message&)': >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >> error: expected unqualified-id before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: >> error: expected initializer before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:205: >> error: expected primary-expression before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:207: >> error: expected primary-expression before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: >> In member function 'virtual bool >> DBus::ObjectProxy::handle_message(const DBus::Message&)': >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >> error: expected unqualified-id before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: >> error: expected initializer before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:360: >> error: expected primary-expression before 'struct' >> c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:362: >> error: expected primary-expression before 'struct' >> make[2]: *** [object.lo] Error 1 >> make[2]: Leaving directory >> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory >> `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' >> make: *** [all] Error >> ==== >> ( details are in attachments ) >> >> Would somebody like to help me to solve this problem or some advice >> for this problem? >> >> Thank you very much. >> >> sincerely, Mat. >> > |
From: Mat <mat...@gm...> - 2010-05-02 07:31:30
|
BTW, The source I use is the unofficial variant: http://gitorious.org/dbus-cplusplus On Sun, May 2, 2010 at 3:28 PM, Mat <mat...@gm...> wrote: > Hi all, > > I am trying to port dbus-c++-0.5.0 to kde-windows ( via kde-windows' emerge ). > After some works, I got some problem of compilation like... > > === > libtool: compile: g++ -DHAVE_CONFIG_H -I. > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src > -I.. -Ic:/kderoot/include > -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include > -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT > object.lo -MD -MP -MF .deps/object.Tpo -c > /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp > -DDLL_EXPORT -DPIC -o .libs/object.o > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: > In member function 'virtual bool > DBus::ObjectAdaptor::handle_message(const DBus::Message&)': > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: > error: expected unqualified-id before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: > error: expected initializer before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:205: > error: expected primary-expression before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:207: > error: expected primary-expression before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: > In member function 'virtual bool > DBus::ObjectProxy::handle_message(const DBus::Message&)': > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: > error: expected unqualified-id before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: > error: expected initializer before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:360: > error: expected primary-expression before 'struct' > c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:362: > error: expected primary-expression before 'struct' > make[2]: *** [object.lo] Error 1 > make[2]: Leaving directory > `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' > make: *** [all] Error > ==== > ( details are in attachments ) > > Would somebody like to help me to solve this problem or some advice > for this problem? > > Thank you very much. > > sincerely, Mat. > |
From: Mat <mat...@gm...> - 2010-05-02 07:29:14
|
Hi all, I am trying to port dbus-c++-0.5.0 to kde-windows ( via kde-windows' emerge ). After some works, I got some problem of compilation like... === libtool: compile: g++ -DHAVE_CONFIG_H -I. -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src -I.. -Ic:/kderoot/include -I/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/include -I../include -I/c/kderoot/include -fvisibility=hidden -Wall -O3 -MT object.lo -MD -MP -MF .deps/object.Tpo -c /c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp -DDLL_EXPORT -DPIC -o .libs/object.o c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: In member function 'virtual bool DBus::ObjectAdaptor::handle_message(const DBus::Message&)': c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: error: expected unqualified-id before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:203: error: expected initializer before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:205: error: expected primary-expression before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:207: error: expected primary-expression before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp: In member function 'virtual bool DBus::ObjectProxy::handle_message(const DBus::Message&)': c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: error: expected unqualified-id before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:353: error: expected initializer before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:360: error: expected primary-expression before 'struct' c:/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/libdbus-c++-0.5.0/src/object.cpp:362: error: expected primary-expression before 'struct' make[2]: *** [object.lo] Error 1 make[2]: Leaving directory `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/c/kderoot/build/win32libs-sources/dbus-cpp-src-0.5.0/work/mingw4-RelWithDebInfo-0.5.0' make: *** [all] Error ==== ( details are in attachments ) Would somebody like to help me to solve this problem or some advice for this problem? Thank you very much. sincerely, Mat. |
From: Dana G. <dan...@gm...> - 2010-05-01 22:15:48
|
I'm trying to use the DBus-C++ libraries to talk to bluez, and I'm finding that the dbus-c++ library keeps hanging on some futex even after strace shows it successfully receiving all expected data. Sometimes it hangs on calling DBus::ObjectProxy()... and other times it hangs on calling GetProperties() for an object that was just constructed. I have attached a log of gdb and strace -- however, due to the "Heisenbug" behavior under gdb and strace, the two logs do not show the exact same hang. Most notably, strace itself seems to sometimes fix the behavior. Device::Device(DBus::Connection* connection, const ::DBus::Path& path, Adapter* adapter, Manager * manager, map < string, DBus::Variant> properties) : ::org::bluez::Device_proxy() , DBus::ObjectProxy(*connection, path, "org.bluez") <-- this is device.cpp, line 22. If anyone has any advice for how to fix this hang, I would greatly appreciate it. My libdbus-c++ package version is 0~20090907-1 on 64-bit Ubuntu Lucid -- but I've now also manually built and installed the "Unofficial GIT Variant" at git://gitorious.org/dbus-cplusplus/mainline.git . Additionally, does anyone know how to set a shorter timeout for method calls? The only "set" method I can find takes an undocumented, private "Timeout::Internal" class. Thanks for any help you can give. -- Dana |
From: Mat <mat...@gm...> - 2010-05-01 10:27:55
|
Hi, I just made a simple gentoo package ( ebuild ) for dbus-c++. ( as attachment ) hope it bring some convenience :-) sincerely, Mat. |