#6014 closed enhancement (fixed)
script to assist building BFS_FUSE in other OS's
Reported by: | mmadia | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | - General | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
As Haiku's source includes the BFS FUSE module, to allow access on other operating systems. It may be worthwhile to provide a helper script to checkout the related files and provide either the information or links to further information.
Assigning to myself as it'd probably be a shell script, but I've no immediate plans to work on it.
To note, this script may be helpful to other people who are willing to create pre-built packages for use with various Linux/BSD/... package managers.
Attachments (2)
Change History (10)
comment:1 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 14 years ago
I've created a simple shell script that will checkout the necessary files and patch configure.
After this initial set-up you can periodically build an updated bfs_fuse
with:
svn update jam -q "<build>bfs_fuse"
by , 13 years ago
Attachment: | configure.patch added |
---|
Patch file needed by checkout_tree_and_configure.sh.
comment:3 by , 9 years ago
Three years later and a couple of things have changed. Most notably the configure script doesn't need patching any more. I've updated the shell script.
by , 9 years ago
Attachment: | checkout_tree_and_configure.sh added |
---|
Simple shell script that will setup the tree for the building of 'bfs_fuse'.
comment:4 by , 9 years ago
I've tried the script on my OS X which ran fine, but then I couldn't compile bfs_fuse:
jam -q "<build>bfs_fuse" No `BuildConfig' found in /Users/diver/Downloads/bfs_fuse/generated/build! Run ./configure in the source tree's root directory first!
comment:5 by , 9 years ago
Unfortunately, I only tested this script on Linux (Ubuntu x86, x86_64 & arm). I don't know if it's even possible to build bfs_fuse on OS X.
comment:6 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
A full tree checkout is needed (but a shallow clone is now possible and much smaller than it used to be). Just run ./configure --host-only
to configure the build without cross-compilers, and then jam -q "<build>bfs_fuse"
.
It seems this is documented on the website, anyway: https://www.haiku-os.org/guides/daily-tasks/access_bfs_with_fuse/
comment:7 by , 6 years ago
This is what i'm getting now on macOS 10.14:
./configure --host-only
stat: illegal option -- c usage: stat [-FlLnqrsx] [-f format] [-t timefmt] [file ...] ./configure: line 556: [: -lt: unary operator expected xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun You need a case-sensitive file-system to build Haiku. You can create a case-sensitive disk image using Disk Utility.
comment:8 by , 5 years ago
Milestone: | → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Giving ownership up, as I've no immediate plans to implement this.