Spike: compile the engine to WebAssembly

Result: NetCDF is the only thing preventing a WebAssembly build.

em++ -std=c++11 -fsyntax-only over all 58 files in src/: 10 compile, and all 48 failures are 'netcdf' file not found. The include appears in one place, DataBroker.h:25, and reaches everything else through transitive includes.

The rest is already isolated: MPI is behind #ifdef MPI_COUPLING, the HTTP server is 3 references, popen is one block, and termios is only in app/.

Next step: put the NetCDF parts of DataBroker.h/.cpp and load/saveArrivalTimeNC in FireDomain.cpp behind an FF_NO_NETCDF guard, then run the check again. The same guard would also enable a slim wheel without NetCDF/HDF5.

Not tested yet: linking, running, binary size. Threads need SharedArrayBuffer and COOP/COEP headers, so the demo stays single-threaded.

Side finding: 7 variable-length arrays (e.g. ArrayDataLayer.h:275). They are not standard C++ and are a stack risk. Worth fixing on their own.

Drafted with Claude Opus 5, reviewed by a maintainer.

feat(build): compile the engine to WebAssembly

@HugoFara

@HugoFara and @antonio-leblanc
The main issue is Natcdf; i think dev should go get rid of netcdf and dependencies. Probably need to write a custom external binary to a custom compact "ff native" fileformat that will read from a global database. First the current netcdf. loadFromFile will use the binary to pre-process, otherwise without would require the native file format.
a good opportunity to store states to, with fronts, atmap, and data.
I have some ideas for that that requires some infusions, currently testing some, give a bit more time

Yes, NetCDF is understaffed unfortunately. I can try to send a few PRs to the maintainer, who seemed happy to help, but in the long term it seems more efficient to vendor NetCDF.

feat(build): FOREFIRE_ENABLE_NETCDF to build without NetCDF

feat(build): FOREFIRE_ENABLE_NETCDF to build without NetCDF (#208)

feat(build): compile the engine to WebAssembly (#210)

feat(wasm): run a fire in the browser on real terrain

feat(wasm): run a fire in the browser on real terrain (#211)

For record, this is the current state of things as of PR #213

Very cool features we are cooking!

This is great ! thanks a lot. having it run worldwide on github.io would be the next step...we need a separate data tiling for that i guess. *Jean-Baptiste Filippi* Directeur de recherche CNRS | Research Director Sciences Pour l'Environnement (UMR CNRS 6134) Università di Corsica Pasquale Paoli 20250 Corte, France - firecaster.org Le sam. 24 oct. 2026 à 00:50, Hugo ***@***.***> a écrit :

…

*HugoFara* left a comment (forefireAPI/forefire#171) <#171 (comment)> For record, this is the current state of things as of PR #213 <#213> Image: Image (view on web) <https://github.com/user-attachments/assets/b14f26f3-ebe7-4bfa-8c65-f89bcbb48004> Very cool features we are cooking! — Reply to this email directly, view it on GitHub <#171?email_source=notifications&email_token=AAUZ7CXNNV6IAVHAHDO5UXL5VPOFBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZXGYZDSNZRGM32M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-6376297137>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUZ7CWOHF2LAFUEV3THCPT5VPOFBAVCNFSNUABEKJSXA33TNF2G64TZHMYTOMRUHE3TKMJ3JFZXG5LFHM2TCMZTGQZTMMZTGKQXMAQ> . You are receiving this because you commented.Message ID: ***@***.***>

Navigation Menu

Repository navigation

Spike: compile the engine to WebAssembly #171

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Spike: compile the engine to WebAssembly #171

Description

Activity

filippi commented on Oct 21, 2026

HugoFara commented on Oct 21, 2026

HugoFara commented on Oct 23, 2026

filippi commented on Oct 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions