Filesystem Operations

[CMCDragonkai]

Hey I'm thinking of continuing with this project.

I assume libgit2 uses the real filesystem right?

Were you able to change libgit2 to use an in-memory filesystem supplied by javascript so that it is possible to use libgit2 inside a browser?

I have developed a in-memory fs in javascript, and I'm wondering how I would integrate that into an emscripten compiled libgit2.

[ldct]

If I remember correctly, the compiled js uses https://kripken.github.io/emscripten-site/docs/api_reference/Filesystem-API.html

[CMCDragonkai]

Is it possible to change to a pluggable back end within emscripten? I have my own in memory fs I want to use.

…

On 30 Aug 2017 20:41, "Li Xuanji" ***@***.***> wrote: If I remember correctly, the compiled js uses https://kripken.github.io/ emscripten-site/docs/api_reference/Filesystem-API.html — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnHHTjR5fGcdb7d5G4pQ0DxEla-F5nbks5sdTxHgaJpZM4PF-LN> .

[ldct]

I am not sure. I don't see why it wouldn't be possible

[CMCDragonkai]

I spent the whole day reading about emscripten and libgit2.. etc.

So here's one proposal.

I write the pluggable backend in C and call external functions that will be implemented in JS. Then use emscripten to compile all of it, and the "dynamically link" to the JS VirtualFS.

Or...

I just compile libgit2 to JS first, then write the pluggable backend in JS somehow (http://blog.deveo.com/your-git-repository-in-a-database-pluggable-backends-in-libgit2/) and then everything is done.

The standard way of writing the pluggable backend is apparently through implementing the struct defined in https://github.com/libgit2/libgit2/blob/development/include/git2/sys/odb_backend.h and https://github.com/libgit2/libgit2/blob/development/include/git2/sys/refdb_backend.h. Since I haven't actually worked with emscripten, I'm not entirely sure how to get JS to implement those headers. And then pass those functions into libgit2 initialisation.

BTW how did you deal with the libgit2 dependencies of openssl, zlib, curl, http-parse, libssh2?