So would the best way to do this be to have a separate process for the
Wine program that loads the DLL, and then have the Fuse process
communicate over pipes or some other IPC method?
Tried adding in those other options and the only difference it makes
is that I get an additional error message when I try to execute the
program as a normal user. Instead of getting:
fusermount: failed to open /etc/fuse.conf: Permission denied
fusermount: waitpid: No child processes
...I now
I thought that the "main" executable being produced by winegcc was
just a script that called wine with "main.exe.so"? This seems to be
the case, as attempting to run "wine main" fails (Module not found),
and running "wine main.exe.so" produces exactly the same results as
running "./main" did.
On
I tried but I've hit a problem. I'm just trying to compile the "Hello
world" Fuse application.
(http://fuse.sourceforge.net/helloworld.html) In regular gcc, I can
compile and run it fine:
$ gcc -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=22 -lfuse -o main main.c
$ mkdir test
$ ./main test
I'm writing a program in which I have a Windows DLL that I need to load.
The DLL contains a function that returns a pointer to some data, and I want
to expose that data as file data in a Fuse file system. My first thought
was that I could have the program load the DLL using winelib, but I'm not
su
