Document build steps

[rmx90210]

Hi @lixun910!

Would it be possible to give some very brief instructions here on how you built the GeoDa Wasm module, just to get me started?

Was assuming this involves running Emscripten against libgeoda, but I wasn’t sure how to find the entry point to libgeoda in the geoda repo. Or maybe you used a different method altogether 😄

Thank you for helping kick this off!

[lixun910]

Are you familiar with both C++ and C (mixture programming)? and CMake? If you do, we can get back to work on a generic module like pygeoda/rgeoda after this covid project. This is not a focus for now. The libgeoda is under active development (so not public available), and is currently customized built for GeoDaWASM, not generic. Xun

…

On Apr 19, 2020, at 7:13 PM, Robert Martin ***@***.***> wrote: Hi @lixun910 <https://github.com/lixun910>! Would it be possible to give some very brief instructions here on how you built the GeoDa Wasm module, just to get me started? Was assuming this involves running Emscripten against libgeoda, but I wasn’t sure how to find the find the entry point to libgeoda in the geoda repo. Or maybe you used a different method altogether 🤪 Thank you for helping kick this off! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASPYT754MFYIRPQJTFQSSTRNOVTVANCNFSM4MMB6EWQ>.

[lixun910]

Hi Robert, I just send an invitation to the private wasmgeoda repo. But, it has no documents, notes. You are welcome to play with it, but keep in mind this is a customized build for covid project, not for a generic npm package, which is a target after covid project. Xun

…

On Apr 19, 2020, at 8:00 PM, Xun Li ***@***.***> wrote: Are you familiar with both C++ and C (mixture programming)? and CMake? If you do, we can get back to work on a generic module like pygeoda/rgeoda after this covid project. This is not a focus for now. The libgeoda is under active development (so not public available), and is currently customized built for GeoDaWASM, not generic. Xun > On Apr 19, 2020, at 7:13 PM, Robert Martin ***@***.*** ***@***.***>> wrote: > > > Hi @lixun910 <https://github.com/lixun910>! > > Would it be possible to give some very brief instructions here on how you built the GeoDa Wasm module, just to get me started? > > Was assuming this involves running Emscripten against libgeoda, but I wasn’t sure how to find the find the entry point to libgeoda in the geoda repo. Or maybe you used a different method altogether 🤪 > > Thank you for helping kick this off! > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASPYT754MFYIRPQJTFQSSTRNOVTVANCNFSM4MMB6EWQ>. >

[rmx90210]

Hi Xun, thank you for the invite. I think I understand a bit better now how wasmgeoda was built. I definitely don't want to create extra work or rush building the generic npm module, so maybe I can clarify what I'm trying to do.

The problem I'm trying to solve for is how to bundle the wasmgeoda into an application built with webpack, which generally works with npm packages. I was interested in how you built wasmgeoda because I thought there might be an option to output it as a CommonJS module, i.e.:

var GeoDa = {...};

module.exports = GeoDa;

I found a blog post that suggests emcc supports outputting to UMD or ES6 modules, which could also work:

It is possible to emit a UMD module instead using the -s MODULARIZE=1 flag of the emcc command or -s EXPORT_ES6=1 for ES6 modules.

I can try to import gen/jsgeoda.js as-is and configure webpack to look for a global called Module, aliasing it to something like geoda. Let me see where I get with that first, and I'll follow up with you if I get stuck. Thank you again for your help 😄

[lixun910]

Sure! Sounds good. Let me know when I can help :) Xun Xun Li, Ph.D. Assistant Director of Data Science Center for Spatial Data Science University of Chicago

…

On Apr 19, 2020, at 8:43 PM, Robert Martin ***@***.***> wrote:  Hi Xun, thank you for the invite. I think I understand a bit better now how wasmgeoda was built. I definitely don't want to create extra work or rush building the generic npm module, so maybe I can clarify what I'm trying to do. The problem I'm trying to solve for is how to bundle the GeoDa JS into an application built with webpack, which generally works with npm packages. I was interested in how you built the Wasm JS because I thought there might be an option to output it as a CommonJS (or UMD) module, i.e.: var GeoDa = {...}; module.exports = GeoDa; I found a blog post that suggests emcc can do this: It is possible to emit a UMD module instead using the -s MODULARIZE=1 flag of the emcc command or -s EXPORT_ES6=1 for ES6 modules. I can try to import gen/jsgeoda.js as-is and configure webpack to look for a global called Module, aliasing it to something like geoda. Let me see where I get with that first, and I'll follow up with you if I get stuck. Does that sound OK? 😄 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.