What are the bare minimum emscripten sdk files needed to build an emscripten c++ project? Reason? I'd like to keep the minimum version of the emscripten sdk needed to build my project along with my project source files on my own git repo so that I have control over which emscripten sdk version I am using to build my project and b) everything is contained in that one git repo without needing to download the sdk separately.
--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/bad65a1b-2349-454d-b053-0854ea4fce46o%40googlegroups.com.
So why not just take emsdk as a submodule? That way you'll have control on when you upgrade the repo's version.
On Sat, 25 Jul 2020 at 16:20, ssg <s...@gmail.com> wrote:
What are the bare minimum emscripten sdk files needed to build an emscripten c++ project? Reason? I'd like to keep the minimum version of the emscripten sdk needed to build my project along with my project source files on my own git repo so that I have control over which emscripten sdk version I am using to build my project and b) everything is contained in that one git repo without needing to download the sdk separately.--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-discuss+unsub...@googlegroups.com.
How do you mean submodule? I am a bit new at git.
My thoughts were more along these lines: The entire emsdk is about 600+ MB. The emsdk/upstream/emscripten/system is about 25 MB. Thats the one containing the C++ includes and libs that I am using in my project, though I am not sure what the executable equivalents are for the virtual machine emscripten compiles to (again, am new to emscripten too). So the hope was if I could just pop in the system folder in my repo and some other files like em++ or emcc compiler, I could end up with a lean c++ sdk that would suffice for my project.
On Sunday, July 26, 2020 at 4:11:44 AM UTC+8, Shachar Langbeheim wrote:
So why not just take emsdk as a submodule? That way you'll have control on when you upgrade the repo's version.
On Sat, 25 Jul 2020 at 16:20, ssg <s...@gmail.com> wrote:
What are the bare minimum emscripten sdk files needed to build an emscripten c++ project? Reason? I'd like to keep the minimum version of the emscripten sdk needed to build my project along with my project source files on my own git repo so that I have control over which emscripten sdk version I am using to build my project and b) everything is contained in that one git repo without needing to download the sdk separately.--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/bad65a1b-2349-454d-b053-0854ea4fce46o%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/38e4106b-a4df-455e-8796-03a67cce479fo%40googlegroups.com.
What are the bare minimum emscripten sdk files needed to build an emscripten c++ project? Reason? I'd like to keep the minimum version of the emscripten sdk needed to build my project along with my project source files on my own git repo so that I have control over which emscripten sdk version I am using to build my project and b) everything is contained in that one git repo without needing to download the sdk separately.