> I'm having some trouble building 2.1.9 -- I downloaded and unpacked > the tarball linked above (http://www.tuxera.com/mac/macfuse- > rebel-2.1.9-src.tar.bz2), but running 'macfuse_buildtool -t dist' in > macfuse-rebel-2.1.9/core failed to find /etc/macfuse/private.der. I > copied in core/private_key.der from the 2.1.7 tree and hacked the > build script's M_CONF_PRIVKEY to refer to it (assuming it's just a > "throwaway" private key for signing the build for distribution, and > not much of a concern since I'm not actually distributing anything).
Correct. Amit has the official private key for signing his official releases/updates so that the preference pane can check if they are legit before installing anything. I took the key file from "core/autoinstaller/TestKeys". > The build still failed though, and the source of the problem wasn't > immediately obvious to me (output is at http://pastebin.com/TevasaHj). > Does this version require some different build steps I'm not aware of? When I started working on MacFUSE I had to patch the build tool in order for it to work. macfuse_buildtool can build MacFUSE for different targets. "dist" is just one of them. Running "macfuse_buildtool -h" will list them. clean clean all targets dist create a multiplatform distribution package examples build example file systems (e.g. fusexmp_fh and hello) lib build the user-space library (e.g. to run fusexmp_fh) libsrc unpack and patch the user-space library source reload rebuild and reload the kernel extension smalldist create a platform-specific distribution package swconfigure configure software (e.g. sshfs) for compilation For Erik's source release I had to run "macfuse_buildtool -t smalldist" This creates a platform specific core package "MacFUSE Core.pkg" which includes basically just the fuse.fs filesystem. I suppose this would be how Erik built it, too. If you want to know what the actual problem is keep on reading otherwise you should be fine with using "smalldist" as target. If you run "macfuse_buildtool -t dist" a multiplatform package is built which would include binaries for 10.4 and support for ppc architecture by default. In addition to the fuse.fs filesystem the preference pane and some other stuff would be built. Your problem is caused by the autoistaller project which is needed by the preference pane. You can find it here "core/autoinstaller". The autoinstaller project requires some other projects which should be in the directory "core/externals". But this directory (about 52 MB) is missing in Erik's release. In addition to that the autoinstaller is broken in the official svn and therefore in Erik's release. He did not patch it up because it is not needed if are just interested in the core fuse.fs component. If you copy the directories "core/autoinstaller" and "core/externals" to Erik's source tree "macfuse_buildtool -t dist" might work. But you would still need the 10.4 SDK. In my 2.1.7 source release "macfuse_buildtool -t dist" works fine because I fixed the autoinstaller and the projects it relies on. In addition to that I tweaked the build tool so that it would only create Mac OS X 10.6 packages. So neither the 10.4 SDK nor 10.5 SDK is needed. By the way if you are using the case sensitive hfs like me you need to change line 33 in "macfuse-rebel-2.1.9/core/10.5/fusefs/fuse_ipc.h" #include <IOKit/IOLocks.h> The "l" in locks needs to be uppercase otherwise the header file is not found. Regards Benjamin -- 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.
