Emscripten binding templates. #142
Description
Activity
Would love to see your cmake command and any special steps you needed to take. I was able to build libgit2.so.0.20.0.js but I'm not sure if I've done anything really since there are no libgit2 functions within it seems.
Did you export any? From what I've seen Emscripten doesn't do this by default. Try out their support channel on irc.mozilla.org#emscripten.
Indeed, I found what I wanted by running emcc with -s LINKABLE=1 "which will disable link-time optimizations and dead code elimination" Thanks! FWIW I'm playing around with this while wondering if the gen'd method is slowing a move to 0.20.0? (is it simple to build 0.20.0.json? what else is involved? should this be in a new ticket :) )...I want the newer creds/transports that came with 0.19.0...
@jpstrikesback It's a bit more involved, I'd love to come up with a way to separate the metadata we add from the actual JSON file we consume. At the moment decoration needs to be manually added.
I've started working on binding libgit2 v0.20.0:
λ node > require("./").Repository.open(".", function(e, repo) { console.log(e, repo); }); 0 {}
... and it works ;-)
Also amazing that a Browserified version works as well.
Well cool!
At the moment, it's all show and no dough. 🍕
diff --cc CMakeLists.txt index 6f731d4,30a32ec..0000000 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@@ -485,3 -465,13 +465,13 @@@ ENDIF ( IF (BUILD_EXAMPLES) ADD_SUBDIRECTORY(examples) ENDIF () + + SET(CMAKE_VERBOSE_MAKEFILE true) + + set(EMSCRIPTEN_ROOT_PATH "/usr/lib/emscripten") + + set(CMAKE_C_COMPILER "${EMSCRIPTEN_ROOT_PATH}/emcc") + set(CMAKE_CXX_COMPILER "${EMSCRIPTEN_ROOT_PATH}/em++") + set(CMAKE_AR "${EMSCRIPTEN_ROOT_PATH}/emar") + set(CMAKE_RANLIB "${EMSCRIPTEN_ROOT_PATH}/emranlib") -set(CMAKE_C_FLAGS "-Wno-implicit -Wno-warn-absolute-paths") ++set(CMAKE_C_FLAGS "-O2 -Wno-implicit -Wno-warn-absolute-paths")
Closing, we're not gonna get to this till sometime next year.
This is a really cool idea. I'm really curious as to whether this sort of thing could potentially be used to get a full-featured git client running in a browser. Chrome has an API for fileSystem access, so this actually seems like it might be plausible to me.
Is this a dead subject? or is there a working port of libgit2 that can be used in the browser or in node?
@eric-schleicher This works: https://github.com/fintechneo/angular-git-filebrowser
Video demos: https://youtu.be/rcBluzpUWE4 and https://youtu.be/xfGrMwLy_tw
I've successfully built libgit2 with Emscripten and am able to call into its functions within Node. This is an interesting fallback option for when compilation or prebuilt binaries fail to work.
However for this to work we'll have to modify our main script here:
https://github.com/nodegit/nodegit/blob/master/index.js#L14-L18
And create another template that can bind directly to the Emscripten exported functions mimicking our native classes exported through nodegit.node.