From: Bill Zissimopoulos <billziss@navimatics.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: cygfuse
Date: Wed, 21 Sep 2016 06:01:00 -0000 [thread overview]
Message-ID: <D4076BB6.B412%billziss@navimatics.com> (raw)
In-Reply-To: <Pine.BSF.4.63.1609202225470.89347@m0.truegem.net>
On 9/20/16, 10:33 PM, Mark Geisert wrote:
>On Tue, 20 Sep 2016, Bill Zissimopoulos wrote:
>> Mark, has there been any additional progress on this?
>
>No activity. I was not expecting Dokany to be fully integrated before
>ITPing cygfuse, but I had hoped to hear at least that the layout of FUSE
>include files works for them (or doesn't) and that the strategy of
>dynamic
>loading Dokany's DLL is workable for them too.
I am no Dokany expert, but I would think that the dlopen strategy will
work for them as well. They export FUSE symbols such as fuse_new, etc.
https://github.com/dokan-dev/dokany/blob/master/dokan_fuse/src/dokanfuse.de
f
>> Looking at the updated cygfuse I believe one change would be to rename
>> cygfuse.pc back to fuse.pc so that build configuration scripts can find
>> it. I have created a github issue for this.
>
>I've now made those changes and updated the GitHub issue. Should the URL
>named in fuse.pc.in now point at the GitHub cygfuse project?
Yes, I think only the cygfuse project should be referenced.
>> Other than that I would think that the package would be ready for
>> submission. Any changes to support additional projects like Dokany, etc.
>> could easily happen in the future when those projects are ready.
>
>Agreed. It would be neet though to find out sooner rather than later
>whether some other FUSE implementation can coexist with WinFSP. I don't
>have the bandwidth to check Dokany or any others myself despite interest.
The only gotcha that I see is with the header files. I recommend that you
eventually create a new cygfuse-winfsp.c file and move all WinFsp specific
code in there. Some of the code from the header files will have to be
moved into this new file (cygfuse-winfsp.c). Then the header files could
have all WinFsp specific references removed. Notice that under normal
circumstances (e.g. when used to compile SSHFS) the FSP_FUSE_* macros get
defined as:
#define FSP_FUSE_API __declspec(dllimport)
#define FSP_FUSE_API_NAME(n) (n)
#define FSP_FUSE_API_CALL(n) (n)
#define FSP_FUSE_SYM(proto, ...) proto;
I would hope though that the ITP happens before this refactoring. I have
SSHFS and (possibly) FUSEPY ports that I would like to submit :)
Bill
next prev parent reply other threads:[~2016-09-21 6:01 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 11:59 [ITP] FUSE 2.8 Adrien JUND
2016-07-22 17:55 ` Bill Zissimopoulos
2016-07-22 19:56 ` Adrien JUND
2016-07-23 0:23 ` Bill Zissimopoulos
2016-07-23 10:40 ` Corinna Vinschen
2016-07-23 16:44 ` Bill Zissimopoulos
2016-07-23 17:48 ` Corinna Vinschen
2016-07-23 18:34 ` Bill Zissimopoulos
2016-07-25 7:35 ` Corinna Vinschen
2016-07-25 21:20 ` Bill Zissimopoulos
2016-07-26 6:28 ` Mark Geisert
2016-07-26 8:45 ` Herbert Stocker
2016-07-26 12:40 ` Adrien JUND
2016-07-26 18:13 ` Mark Geisert
2016-07-26 18:41 ` Bill Zissimopoulos
2016-07-26 17:23 ` Bill Zissimopoulos
2016-07-26 18:38 ` Bill Zissimopoulos
2016-07-26 19:02 ` Mark Geisert
2016-07-26 19:10 ` Bill Zissimopoulos
2016-07-26 23:22 ` Bill Zissimopoulos
2016-07-27 9:03 ` Mark Geisert
2016-07-27 17:45 ` Bill Zissimopoulos
2016-07-28 9:17 ` Mark Geisert
2016-07-28 16:36 ` Bill Zissimopoulos
2016-07-28 17:29 ` Mark Geisert
2016-07-28 17:43 ` Bill Zissimopoulos
2016-07-28 19:14 ` Bill Zissimopoulos
2016-07-28 19:21 ` Bill Zissimopoulos
2016-07-28 19:59 ` Mark Geisert
2016-07-28 20:08 ` Corinna Vinschen
2016-07-28 20:04 ` Corinna Vinschen
2016-07-28 21:18 ` Bill Zissimopoulos
2016-07-29 0:05 ` Mark Geisert
2016-07-29 0:17 ` Bill Zissimopoulos
2016-07-29 0:27 ` Bill Zissimopoulos
2016-07-29 8:19 ` Mark Geisert
2016-07-29 8:51 ` Corinna Vinschen
2016-07-29 9:15 ` Mark Geisert
2016-07-29 9:48 ` Corinna Vinschen
2016-08-16 17:32 ` Corinna Vinschen
2016-08-17 8:27 ` Mark Geisert
2016-08-17 9:14 ` Corinna Vinschen
2016-08-22 9:43 ` Mark Geisert
2016-08-22 11:54 ` Corinna Vinschen
2016-08-25 8:49 ` Bill Zissimopoulos
2016-09-05 9:36 ` Mark Geisert
2016-09-05 11:20 ` Adrien JUND
2016-09-05 20:16 ` Mark Geisert
2016-09-06 21:15 ` Bill Zissimopoulos
2016-09-07 5:22 ` Herbert Stocker
2016-09-08 8:13 ` Mark Geisert
2016-09-06 22:07 ` Mark Geisert
2016-09-08 8:03 ` cygfuse (was Re: [ITP] FUSE 2.8) Mark Geisert
2016-09-20 21:12 ` Bill Zissimopoulos
2016-09-21 5:33 ` cygfuse Mark Geisert
2016-09-21 6:01 ` Bill Zissimopoulos [this message]
2016-09-21 6:13 ` cygfuse (was Re: [ITP] FUSE 2.8) Adrien JUND
2016-09-06 21:13 ` [ITP] FUSE 2.8 Bill Zissimopoulos
2016-09-08 12:01 ` Corinna Vinschen
2016-09-08 16:58 ` Bill Zissimopoulos
2016-08-25 8:58 ` Bill Zissimopoulos
2016-07-29 15:35 ` Bill Zissimopoulos
2016-07-29 18:35 ` Mark Geisert
2016-07-29 7:50 ` Bill Zissimopoulos
2016-07-29 8:02 ` Mark Geisert
2016-07-26 20:07 ` Adrien JUND
2016-07-26 20:56 ` Bill Zissimopoulos
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D4076BB6.B412%billziss@navimatics.com \
--to=billziss@navimatics.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).