Commit Graph

5 Commits

Author SHA1 Message Date
Alex Browne
012a7ea686 Improve build tags for Wasm
Fixes #515

This includes a few small and closely related changes:

1. All occurrences of the build tag `+build js` have been changed to the
   more precise `+build js,wasm`. This will exclude the files from being
   included by third-party compilers like GopherJS, with which they are
   incompatible.
2. Some files which are incompatible with JavaScript/Wasm now have the
   correct build tag (`+build -js`) so they will be excluded from Wasm
   builds.
3. Some configuration options which are incompatible with
   JavaScript/Wasm (or at least the current bindings) will now no longer
   appear in Wasm builds. This meant creating new files with new struct
   definitions and the appropriate build tags.
2019-03-22 10:48:03 -07:00
backkem
db15e20c54 API: Expose SettingEngine
Enable passing custom settings and media engine to an API.
2019-01-24 20:35:49 +01:00
Woodrow Douglass
9458d58a04 Use a full API pointer instead of settingEngine
This replaces context pointers in many
RTC objects (to be more consistent)

Relates to #333
2019-01-23 16:21:13 +01:00
Woodrow Douglass
7743682c86 Use isolated API objects for more tests
This keeps tests from cross-contaminating each other

Relates to #333
2019-01-23 16:21:13 +01:00
Woodrow Douglass
40eb364f97 Add a test for the setting engine
Relates to #333
2019-01-23 16:21:13 +01:00