On Oct 19, 11:14 am, Archie Cobbs <[email protected]> wrote: > Now I guess I'm supposed to tell them to install MacFUSE using > the .dmg file instead of MacPorts. OK, that sounds entirely > reasonable, so the world can have One True Install of MacFUSE. And in > any case, MacPorts does not have a 2.x version of MacFUSE in it.
In the past, there always has been one true installation of MacFUSE. You should always have told your users to install MacFUSE using the official .dmg file. I've discouraged people from using other repackagings. There are several threads about this in this group's archives. > Here is where it gets fuzzy though. It seems like the new MacFUSE > install doesn't install pkg-config .pc files -- or at least not where > a pkg-config installed via MacPorts can find them: MacFUSE has always (for a long, long time) installed .pc files under / usr/local/ (/usr/local/lib/pkgconfig/ specifically). MacPorts uses / opt, Fink uses /sw, somebody else might prefer some other location. There's no "new" MacFUSE installation (at least yet). > I realized there is stuff on the HOWTO wiki page relating to this. But > am I really expected to ask my users to checkout MacFUSE from > Subversion and run shell scripts? Which don't work by the way: The "-t swconfigure" option of macfuse_buildtool.sh is merely a convenience. Nobody is expected or required to use it. All it does is set the CFLAGS and LDFLAGS that a fat (multi-architecture) compilation might need. The script is open source so you can actually look inside the shell script to see what that option does, and then use the same flags yourself. > Summary: it would be really nice if there were a developer-targeted > "best practices" document for how to configure autoconf in 3rd party > filesystems that want to build on both Linux and OS X. I'm sure I'm > not the only developer with questions about how to properly do this. http://code.google.com/p/macfuse/wiki/HOWTO (the last section) says that if the default compiler/linker flags (as set by "-t swconfigure" or those coming from the .pc file) do not work for you, then you need to figure out what you need to tweak. There's no panacea. That said, numerous existing FUSE file systems from Linux do compile with MacFUSE without any or much trouble. In your case where configure fails, you should look at the contents of config.log. Amit --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
