... a little integration just to be sure you understand.
I wrote there because of my failure compiling fuse-2.8.4 and believing
in the possibility to use MacFUSE in user space.
Reading your comment I see MacFUSE runs only in kernel space, so I
have subscribed fuse-devel and switched back to fuse.

Thanks again for your comment,
freedev

On May 24, 2:25 am, freedev <[email protected]> wrote:
> Hello,
>
> thanks for your response and I agree with you.
> I begun to think at macfuse because obviously it runs on mac os x and
> my first (and too short) experience in recompiling fuse-2.8.4 on mac
> os x (show) disappointed me, I was blocked immediately by a "stupid"
> compile error (you can see it few lines after).
> So I suppose to use MacFUSE only in user space without those annoying
> compile errors.
>
> Making all in include
> make  all-am
> Making all in lib
> /bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -
> I../include  -I../include -DFUSERMOUNT_DIR=\"/usr/local/bin\" -
> D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=26    -MT
> fuse.lo -MD -MP -MF .deps/fuse.Tpo -c -o fuse.lo fuse.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../include -
> DFUSERMOUNT_DIR=\"/usr/local/bin\" -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DFUSE_USE_VERSION=26 -MT fuse.lo -MD -MP -MF .deps/fuse.Tpo -c
> fuse.c  -fno-common -DPIC -o .libs/fuse.o
> In file included from fuse.c:18:
> ../include/fuse_compat.h:69:24: error: sys/statfs.h: No such file or
> directory
> In file included from fuse.c:18:
> ../include/fuse_compat.h:91: warning: ‘struct statfs’ declared inside
> parameter list
> ../include/fuse_compat.h:91: warning: its scope is only this
> definition or declaration, which is probably not what you want
> ../include/fuse_compat.h:140: warning: ‘struct statfs’ declared inside
> parameter list
> fuse.c:1017: warning: ‘struct statfs’ declared inside parameter list
>
> On May 22, 4:01 am, Sam Moffatt <[email protected]> wrote:
>
>
>
> > FUSE is designed to provide user space support for what is usually put  
> > into the kernel space. I'd suggest that if you are going to write an  
> > application on an iPhone that this isn't going to make sense as apple  
> > don't let you have access to a kernel on a normal iPhone (not sure  
> > about the jail broken ones but I wouldn't be worried about targeting  
> > such a small target audience). Android I think is also going to be  
> > tricky but you can hack it apart but again the target audience could  
> > be limited here.
>
> > So I personally don't see the point of porting macfuse to a mobile  
> > platform, just write an equivalent library that you can use in your  
> > applications. If you think about it you should be able to write a  
> > library in such a way that you can share code between platforms  
> > (iPhone and mac at least so a c/c++/obj-c library, android is java)
>
> > Cheers,
>
> > Sam
>
> > --
> > Sam Moffatthttp://pasamio.id.au
> > Note: I'm not at my desk, responses may be delayed
>
> > On 22/05/2010, at 11:17 AM, freedev <[email protected]> wrote:
>
> > > Hello,
>
> > > I'm and independent developer and I was trying to create an
> > > application to share documents with computers or mobile devices.
> > > For example, you put some document inside a folder on your computer
> > > and magically these documents appear and are available into another
> > > computer or mobile device.
> > > I know, it isn't a new idea and there are a couple of applications
> > > that already do this.
> > > But I would like to use FUSE and understand if it could be good enough
> > > to port on mobile phones.
> > > For example on Iphone (may be Android in future).
> > > So the question is:
> > > do you know if there is anybody that have tried to port MacFUSE on
> > > iPhone?
> > > If I would like to start writing an iPhone application with MacFUSE
> > > support can you give me some tip to start?
>
> > > Thanks in advance for time spent reading my email,
> > > freedev
>
> > > --
> > > You received this message because you are subscribed to the Google  
> > > Groups "MacFUSE" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to 
> > > [email protected]
> > > .
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/macfuse?hl=en
> > > .
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "MacFUSE" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/macfuse?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "MacFUSE" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group 
> athttp://groups.google.com/group/macfuse?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"MacFUSE" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/macfuse?hl=en.

Reply via email to