public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: Mark Geisert <>,
	"" <>
Subject: Re: [ITP] cygfuse
Date: Sat, 12 Mar 2022 14:43:52 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10/03/2022 06:16, Mark Geisert wrote:
> This is a Cygwin version of libfuse{,3} that can be found in various 
> Linux distributions.  It is a couple of link libraries and additions to 
> /usr/include to allow porting of FUSE apps.  FUSE: File System In User 
> Space.  I will shortly be providing an sshfs FUSE app, to be covered by 
> a separate ITP.
> Importantly, cygfuse depends on an underlying Windows FUSE 
> implementation: WinFSP.  In fact the Cygwin library code was provided by 
> the author of WinFSP.  I'm just providing a bona-fide Cygwin package for 
> the code.
> WinFSP, and thus cygfuse, is made available under GPLv3 for Free/Libre 
> and Open Source Software or under a commercial license.
> If another Windows FUSE provider shows interest in supporting Cygwin, I 
> suspect it could be supported with alternatives(8).

It's not quite that straightforward as the Windows loader can only 
follow symlinks to DLLs if they are

But that's not

> The initial project files for review are located at:
> Thanks for reading and for any feedback you might have,

A few small comments on the cygport file

> #SRC_URI="${PV}.tar.xz"
> #NOT YET:	inherit git

It's unclear where the upstream source tarball comes from...

> PKG_NAMES="cygfuse"
> cygfuse_CONTENTS="
>     usr/bin/*
>     usr/include/fuse/*
>     usr/include/fuse3/*
>     usr/lib/*
>     usr/share/man/man1/*
>     usr/share/man/man8/*
> "
> # take over these activities from cygport..

This should be written 'RESTRICT=strip', I think.

> src_compile()
> {
>     # fix source tree glitch.. (maybe 'prep' stumbling or bad tarfile layout?)
>     if [ -e ${S}/src ]; then
> 	mv ${S}/src/cygfuse ${S}
> 	rmdir ${S}/src
>     fi

I think this can be handled with 'SRC_DIR=src/cygfuse' (and suitable 
adjustment to paths throughout)

>     # and on with the show..
>     cd ${S}
>     lndirs
>     # compile emulation of Linux libfuse..
>     mkdir -p ${B}/cygfuse/fuse
>     cd ${B}/cygfuse/fuse
>     cygmake
>     # compile emulation of Linux libfuse3..
>     mkdir -p ${B}/cygfuse/fuse3
>     cd ${B}/cygfuse/fuse3
>     cygmake
> }

  parent reply	other threads:[~2022-03-12 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  6:16 Mark Geisert
2022-03-10 20:53 ` Marco Atzeri
2022-03-12 14:43 ` Jon Turney [this message]
2022-03-12 14:46   ` Jon Turney
2022-03-25  8:24   ` Mark Geisert
2022-03-27  8:20     ` [ITP] cygfuse -- cygport issues solved Mark Geisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).