1. Don't use fuse_purge_np. The function is still experimental and not recommended. Look at the auto_cache option and see why your need can't be satisfied through it.
2. MacFUSE.framework links against libfuse_ino64 on Leopard and above. It's likely to keep doing that. 3. You can't link against both libfuse_ino64 and libfuse in a program. You also mustn't link against libfuse_ino64/libfuse directly if you already linked against MacFUSE.framework. Amit On Mar 23, 11:37 am, David Zhao <[email protected]> wrote: > Hi guys, > > I'm currently using the ObjC framework but found the need to use > fuse_purge_np, which is only exposed via the fuse libraries. I figured > I need to link directly against the library and found that when I > added the -lfuse linker flag, my fs would refuse to mount and crash > when it initializes. > > After some digging, I found that the Leopard version of the > MacFUSE.framework links against -lfuse_ino64 while the Tiger version > links against -lfuse. > > The question is, can I reliably depend on this fact and distribute two > versions of my library that are linked differently based on the > platform? Will this linking behavior ever change in the future? The > last thing I want is for my filesystem to stop working after a MacFUSE > update. > > Thanks, > > -David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
