witme-ferris Mailing List for witme
Status: Beta
Brought to you by:
monkeyiq
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(4) |
2003 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(2) |
2004 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(7) |
2005 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(3) |
Aug
(5) |
Sep
(2) |
Oct
(2) |
Nov
(17) |
Dec
(8) |
2006 |
Jan
|
Feb
|
Mar
(3) |
Apr
(2) |
May
(2) |
Jun
(3) |
Jul
(8) |
Aug
(9) |
Sep
(4) |
Oct
(9) |
Nov
(13) |
Dec
(30) |
2007 |
Jan
(15) |
Feb
(13) |
Mar
(7) |
Apr
(63) |
May
(26) |
Jun
(7) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
From: lukash <lu...@em...> - 2010-10-27 16:17:58
|
On Tue, 26 Oct 2010 12:21:51 +0200 (CEST) Ben Martin <mon...@us...> wrote: > On Mon, 2010-10-25 at 17:31 +0200, lukash wrote: > > On Sun, 24 Oct 2010 18:01:33 +0200 (CEST) Ben Martin > > <mon...@us...> wrote: > > > > > > > > > I now have an n900 myself and packages here: > > > http://fuuko.libferris.com/maemo/n900/repository/ > > > > And you tell me that now? :) Well, at least I've done the excersize. > > Sorry about that again :( No worries :) I guess I should check your blog more often.. > > > > > > If you are interested the first move might be to wrap for Qt access, so > > > a fh_context can be accessed from QML and a custom QTreemodel for the > > > filesystem can be used to navigate around. I have both of these on my > > > list of things TODO, but given my time commitments for the next few > > > months I'm not sure they will materialize before xmas. > > > > I just had to read up on what's QML, now I'm not sure what you mean by > > accessing fh_context from it? (just having only a faint idea what > > fh_context is) > > The main thing is getting a wrapper that exposes fh_context (which is > the file/dir abstraction in libferris) as a QObject child. This way you > can create, setup and interact with those objects from QML/Javascript. > I see. In QT, there are the QFile and QDir classes, so this would be their equivalent (I find the name 'context' a bit misleading, though it may just be me not understanding the concept well enough). > > > > My plan was to implement QFSFileEngine, which is the low level class > > for accessing a file system. That would give me access from all the > > highlevel classes, and make also my file manipulation methods work, I > > call QFSFileEngine methods directly from them. > > You might also like to directly access your QFSFileEngine subclass at > times. In libferris a whole lot is exposed as extended attributes > (key/value pairs on files). For example, you can do > > fh_context myFile = Resolve("file://tmp/boo.txt"); > string v = getStrAttr( myFile, "md5", "" ); > cerr << "md5 is:" << v << endl; > > To get the checksum. To see what attributes are available for a file you > can do this: > fls --show-ea=ea-names /tmp/boo.txt > But you will likely want to pipe it to tr to change , to \n with the > huge range of attributes these days. > > This is why I was also thinking about a custom QAbstractItemModel which > exposes all the attributes for files to Qt. Such a model could be > accessed from QML/Javascript. I have such a custom data model for GTK+2 > which is used by my "ego" file manager and works well allowing sort by > one or more attributes etc. If the model knows the attributes then you > should be able to do some quite powerful stuff with filtering and > sorting of views on the device. > > > > > I'm open for any advice though, and any links on some info about > > wrapping libferris are most welcome :) > > I'm guessing a QObject subclass which keeps a fh_context as private > data. For a QFSFileEngine see also Shell.hh for create file, dir, link, > and touch. fileTime() is getattribute() with ctime, mtime, and atime. > > open() is getIOStream() with the corrosponding std ioflags. You would > have to cache the fh_iosteam in the class for read(), pos(), close() etc > to use. > > owner() and ownerId() are available through attributes, for the group > substitute "group" for "user" in the following: > $ fls --show-ea=name,user-owner-name,user-owner-number Shell.hh > Shell.hh ben 500 > > getSize() is the "size" attibute > > For setting the size there is some support for preallocation, or you > have to fall back to doing it through the std::iostreams interface, for > example: > fh_iostream ss = myFile->getIOStream( trunc ); > ss.write( zero to size ); > Thanks for the heads up :) > > > > > I haven't checked, but I suspect you havent uploaded your packages to > > the official maemo repositories? Any plans on doing that? I'll need > > them there when I want to release my application... > > I would like that. If you would like to be the guy to moves those across > into extras that would likely speed things up a bunch. See also my blog > post on soprano which would have to be fixed in the extras repo in order > for some parts of libferris to work as expected. > > Ok, I've checked out your blog. I can upload them to extras, if you don't mind me being the maintainer? Or perhaps the maintanership can be changed later. But for that I think I will need a git repository for the components with the packaging, so that I can checkout them regularly and also eventually send you patches/pull requests for some packaging fixes if needed. How do you feel about that? cheers lukash |
From: Ben M. <mon...@us...> - 2010-10-26 10:22:11
|
On Mon, 2010-10-25 at 17:31 +0200, lukash wrote: > On Sun, 24 Oct 2010 18:01:33 +0200 (CEST) Ben Martin > <mon...@us...> wrote: > > > > > I now have an n900 myself and packages here: > > http://fuuko.libferris.com/maemo/n900/repository/ > > And you tell me that now? :) Well, at least I've done the excersize. Sorry about that again :( > > > If you are interested the first move might be to wrap for Qt access, so > > a fh_context can be accessed from QML and a custom QTreemodel for the > > filesystem can be used to navigate around. I have both of these on my > > list of things TODO, but given my time commitments for the next few > > months I'm not sure they will materialize before xmas. > > I just had to read up on what's QML, now I'm not sure what you mean by > accessing fh_context from it? (just having only a faint idea what > fh_context is) The main thing is getting a wrapper that exposes fh_context (which is the file/dir abstraction in libferris) as a QObject child. This way you can create, setup and interact with those objects from QML/Javascript. > > My plan was to implement QFSFileEngine, which is the low level class > for accessing a file system. That would give me access from all the > highlevel classes, and make also my file manipulation methods work, I > call QFSFileEngine methods directly from them. You might also like to directly access your QFSFileEngine subclass at times. In libferris a whole lot is exposed as extended attributes (key/value pairs on files). For example, you can do fh_context myFile = Resolve("file://tmp/boo.txt"); string v = getStrAttr( myFile, "md5", "" ); cerr << "md5 is:" << v << endl; To get the checksum. To see what attributes are available for a file you can do this: fls --show-ea=ea-names /tmp/boo.txt But you will likely want to pipe it to tr to change , to \n with the huge range of attributes these days. This is why I was also thinking about a custom QAbstractItemModel which exposes all the attributes for files to Qt. Such a model could be accessed from QML/Javascript. I have such a custom data model for GTK+2 which is used by my "ego" file manager and works well allowing sort by one or more attributes etc. If the model knows the attributes then you should be able to do some quite powerful stuff with filtering and sorting of views on the device. > > I'm open for any advice though, and any links on some info about > wrapping libferris are most welcome :) I'm guessing a QObject subclass which keeps a fh_context as private data. For a QFSFileEngine see also Shell.hh for create file, dir, link, and touch. fileTime() is getattribute() with ctime, mtime, and atime. open() is getIOStream() with the corrosponding std ioflags. You would have to cache the fh_iosteam in the class for read(), pos(), close() etc to use. owner() and ownerId() are available through attributes, for the group substitute "group" for "user" in the following: $ fls --show-ea=name,user-owner-name,user-owner-number Shell.hh Shell.hh ben 500 getSize() is the "size" attibute For setting the size there is some support for preallocation, or you have to fall back to doing it through the std::iostreams interface, for example: fh_iostream ss = myFile->getIOStream( trunc ); ss.write( zero to size ); > > I haven't checked, but I suspect you havent uploaded your packages to > the official maemo repositories? Any plans on doing that? I'll need > them there when I want to release my application... I would like that. If you would like to be the guy to moves those across into extras that would likely speed things up a bunch. See also my blog post on soprano which would have to be fixed in the extras repo in order for some parts of libferris to work as expected. |
From: lukash <lu...@em...> - 2010-10-25 15:32:16
|
On Sun, 24 Oct 2010 18:01:33 +0200 (CEST) Ben Martin <mon...@us...> wrote: > Hi, > Sorry, I thought I'd replied :/ Your message arrived just as I was > landing from a long flight, jet lagged, and had a conference to race > to... a bad combination it seems. No problem. > > I now have an n900 myself and packages here: > http://fuuko.libferris.com/maemo/n900/repository/ And you tell me that now? :) Well, at least I've done the excersize. > If you are interested the first move might be to wrap for Qt access, so > a fh_context can be accessed from QML and a custom QTreemodel for the > filesystem can be used to navigate around. I have both of these on my > list of things TODO, but given my time commitments for the next few > months I'm not sure they will materialize before xmas. I just had to read up on what's QML, now I'm not sure what you mean by accessing fh_context from it? (just having only a faint idea what fh_context is) My plan was to implement QFSFileEngine, which is the low level class for accessing a file system. That would give me access from all the highlevel classes, and make also my file manipulation methods work, I call QFSFileEngine methods directly from them. I'm open for any advice though, and any links on some info about wrapping libferris are most welcome :) I haven't checked, but I suspect you havent uploaded your packages to the official maemo repositories? Any plans on doing that? I'll need them there when I want to release my application... > Have fun with libferris on the device :) > Thanks! lukash > > On Fri, 2010-10-22 at 21:34 +0200, lukash wrote: > > Hi Ben, > > > > just writing you in case you somehow missed the message I sent to the > > mailing list. You've been quick to reply before, so... I wanted to do > > some work on it this weekend, so your advice would be most welcome. If > > there's another reason for you not replying me, please ignore this. > > Thanks. > > |
From: Ben M. <mon...@us...> - 2010-10-24 16:33:50
|
On Sun, 2010-10-17 at 21:54 +0200, lu...@em... wrote: > Hi again, > > its me trying to build libferris on Maemo. I've had a 'short' vacation and now > I'm back :) Just to double check, I sent you a mail which might have been consumed by your spam filter... |
From: Ben M. <mon...@us...> - 2010-10-24 16:33:45
|
Up for all to enjoy.... http://fuuko.libferris.com/maemo/n900/repository/ |
From: <lu...@em...> - 2010-10-17 19:54:30
|
Hi again, its me trying to build libferris on Maemo. I've had a 'short' vacation and now I'm back :) I managed to build packages for all dependencies (at least everything configure script strictly required) of libferris. I didn't have any bigger trouble, only had to bump versions of some packages to latest (as opposed to using the ones you had the debian packaging for), they wouldn't build against my libsigc++-2.0-dev otherwise. So I bumped all (or most of them) to newest for a good measure. But when building libferris-1.5.0 itself, I'm running into compilation errors I don't understand. There is some code which seems to be written for Xerces 3.0 involved. I'm not really sure. It just seems quite wrong, but you might know what it is. I'm using libxerces27-dev-2.7.0-3. Please see the attached log. cheers lukash |
From: lukash <lu...@em...> - 2010-06-21 14:59:49
|
On Tue, 15 Jun 2010 12:40:39 +0200 (CEST) Ben Martin <mon...@us...> wrote: > On Sat, 2010-06-12 at 23:45 +0200, lukash wrote: > > Sorry for the delay, I was busy with other things... > > > > On Sun, 06 Jun 2010 00:49:30 +0200 (CEST) Ben Martin > > <mon...@us...> wrote: > > > > > > > > The configure will try to build code for anything it detects on the > > > system. the Libferris library relies on a few other static libs that are > > > built during the build. However, if you cd Ferris && make install then > > > you will get just the libferris.so and headers. > > > > > > > I can't however just do this, right? I need to run ./configure before? > > indeed. > > > > > I installed xerces-c-2.7.0 on my Funtoo box. But right after it I ran > > into another problem with fampp2. Its in the Funtoo (Gentoo) "repo", > > but it depends on ferrisloki-3.0.1 which failed to build (see attached > > ferrisloki_build_log if interested). > > hmm, I'll have to dig into that when I get a moment. It builds fine for > me on Fedora 11,12,13. > > You could also try the latest (3.0.3) of ferrisloki from source... > http://sourceforge.net/projects/witme/files/ > I'll try that when time permits.. > > > > So I figure if its this problematic to build on a laptop, it will be > > even worse for maemo. I thought I'd have a look at the packages you > > made for Chinook (was it Chinook?), but I can't find them anywhere. Are > > they in the official repos? If I had source packages for those, it > > should not be hard to get them to work on N900? > > http://fuuko.libferris.com/maemo/repository/binary/ > > I can upload snapshots of the source directories that made these if you > like. Mostly its just plain old debian packaging. I would really appreciate that, seems like you don't make the source packages? Does it also contain the build scripts that work in maemo? If not could you upload those too? That would be great... It seems like it has a whole lot of dependencies, I really wonder if I'll be able to put it together... > > > > > cheers > > lukash > |
From: Ben M. <mon...@us...> - 2010-06-15 10:41:11
|
On Sat, 2010-06-12 at 23:45 +0200, lukash wrote: > Sorry for the delay, I was busy with other things... > > On Sun, 06 Jun 2010 00:49:30 +0200 (CEST) Ben Martin > <mon...@us...> wrote: > > > > > The configure will try to build code for anything it detects on the > > system. the Libferris library relies on a few other static libs that are > > built during the build. However, if you cd Ferris && make install then > > you will get just the libferris.so and headers. > > > > I can't however just do this, right? I need to run ./configure before? indeed. > > I installed xerces-c-2.7.0 on my Funtoo box. But right after it I ran > into another problem with fampp2. Its in the Funtoo (Gentoo) "repo", > but it depends on ferrisloki-3.0.1 which failed to build (see attached > ferrisloki_build_log if interested). hmm, I'll have to dig into that when I get a moment. It builds fine for me on Fedora 11,12,13. You could also try the latest (3.0.3) of ferrisloki from source... http://sourceforge.net/projects/witme/files/ > > So I figure if its this problematic to build on a laptop, it will be > even worse for maemo. I thought I'd have a look at the packages you > made for Chinook (was it Chinook?), but I can't find them anywhere. Are > they in the official repos? If I had source packages for those, it > should not be hard to get them to work on N900? http://fuuko.libferris.com/maemo/repository/binary/ I can upload snapshots of the source directories that made these if you like. Mostly its just plain old debian packaging. > > cheers > lukash |
From: lukash <lu...@em...> - 2010-06-12 22:02:59
|
Sorry for the delay, I was busy with other things... On Sun, 06 Jun 2010 00:49:30 +0200 (CEST) Ben Martin <mon...@us...> wrote: > > The configure will try to build code for anything it detects on the > system. the Libferris library relies on a few other static libs that are > built during the build. However, if you cd Ferris && make install then > you will get just the libferris.so and headers. > I can't however just do this, right? I need to run ./configure before? I installed xerces-c-2.7.0 on my Funtoo box. But right after it I ran into another problem with fampp2. Its in the Funtoo (Gentoo) "repo", but it depends on ferrisloki-3.0.1 which failed to build (see attached ferrisloki_build_log if interested). So I figure if its this problematic to build on a laptop, it will be even worse for maemo. I thought I'd have a look at the packages you made for Chinook (was it Chinook?), but I can't find them anywhere. Are they in the official repos? If I had source packages for those, it should not be hard to get them to work on N900? cheers lukash |
From: Ben M. <mon...@us...> - 2010-06-04 09:03:53
|
On other tip, if you decide to poke around, see Ferris/ClipAPI.hh. This is used by many command line clients and the ego file manager. You can Cut(), Copy() and Paste() files and subprocesses are created to perform these actions. Of course, you still have to handle rename and delete, but you get move and copy at low cost. At some stage I'll be tinkering with Qt clients for ferrismv, ferriscp, and ferrisrm, which will make things easier... and of course, when I get an n900 and some time there will be debs for libferris on that platform :) On Thu, 2010-06-03 at 19:43 +1000, Ben Martin wrote: > On Thu, 2010-06-03 at 11:16 +0200, lukash wrote: > > Hi all, > > > > I am developing a file manager for N900. At the moment, I'm trying to > > put together the basic functionality quickly. I'm using QT and it has a > > pretty suitable file system model already. It just doesn't have good > > enough move/copy/delete functions that would support interactive thread > > communication. It seems like a nontrivial issue, so I would like to use > > some existing solution.. > > The copy/remove/move code in libferris uses mainloop callbacks instead > of threading. Things can still work interactively, eg, the GTK+2 clients > gfcp, gfmv, gfrm etc. > > > > > I've spent a lot of time searching for some suitable implementation, > > until I bumped into libferris. Now it seems like I found a diamond in > > piles of mud :) But as I was reading up on it, my hopes went up and > > down a few times... > > > > First, I couldn't find any suitable documentation. Is there any? From > > some papers I figured libferris really does implement these functions I > > need the most. I also got the feeling that it would be perfect for > > implementing my own QFileSystemModel-like class later on and greatly > > extend the features of my FM. > > Indeed, the code for most of what the coreutils cp, mv, rm, etc do is > contained in libferris.so. Both the ferriscp and GTK+2 gfcp apps use the > same codepaths in libferris to perform their task. > > Most of the documentation is in the form of papers and articles > (linux.com, linuxjournal, linux format etc, etc). > > > > > But from the website I didn't really gather what actually libferris is > > and how to use it... So I downloaded the sources. And that was the time > > when I actually got scared :) What is it? How do I use it? It seems to > > be something that lives its own live. Just from the readme I gathered > > its not simple to even install it, though I still have no clue what it > > does. I would be very happy if I just had a library to link against... > > Sorry about the miscommunication. Libferris is a virtual filesystem. It > also includes rich metadata support, common code like recursive copy, > and many posix clients like ferrisls, ferriscp etc. along with GTK+2 > interfaces to that functionality. Since libferris can mount many things, > it can be non trivial to build. But much of the functioanlity is > optional so you should be able to trim it down to a small build. > > I make packages for Fedora and maemo to help with installation. Nothing > for the n900 yet as I lack the device to test it on. Yes, I could test > on scratchbox but that's another story. > > The code in Ferris/ links to libferris.so which is the library you seek. > You'll have to read the ferriscp code to see how to use the API though. > > > > > Then I also found out that it was already ported to Maemo 2008, which > > is great news. But it seemed like it was not so easy to actually port > > it, hinting again at libferris being far too complex... > > Well, the main things are the xerces-c usage there. If/when I port to > using Qt's XML code then making maemo and symbian ports should be easier > still. > > > > > What do you think, is libferris for me? Can you give me advice on how > > to use it? > > Well, it might be for you, its hard to say. There is no huge company > behind libferris to make it easy to use or install. So to use it's API > you are going to have to read source and get your hands dirty, but if > that's fine with you then libferris might be for you :) > > > > > Thanks in advance! > > > > lukash > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ Witme-ferris mailing list Wit...@li... https://lists.sourceforge.net/lists/listinfo/witme-ferris |
From: Ben M. <mon...@us...> - 2010-06-03 09:44:21
|
On Thu, 2010-06-03 at 11:16 +0200, lukash wrote: > Hi all, > > I am developing a file manager for N900. At the moment, I'm trying to > put together the basic functionality quickly. I'm using QT and it has a > pretty suitable file system model already. It just doesn't have good > enough move/copy/delete functions that would support interactive thread > communication. It seems like a nontrivial issue, so I would like to use > some existing solution.. The copy/remove/move code in libferris uses mainloop callbacks instead of threading. Things can still work interactively, eg, the GTK+2 clients gfcp, gfmv, gfrm etc. > > I've spent a lot of time searching for some suitable implementation, > until I bumped into libferris. Now it seems like I found a diamond in > piles of mud :) But as I was reading up on it, my hopes went up and > down a few times... > > First, I couldn't find any suitable documentation. Is there any? From > some papers I figured libferris really does implement these functions I > need the most. I also got the feeling that it would be perfect for > implementing my own QFileSystemModel-like class later on and greatly > extend the features of my FM. Indeed, the code for most of what the coreutils cp, mv, rm, etc do is contained in libferris.so. Both the ferriscp and GTK+2 gfcp apps use the same codepaths in libferris to perform their task. Most of the documentation is in the form of papers and articles (linux.com, linuxjournal, linux format etc, etc). > > But from the website I didn't really gather what actually libferris is > and how to use it... So I downloaded the sources. And that was the time > when I actually got scared :) What is it? How do I use it? It seems to > be something that lives its own live. Just from the readme I gathered > its not simple to even install it, though I still have no clue what it > does. I would be very happy if I just had a library to link against... Sorry about the miscommunication. Libferris is a virtual filesystem. It also includes rich metadata support, common code like recursive copy, and many posix clients like ferrisls, ferriscp etc. along with GTK+2 interfaces to that functionality. Since libferris can mount many things, it can be non trivial to build. But much of the functioanlity is optional so you should be able to trim it down to a small build. I make packages for Fedora and maemo to help with installation. Nothing for the n900 yet as I lack the device to test it on. Yes, I could test on scratchbox but that's another story. The code in Ferris/ links to libferris.so which is the library you seek. You'll have to read the ferriscp code to see how to use the API though. > > Then I also found out that it was already ported to Maemo 2008, which > is great news. But it seemed like it was not so easy to actually port > it, hinting again at libferris being far too complex... Well, the main things are the xerces-c usage there. If/when I port to using Qt's XML code then making maemo and symbian ports should be easier still. > > What do you think, is libferris for me? Can you give me advice on how > to use it? Well, it might be for you, its hard to say. There is no huge company behind libferris to make it easy to use or install. So to use it's API you are going to have to read source and get your hands dirty, but if that's fine with you then libferris might be for you :) > > Thanks in advance! > > lukash > |
From: Ben M. <mon...@us...> - 2010-05-03 12:18:56
|
On Mon, 2010-05-03 at 11:45 +0200, Maxim Burgerhout wrote: > Hi, > > remembering Ben Martin's presentation on the NLUUG conference last > year, I wanted to make some time to toy with libferris a bit. I tried > compiling it on my Fedora 13 box, but it seems libferris needs > Xerces-c 2.7.0, whereas F13 only has Xerces-c 3.0 in it's > repositories. Hi, Glad my presentation was so memorable :) I notice that Fedora 13 is to be released later this month. My plan was to update my rpms on the OBS for Fedora and include modifications to the main libferris tree which might be required at that time. As you mention Xerces-C will likely be one of these things. The other expected one might be some little changes due to more receent gcc versions. > > Can libferris support xerces-c 3.0? Is there another way to run > libferris on newer releases of Fedora? If you absolutely need to use the beta of Fedora 13 for some reason then you'll either have to port the xerces-c stuff to version 3.0 of the API or parallel install xerces-c 2.x on your machine. I've not tested against xerces-c 3.0 yet, but it will work with that version in the future. I can't set times here because the porting will probably be done when I find time to do it :/ > > Regards, > > Maxim Burgerhout |
From: Maxim B. <ma...@wz...> - 2010-05-03 10:09:33
|
Hi, remembering Ben Martin's presentation on the NLUUG conference last year, I wanted to make some time to toy with libferris a bit. I tried compiling it on my Fedora 13 box, but it seems libferris needs Xerces-c 2.7.0, whereas F13 only has Xerces-c 3.0 in it's repositories. Can libferris support xerces-c 3.0? Is there another way to run libferris on newer releases of Fedora? Regards, Maxim Burgerhout ma...@wz... ---------------- GPG Fingerprint EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A |
From: Ben M. <mon...@us...> - 2010-01-27 08:15:46
|
Sorry about the delay, I've been a bit buried in tasks lately. You don't have to build the libsoprano_boostmmapbackend.cpp to use libferris. This custom soprano backend is mainly for playing with performance and hasn't really got anything to do with ferris itself. If you are not comfortable building software I would recommend installing the rpm files on a Fedora 11 or 12 virtual machine. The build order is shown here: http://witme.sourceforge.net/libferris.web/images/ferris-deps.png You don't need redland now. Of the custom stuff that is unlikely to be in your distro the order would be start to end: libferrisloki, libferrisstreams, libstldb4, fampp2, libferris, then ferriscreate. You should be able to get xerces-c, xalan-c, boost, and their respective development package from your distro. Also forget about STLport from the diagram. On Tue, 2010-01-05 at 15:31 -0600, Neil Best wrote: > I am trying to build libferris from source. My configuration went > fine with: > > ./configure --prefix=$HOME/local > > but make ran into problems: > > . . . > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I. -I. -I.. -I.. -I/ > home/nbest/local/include -I/usr/local/include -MT > libsoprano_boostmmapbackend.lo -MD -MP -MF .deps/ > libsoprano_boostmmapbackend.Tpo -c libsoprano_boostmmapbackend.cpp - > fPIC -DPIC -o .libs/libsoprano_boostmmapbackend.o > libsoprano_boostmmapbackend.cpp:23:46: error: src/ > libsoprano_boostmmapbackend.hh: No such file or directory > In file included from libsoprano_boostmmapbackend.cpp:24: > ../src/BoostmmapModel.hh:52:27: error: QtCore/QtGlobal: No such file > or directory > ../src/BoostmmapModel.hh:53:30: error: QtCore/QTextStream: No such > file or directory > ../src/BoostmmapModel.hh:55:27: error: Soprano/Backend: No such file > or directory > ../src/BoostmmapModel.hh:56:32: error: Soprano/StorageModel: No such > file or directory > ../src/BoostmmapModel.hh:57:29: error: Soprano/Statement: No such file > or directory > ../src/BoostmmapModel.hh:58:32: error: Soprano/NodeIterator: No such > file or directory > ../src/BoostmmapModel.hh:59:39: error: Soprano/QueryResultIterator: No > such file or directory > ../src/BoostmmapModel.hh:60:37: error: Soprano/StatementIterator: No > such file or directory > libsoprano_boostmmapbackend.cpp:26:27: error: QtCore/QtPlugin: No such > file or directory > libsoprano_boostmmapbackend.cpp:27:25: error: QtCore/QDebug: No such > file or directory > libsoprano_boostmmapbackend.cpp:28:24: error: QtCore/QHash: No such > file or directory > libsoprano_boostmmapbackend.cpp:29:23: error: QtCore/QDir: No such > file or directory > libsoprano_boostmmapbackend.cpp:30:31: error: QtCore/QMutexLocker: No > such file or directory > ../src/BoostmmapModel.hh:66: error: ‘Soprano’ is not a namespace-name > ../src/BoostmmapModel.hh:66: error: expected namespace-name before ‘;’ > token > ../src/BoostmmapModel.hh:69: error: expected ‘,’ or ‘...’ before ‘&’ > token > ../src/BoostmmapModel.hh:69: error: ISO C++ forbids declaration of > ‘QString’ with no type > ../src/BoostmmapModel.hh:70: error: expected ‘,’ or ‘...’ before ‘&’ > token > ../src/BoostmmapModel.hh:70: error: ISO C++ forbids declaration of > ‘QVariant’ with no type > ../src/BoostmmapModel.hh:71: error: ‘std::string Boostmmap::tostr’ > redeclared as different kind of symbol > ../src/BoostmmapModel.hh:70: error: previous declaration of > ‘std::string Boostmmap::tostr(int)’ > ../src/BoostmmapModel.hh:71: error: ‘Soprano’ has not been declared > ../src/BoostmmapModel.hh:168: error: ‘Soprano’ has not been declared > ../src/BoostmmapModel.hh:168: error: ISO C++ forbids declaration of > ‘Node’ with no type > ../src/BoostmmapModel.hh:168: error: expected ‘;’ before ‘getObject’ > ../src/BoostmmapModel.hh:177: error: expected `;' before ‘}’ token > ../src/BoostmmapModel.hh:230: error: ‘Soprano’ has not been declared > ../src/BoostmmapModel.hh:230: error: expected `{' before ‘StorageModel’ > ../src/BoostmmapModel.hh:230: error: invalid function declaration > libsoprano_boostmmapbackend.cpp:36: error: expected constructor, > destructor, or type conversion before ‘(’ token > make[2]: *** [libsoprano_boostmmapbackend.lo] Error 1 > > > I suspect that it is a matter of dependencies but I can't tell what's > missing. I tried to add --disable-kde-detection to ./configure but it > had no effect. I am no expert on compiling from source and could not > make an association between the build order graphic on the libferris > web site and the above output. Where can I find a succint list of > components that must be in place in order to make libferris? What did > I miss in that output that would tell me what I was missing? I'm > after that's solved it will be an iterative process of fulfilling all > dependencies. Thanks for any guidance. > > > Neil > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Witme-ferris mailing list > Wit...@li... > https://lists.sourceforge.net/lists/listinfo/witme-ferris |
From: Neil B. <nb...@ci...> - 2010-01-05 21:31:23
|
I am trying to build libferris from source. My configuration went fine with: ./configure --prefix=$HOME/local but make ran into problems: . . . libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I. -I. -I.. -I.. -I/ home/nbest/local/include -I/usr/local/include -MT libsoprano_boostmmapbackend.lo -MD -MP -MF .deps/ libsoprano_boostmmapbackend.Tpo -c libsoprano_boostmmapbackend.cpp - fPIC -DPIC -o .libs/libsoprano_boostmmapbackend.o libsoprano_boostmmapbackend.cpp:23:46: error: src/ libsoprano_boostmmapbackend.hh: No such file or directory In file included from libsoprano_boostmmapbackend.cpp:24: ../src/BoostmmapModel.hh:52:27: error: QtCore/QtGlobal: No such file or directory ../src/BoostmmapModel.hh:53:30: error: QtCore/QTextStream: No such file or directory ../src/BoostmmapModel.hh:55:27: error: Soprano/Backend: No such file or directory ../src/BoostmmapModel.hh:56:32: error: Soprano/StorageModel: No such file or directory ../src/BoostmmapModel.hh:57:29: error: Soprano/Statement: No such file or directory ../src/BoostmmapModel.hh:58:32: error: Soprano/NodeIterator: No such file or directory ../src/BoostmmapModel.hh:59:39: error: Soprano/QueryResultIterator: No such file or directory ../src/BoostmmapModel.hh:60:37: error: Soprano/StatementIterator: No such file or directory libsoprano_boostmmapbackend.cpp:26:27: error: QtCore/QtPlugin: No such file or directory libsoprano_boostmmapbackend.cpp:27:25: error: QtCore/QDebug: No such file or directory libsoprano_boostmmapbackend.cpp:28:24: error: QtCore/QHash: No such file or directory libsoprano_boostmmapbackend.cpp:29:23: error: QtCore/QDir: No such file or directory libsoprano_boostmmapbackend.cpp:30:31: error: QtCore/QMutexLocker: No such file or directory ../src/BoostmmapModel.hh:66: error: ‘Soprano’ is not a namespace-name ../src/BoostmmapModel.hh:66: error: expected namespace-name before ‘;’ token ../src/BoostmmapModel.hh:69: error: expected ‘,’ or ‘...’ before ‘&’ token ../src/BoostmmapModel.hh:69: error: ISO C++ forbids declaration of ‘QString’ with no type ../src/BoostmmapModel.hh:70: error: expected ‘,’ or ‘...’ before ‘&’ token ../src/BoostmmapModel.hh:70: error: ISO C++ forbids declaration of ‘QVariant’ with no type ../src/BoostmmapModel.hh:71: error: ‘std::string Boostmmap::tostr’ redeclared as different kind of symbol ../src/BoostmmapModel.hh:70: error: previous declaration of ‘std::string Boostmmap::tostr(int)’ ../src/BoostmmapModel.hh:71: error: ‘Soprano’ has not been declared ../src/BoostmmapModel.hh:168: error: ‘Soprano’ has not been declared ../src/BoostmmapModel.hh:168: error: ISO C++ forbids declaration of ‘Node’ with no type ../src/BoostmmapModel.hh:168: error: expected ‘;’ before ‘getObject’ ../src/BoostmmapModel.hh:177: error: expected `;' before ‘}’ token ../src/BoostmmapModel.hh:230: error: ‘Soprano’ has not been declared ../src/BoostmmapModel.hh:230: error: expected `{' before ‘StorageModel’ ../src/BoostmmapModel.hh:230: error: invalid function declaration libsoprano_boostmmapbackend.cpp:36: error: expected constructor, destructor, or type conversion before ‘(’ token make[2]: *** [libsoprano_boostmmapbackend.lo] Error 1 I suspect that it is a matter of dependencies but I can't tell what's missing. I tried to add --disable-kde-detection to ./configure but it had no effect. I am no expert on compiling from source and could not make an association between the build order graphic on the libferris web site and the above output. Where can I find a succint list of components that must be in place in order to make libferris? What did I miss in that output that would tell me what I was missing? I'm after that's solved it will be an iterative process of fulfilling all dependencies. Thanks for any guidance. Neil |
From: Ben M. <mon...@us...> - 2009-10-15 12:32:27
|
OK, try version 3.0.3 just released... On Tue, 2009-10-13 at 22:38 -0400, jesse wilson wrote: > Hi. Ferrisloki (3.0.1, and I would assume any earlier versions) is > broken on Gentoo because of api changes in libsigc++ 2.2. Someone > mentioned in this bug: > > http://bugs.gentoo.org/221139 > > that it has been fixed upstream but that packages have just not been > released yet. This was in June 2008, 16 months ago! Meanwhile there is > no workaround on Gentoo because libsigc++-2.0 has been removed from > the portage tree... The aforementioned Gentoo dev has been working > pretty diligently to create ebuilds for the various libferris related > things, and obviously it would be great to get libferris itself into > the portage tree. I need libferris so I can mount dbus and see what > signals get transmitted over it and how with the telepathy framework. > I am planning to write some tools and contribute to a client for > telepathy. So, is the updated ferrisloki at all ready for release yet? > We would all like to see libferris enter the portage tree. > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Witme-ferris mailing list > Wit...@li... > https://lists.sourceforge.net/lists/listinfo/witme-ferris |
From: jesse w. <jes...@gm...> - 2009-10-14 02:38:25
|
Hi. Ferrisloki (3.0.1, and I would assume any earlier versions) is broken on Gentoo because of api changes in libsigc++ 2.2. Someone mentioned in this bug: http://bugs.gentoo.org/221139 that it has been fixed upstream but that packages have just not been released yet. This was in June 2008, 16 months ago! Meanwhile there is no workaround on Gentoo because libsigc++-2.0 has been removed from the portage tree... The aforementioned Gentoo dev has been working pretty diligently to create ebuilds for the various libferris related things, and obviously it would be great to get libferris itself into the portage tree. I need libferris so I can mount dbus and see what signals get transmitted over it and how with the telepathy framework. I am planning to write some tools and contribute to a client for telepathy. So, is the updated ferrisloki at all ready for release yet? We would all like to see libferris enter the portage tree. |
From: Ben M. <mon...@us...> - 2009-01-11 23:41:34
|
On Sun, 2009-01-11 at 16:09 -0500, Patrick Chapman wrote: > Hi, as a programmer I'm a bit of a hack but I am a good biologist. > > my end goal is to produce Debian packages that work easily for me. I > have started by trying to repackage the Fedora 8 packages (vitural > computers are a wonderful thing) to acheve understanding. Fedora 8 > comes with boost 1.34 libferris configuration demands boost 1.33 and I > cannot change this. You could start with the packages from OBS http://download.opensuse.org/repositories/home:/monkeyiq/ specifically, the xUbuntu 710 ones http://download.opensuse.org/repositories/home:/monkeyiq/xUbuntu_7.10/ I never completely compiled for ubuntu 804 on OBS. I have recently compiled libferris again for maemo using boost 1.34.1. So later boost versions are OK. I have updated that configure message. The downside to the OBS packages referenced above is that I tend to use Fedora and recently maemo, so I generally keep those packages up to date in line with what my needs are at the time. > > If it is not too much trouble I could use a 'point in the right > direction'. At the moment I don't even care if libferris will work > with boost 1.34 if I can't even change the config file I'm not going > to get anywhere. Are you meaning that you want to use boost 1.33.1 on debian? Which config file are your referring to? What are the last few (interesting) lines in config.log? Oh, and I assume you have packaged the prerequisites like ferrisloki, ferrisstreams, stldb4, fampp2? |
From: Patrick C. <pch...@gm...> - 2009-01-11 21:09:27
|
Hi, as a programmer I'm a bit of a hack but I am a good biologist. my end goal is to produce Debian packages that work easily for me. I have started by trying to repackage the Fedora 8 packages (vitural computers are a wonderful thing) to acheve understanding. Fedora 8 comes with boost 1.34 libferris configuration demands boost 1.33 and I cannot change this. If it is not too much trouble I could use a 'point in the right direction'. At the moment I don't even care if libferris will work with boost 1.34 if I can't even change the config file I'm not going to get anywhere. Patrick Chapman |
From: Ben M. <mon...@us...> - 2008-07-19 09:29:06
|
On Fri, 2008-07-18 at 15:53 +0200, Garito wrote: > 2008/7/18 Ben Martin <mon...@us...>: > On Thu, 2008-07-17 at 19:32 +0200, Garito wrote: > > Hi! > > I recently subscribe to this list because I'm interested in > the > > library > > > Hi, welcome aboard! > > > > > Did someone try to use this library in a linux 2.6 with ARM > chip? > > > > There is a port to the Nokia n810 which runs ARM and a 2.6 > kernel: > http://kvo.cs.uow.edu.au/~martin/maemo/repository/binary/ > > Ok, I suppose that in this url I can find a binary for ARM (I'm a > totally newbie) > I try to use it and I tell here my experience > That binary depends on the stdc++ that is in that directory. Once you have a cross compile environment for your board and ARM version you should be able to build libferris with ./configure; make; make install. > > > The biggest two issues is > a) how much RAM your device has > b) you need prelink for faster startup times > > I have to options: one with 32Mb and other with 64Mb > > > > > I plan, if possible, to use it to program embedded systems, > any > > previous experience? > > > > Work is ongoing in improving the maemo port and adding in some > optional > compile time things to allow libferris to be able to use less > RAM (with > less features also). Maemo has 128mb of RAM which is fine, > though most > "embedded" platforms tend to have less than this. > > Are you able to divulge the hardware / project you are > planning? > > The hardware I plan to use at least in the begining are: > http://www.embedinfo.com/english/Product/sbc2410III.asp This > motherboard is my primary target because I have it here in that > moment. A friend of my goes on holidays > > But I will buy this other: http://www.artila.com/p_matrix.html OK cool. Most of the stuff I tend to use so far in embedded is finished phone / MID stuff. > > My mind goal with your library is build a framework called Yanged that > has some rules. The main and the first one is simplicity by > refactoring every time you can > > Less is more > > Can you point me to the correct url where libferris is explained in a > newbie way? I could see a lot of information but no one that explain > how to install it and a refernece manual about what I can do with it? The Linux Journal articles are probably to move friendly introduction. Installing is just ./configure; make; make install. Though as libferris is quite complex there are a heap of --disable type switches too. As much as I'd like to write a solid book with tutorial and reference parts, it's hard to convince publishers that there is a market of sufficient size for the book. > > I know that documentation is the worst part in a project but new > people needs to understand how the things are done I don't actually mind writing documentation. But when it comes down to either coding a feature I want or writing about stuff I tend to do the former. Whenever I can work out a way to write documentation for libferris, like through Linux Journal in the past I always do so. > > Thanks, and good job! > :-) > |
From: Garito <ga...@gm...> - 2008-07-18 13:53:42
|
2008/7/18 Ben Martin <mon...@us...>: > On Thu, 2008-07-17 at 19:32 +0200, Garito wrote: > > Hi! > > I recently subscribe to this list because I'm interested in the > > library > > Hi, welcome aboard! > > > > > Did someone try to use this library in a linux 2.6 with ARM chip? > > > There is a port to the Nokia n810 which runs ARM and a 2.6 kernel: > http://kvo.cs.uow.edu.au/~martin/maemo/repository/binary/<http://kvo.cs.uow.edu.au/%7Emartin/maemo/repository/binary/> Ok, I suppose that in this url I can find a binary for ARM (I'm a totally newbie) I try to use it and I tell here my experience > > > The biggest two issues is > a) how much RAM your device has > b) you need prelink for faster startup times I have to options: one with 32Mb and other with 64Mb > > > > I plan, if possible, to use it to program embedded systems, any > > previous experience? > > Work is ongoing in improving the maemo port and adding in some optional > compile time things to allow libferris to be able to use less RAM (with > less features also). Maemo has 128mb of RAM which is fine, though most > "embedded" platforms tend to have less than this. > > Are you able to divulge the hardware / project you are planning? The hardware I plan to use at least in the begining are: http://www.embedinfo.com/english/Product/sbc2410III.asp This motherboard is my primary target because I have it here in that moment. A friend of my goes on holidays But I will buy this other: http://www.artila.com/p_matrix.html My mind goal with your library is build a framework called Yanged that has some rules. The main and the first one is simplicity by refactoring every time you can Less is more Can you point me to the correct url where libferris is explained in a newbie way? I could see a lot of information but no one that explain how to install it and a refernece manual about what I can do with it? I know that documentation is the worst part in a project but new people needs to understand how the things are done Thanks, and good job! -- Mis Cosas: http://blogs.sistes.net/Garito |
From: Ben M. <mon...@us...> - 2008-07-18 12:12:38
|
On Thu, 2008-07-17 at 19:32 +0200, Garito wrote: > Hi! > I recently subscribe to this list because I'm interested in the > library Hi, welcome aboard! > > Did someone try to use this library in a linux 2.6 with ARM chip? > There is a port to the Nokia n810 which runs ARM and a 2.6 kernel: http://kvo.cs.uow.edu.au/~martin/maemo/repository/binary/ The biggest two issues is a) how much RAM your device has b) you need prelink for faster startup times > I plan, if possible, to use it to program embedded systems, any > previous experience? Work is ongoing in improving the maemo port and adding in some optional compile time things to allow libferris to be able to use less RAM (with less features also). Maemo has 128mb of RAM which is fine, though most "embedded" platforms tend to have less than this. Are you able to divulge the hardware / project you are planning? |
From: Garito <ga...@gm...> - 2008-07-17 17:32:17
|
Hi! I recently subscribe to this list because I'm interested in the library Did someone try to use this library in a linux 2.6 with ARM chip? I plan, if possible, to use it to program embedded systems, any previous experience? Thanks! -- Mis Cosas: http://blogs.sistes.net/Garito |
From: M. D. P. <m....@xm...> - 2008-05-19 12:38:24
|
On Mon, 19 May 2008 04:30:40 -0600, Ben Martin <mon...@us...> wrote: >> Advice? > > The old 1.33 version is the one. Okay, cool. I was mostly concerned that by using the wrong version I was going to find myself with problems later on down the road. > Use xqilla 2.0.0. Okay. >> STLPort at this point in time? > > Not really. Most of my compiles are against the normal libstdc++. Many > years ago there were some show stopping bugs in the latter but not > anymore. Right on. >> *FullTextSearch: ... Any ideas what I should be doing differently? > > Which version are you using. I'll take a look into the configure foo for > xapian again to see if I can make it a little smarter in detection. I need to look. I'll do that shortly and get back to you. Thanks gain for all of your help! -- /M:D M. David Peterson Co-Founder & Chief Architect, 3rd&Urban, LLC Email: m....@3r... | m....@am... Mobile: (206) 999-0588 http://3rdandUrban.com | http://amp.fm | http://www.oreillynet.com/pub/au/2354 |
From: Ben M. <mon...@us...> - 2008-05-19 10:31:19
|
On Sun, 2008-05-18 at 06:31 -0600, M. David Peterson wrote: > True, though things seem to be pretty straight forward in /most/ cases. > The troubles I have had thus far are mainly related to finding and linking > the proper header files and what have you. Actually, in this regard, a > couple of questions, > > *pccts: The only way I could get this portion of the compile process to > succees was by tracking down the /old/ pccts source (1.33 I believe), > building, and then pointing libferris as the proper header files before it > was happy and decided to move on in the configure process. I would have > thought a recent release of antlr would have been adequate, but for some > reason I couldn't get it to take. Advice? The old 1.33 version is the one. I have plans to port to antlr for full blown ENBF->filesystem and using boost::spirit for ffilter and other simpler parsing. Both of these are currently done using pccts. The problem is that it is a fairly significant amount of work to change something that currently already works. pccts is a compile time only dep which also gives me less incentive to spend the many days needed to port over to antlr/spirit. It will happen one day, but then so will many of the things on my libferris.TODO list ;) > > *Xerces: The configure script is hardcoded at Xerces 2.7. The latest > XQilla requires patches against Xerces 2.8 to compile correctly. Should I > move to a previous version of XQilla that uses Xerces 2.7 as its base, run > the 2.8 patches against the 2.7 code base, or something else altogether? > The time it takes to build each of these packages out is significant > enough that I would rather gain your advice before pushing forward. Use xqilla 2.0.0. I originally wanted to port to the latest and greatest xqilla but I don't want to have to distribute a patched private compile of Xerces-C on distributions which already have xerces-c. This will sort itself out when a later xqilla is released which can compile against a vanilla xerces-c again. > > *STLPort: Are there any clear advantages to building everything againts > STLPort at this point in time? Not really. Most of my compiles are against the normal libstdc++. Many years ago there were some show stopping bugs in the latter but not anymore. > > *FullTextSearch: No matter what I did, I couldn't get Xapian built in such > a way that the configure script was satisfied enough to include support > for full text search. Any ideas what I should be doing differently? Which version are you using. I'll take a look into the configure foo for xapian again to see if I can make it a little smarter in detection. |