Cost of native, built-in support for MacOS X
envgap__Vhonowslend__StreamFX-Public-434
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
7829817f77f5f1a67c7178f11b6ac9bfa20dbc91- Manifest
CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
Vhonowslend/StreamFX-Public #434 · read the original issue
<!-- Hi, thank you for taking the time to ask for help. --> <!-- Please make sure that you fill this out in it's entirety. --> <!-- Unfortunately I will have to close issues if it has not been filled out. --> ### Description <!-- Please describe the feature in its entirety. --> <!-- If you have artwork, links or similar, please attach them. --> The mainstream releasees of obs-StreamFx are currently focussed towards Windows and Linux. Compiling a working solution for MacOS is beyond many users. It has been said in other threads that better support for MacOS users (i.e. an easy to install binary) would require further investment. How much capital is required to achieive this? Note - this would have to include long term support for MacOS. ### Checklist <!-- Please check any that apply. If you aren't sure, leave them unchecked. --> - [x] I am willing to pay someone to implement this feature. - [x] This feature absolutely can't be done with already existing features.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]