It's not just mixing versions. You are also trying an unreleased version. Why is the "officially" binary release of MacFUSE 0.4.0 not good enough? Even if you want to build everything yourself, you should be using the tagged 0.4.0 source tree--unless you want bleeding edge on purpose.
The *unreleased* MacFUSE Core (0.5.0, or whatever I end up calling it when it is released) uses a modular implementation of the custom volume icon stuff. Before you can use the "volicon" argument, you need to enable the volicon module. $ ./myfilesystem ... -o modules=volicon -o volicon=/path/to/ iconfile.icns When this gets released, the appropriate wiki page(s) will be updated. Amit On Aug 3, 5:33 pm, davec <[EMAIL PROTECTED]> wrote: > as has been made painfully clear, mixing versions will cause bad > things. my build install went without a hitch. but i'll try again. > I have recompiled 10.4 fuseFS 0.5.0, and libfuse 2.7.0 using the > fuse-2.7.0-macosx.patch. I am still not able to use the -o volicon= > option :( --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
