From mumismo at gmail.com Fri May 12 07:08:23 2006 From: mumismo at gmail.com (Jordi) Date: Fri May 12 07:06:20 2006 Subject: [Pyro-developers] better support for player 2.0 Message-ID: <200605121308.24462.raigengo@yahoo.es> While trying to compile pyrobot with support for player cameras I got some errors I attach a patch to solve them I've needed to add a new question to the configuration, so the include files for player can be found, I guess that most people is using /usr/local for player right now. BTW, I'm trying to make .deb packages out of pyrobot, when I finish I'll post the URL. I'm duplicating other people work? -- Jordi Polo -------------- next part -------------- A non-text attachment was scrubbed... Name: patch_pyrobot_20060512.diff Type: text/x-diff Size: 2741 bytes Desc: not available Url : http://emergent.brynmawr.edu/pipermail/pyro-developers/attachments/20060512/e5ebb8b1/patch_pyrobot_20060512.bin From mumismo at gmail.com Fri May 12 07:39:15 2006 From: mumismo at gmail.com (Jordi) Date: Fri May 12 07:37:27 2006 Subject: [Pyro-developers] installation from source Message-ID: <200605121339.16642.raigengo@yahoo.es> What's the preferred way to install pyrobotics from source?, it seems that the makefiles don't have install option. I want to install from source not from .rpm file because this way I can make debian packages that manages source and binary files. -- Jordi Polo From dblank at brynmawr.edu Fri May 12 08:11:30 2006 From: dblank at brynmawr.edu (dblank@brynmawr.edu) Date: Fri May 12 08:11:41 2006 Subject: [Pyro-developers] installation from source In-Reply-To: <200605121339.16642.raigengo@yahoo.es> References: <200605121339.16642.raigengo@yahoo.es> Message-ID: <60937.68.34.179.248.1147435890.squirrel@webmail.brynmawr.edu> > > What's the preferred way to install pyrobotics from source?, it seems that > the > makefiles don't have install option. > I want to install from source not from .rpm file because this way I can > make > debian packages that manages source and binary files. Jordi, If you know of a good, standard way of being able to install without a config system, then we'd love to have a makefile-based install. Maybe we just need to add a config-based layer? I guess we would need a way of overriding/setting bindir and installdir, and those would need to have defaults. The simpliest way would be to just hardcode those in the makefile. The RPM .spec file uses a different set of magic macros to set those. -Doug > -- > Jordi Polo > > > _______________________________________________ > Pyro-developers mailing list > Pyro-developers@emergent.brynmawr.edu > http://emergent.brynmawr.edu/mailman/listinfo/pyro-developers > From dblank at brynmawr.edu Fri May 12 08:14:56 2006 From: dblank at brynmawr.edu (dblank@brynmawr.edu) Date: Fri May 12 08:14:57 2006 Subject: [Pyro-developers] better support for player 2.0 In-Reply-To: <200605121308.24462.raigengo@yahoo.es> References: <200605121308.24462.raigengo@yahoo.es> Message-ID: <60938.68.34.179.248.1147436096.squirrel@webmail.brynmawr.edu> > > While trying to compile pyrobot with support for player cameras I got some > errors > I attach a patch to solve them > I've needed to add a new question to the configuration, so the include > files > for player can be found, I guess that most people is using /usr/local for > player right now. > > BTW, I'm trying to make .deb packages out of pyrobot, when I finish I'll > post > the URL. I'm duplicating other people work? Jordi, Great! We are looking forward to moving to Player-2.0 in the next few weeks for Player, Stage, and Gazebo. Any such hints or patches are gladly accepted. I don't know of anyone making deb packages, except through quick-n-dirty means (alien). Anything we can do to help on both of these fronts, we will. We'd be glad to host or link to the .debs from our main page. -Doug > -- > Jordi Polo > _______________________________________________ > Pyro-developers mailing list > Pyro-developers@emergent.brynmawr.edu > http://emergent.brynmawr.edu/mailman/listinfo/pyro-developers > From dblank at brynmawr.edu Fri May 12 10:53:55 2006 From: dblank at brynmawr.edu (Douglas S. Blank) Date: Fri May 12 10:54:13 2006 Subject: [Pyro-developers] better support for player 2.0 In-Reply-To: <200605121308.24462.raigengo@yahoo.es> References: <200605121308.24462.raigengo@yahoo.es> Message-ID: <1147445635.2690.19.camel@mightymouse.brynmawr.edu> I have applied Jordi's patch (with tweaks) which only affects the Player camera interface. The CVS version of Pyrobot now begins the transition to Player-2.0. For more information on the CVS version of Pyrobot, see: http://pyrorobotics.org/?page=PyroDeveloperCVS -Doug On Fri, 2006-05-12 at 13:08 +0200, Jordi wrote: > While trying to compile pyrobot with support for player cameras I got some > errors > I attach a patch to solve them > I've needed to add a new question to the configuration, so the include files > for player can be found, I guess that most people is using /usr/local for > player right now. > > BTW, I'm trying to make .deb packages out of pyrobot, when I finish I'll post > the URL. I'm duplicating other people work? > > -- > Jordi Polo > _______________________________________________ > Pyro-developers mailing list > Pyro-developers@emergent.brynmawr.edu > http://emergent.brynmawr.edu/mailman/listinfo/pyro-developers -- Douglas S. Blank Computer Science Assistant Professor Bryn Mawr College (610)526-6501 http://cs.brynmawr.edu/~dblank From dblank at brynmawr.edu Fri May 12 11:15:33 2006 From: dblank at brynmawr.edu (Douglas S. Blank) Date: Fri May 12 11:15:37 2006 Subject: [Pyro-developers] installation from source In-Reply-To: <200605121339.16642.raigengo@yahoo.es> References: <200605121339.16642.raigengo@yahoo.es> Message-ID: <1147446933.2690.30.camel@mightymouse.brynmawr.edu> On Fri, 2006-05-12 at 13:39 +0200, Jordi wrote: > What's the preferred way to install pyrobotics from source?, it seems that the > makefiles don't have install option. > I want to install from source not from .rpm file because this way I can make > debian packages that manages source and binary files. I should point out that George Sakkis did some work on making Pyrobot work with the standard distutils. You can see his comments here: http://emergent.brynmawr.edu/pipermail/pyro-developers/2005-February/thread.html He had a couple of suggestions on reorganization, and a first stab at making a setup.py. I couldn't get my head around distutils to build the C++ files and wrappers, and gave up. His main distutils files can be found here: http://compscitest.brynmawr.edu/cgi-bin/viewcvs.cgi/pyrobot/Attic/ One of his setup.py files can still be found in the pyrobot/camera/player directory. If someone knew how to do this, this would be the preferred method. -Doug > -- > Jordi Polo > > > _______________________________________________ > Pyro-developers mailing list > Pyro-developers@emergent.brynmawr.edu > http://emergent.brynmawr.edu/mailman/listinfo/pyro-developers > -- Douglas S. Blank Computer Science Assistant Professor Bryn Mawr College (610)526-6501 http://cs.brynmawr.edu/~dblank From mumismo at gmail.com Fri May 12 17:40:38 2006 From: mumismo at gmail.com (Jordi) Date: Fri May 12 17:38:31 2006 Subject: [Pyro-developers] installation from source In-Reply-To: <60937.68.34.179.248.1147435890.squirrel@webmail.brynmawr.edu> References: <200605121339.16642.raigengo@yahoo.es> <60937.68.34.179.248.1147435890.squirrel@webmail.brynmawr.edu> Message-ID: <200605122340.38967.raigengo@yahoo.es> > Jordi, > > If you know of a good, standard way of being able to install without a > config system, then we'd love to have a makefile-based install. Maybe we > just need to add a config-based layer? I guess we would need a way of > overriding/setting bindir and installdir, and those would need to have > defaults. The simpliest way would be to just hardcode those in the > makefile. I guess that autoconf/automake are not suitable for python. As Douglas pointed out Distutils are the preferred way with python packages, but I really have no idea about Distutils. Anyway... I'll try to get a look to Distutils. Why didn't get done before, too complex? > The RPM .spec file uses a different set of magic macros to set those. I suspected it -- Jordi Polo From w.richert at gmx.net Fri May 19 03:06:18 2006 From: w.richert at gmx.net (Willi Richert) Date: Fri May 19 03:06:43 2006 Subject: [Pyro-developers] Correcting circularlist.py Message-ID: <446D6E6A.8020309@gmx.net> Hi all, when testing the circularlist.py there appeared some errors: Instead of getItem the __getitem__ function should be used. diff /usr/lib/python2.3/site-packages/pyrobot/tools/circularlist.py /tmp/circularlist.py 66c66 < emptyList.getItem(4) --- > emptyList[4] 81c81 < print "Getting item at index two: ", clist.getItem(2) --- > print "Getting item at index two: ", clist[2] 98,99c98,99 < clist.getItem(0).addItem('a') < clist.getItem(0).addItem('b') --- > clist[0].addItem('a') > clist[0].addItem('b') 101c101 < clist.getItem(1).addItem('c') --- > clist[1].addItem('c') 103,105c103,105 < clist.getItem(2).addItem('d') < clist.getItem(2).addItem('e') < clist.getItem(2).addItem('f') --- > clist[2].addItem('d') > clist[2].addItem('e') > clist[2].addItem('f') From dblank at brynmawr.edu Fri May 19 09:27:37 2006 From: dblank at brynmawr.edu (dblank@brynmawr.edu) Date: Fri May 19 09:27:40 2006 Subject: [Pyro-developers] Correcting circularlist.py In-Reply-To: <446D6E6A.8020309@gmx.net> References: <446D6E6A.8020309@gmx.net> Message-ID: <46554.68.34.179.248.1148045257.squirrel@webmail.brynmawr.edu> > Hi all, > > when testing the circularlist.py there appeared some errors: Instead of > getItem the __getitem__ function should be used. Thanks! This has now been updated in CVS. Also, while I was in there, I added an .__iter__() and .next() methods, and renamed .next to .nextPos. So you can: for i in clist: print i which is an infinite loop. .next was renamed .nextPos so that .next() can implement the correct method to remain compatible with other iterators. pyrobot/brain/ravq.py and pyrobot/brain/governor.py had to be adjusted slightly. -Doug > diff /usr/lib/python2.3/site-packages/pyrobot/tools/circularlist.py > /tmp/circularlist.py > 66c66 > < emptyList.getItem(4) > --- > > emptyList[4] > 81c81 > < print "Getting item at index two: ", clist.getItem(2) > --- > > print "Getting item at index two: ", clist[2] > 98,99c98,99 > < clist.getItem(0).addItem('a') > < clist.getItem(0).addItem('b') > --- > > clist[0].addItem('a') > > clist[0].addItem('b') > 101c101 > < clist.getItem(1).addItem('c') > --- > > clist[1].addItem('c') > 103,105c103,105 > < clist.getItem(2).addItem('d') > < clist.getItem(2).addItem('e') > < clist.getItem(2).addItem('f') > --- > > clist[2].addItem('d') > > clist[2].addItem('e') > > clist[2].addItem('f')