Skip to content

Conversation

@NickGerleman
Copy link
Contributor

@NickGerleman NickGerleman commented Jan 23, 2020

  1. Update NativeToJSBridge.h with a fix that was incorporated into
    Facebook master instead of our current fix.
  2. Remove ENABLE_NATIVE_SYSTRACE_TO_ETW. We don't check it in RNW or
    micosoft/react-native.
  3. Remove conditional definition of ENABLE_ETW_TRACING for non-OSS React
    Native. We can build it just fine, since the patch we had was to fix an
    error exposed when WITH_FBSYSTRACE is defined.
  4. Enable ENABLE_JS_SYSTRACE_TO_ETW in patched OSS RN
  5. Consolidate preprocessor definitions to React.cpp.props.
    WITH_FBSYSTRACE is checked in Facebook headers, meaning projects
    including Facebook headers that didn't copy the definitions may get
    mismatched headers. We should expose the definition to more projects to
    prevent this.
  6. Remove conditional compilation of logMarker, since it builds in
    unpatched OSS RN and there are not any apparent divergences that would
    impact runtime behavior.

Validated we build:

  • Universal Solution with OSS_RN, with and without patches
  • Desktop Solution with OSS_RN with patches, and not more broken without
Microsoft Reviewers: Open in CodeFlow

1. Update NativeToJSBridge.h with a fix that was incorporated into
Facebook master instead of our current fix.
2. Remove "ENABLE_NATIVE_SYSTRACE_TO_ETW". We don't check it in RNW or
micosoft/react-native.
3. Remove conditional definition of ENABLE_ETW_TRACING for non-OSS React
Native. We can build it just fine, since the patch we had was to fix an
error exposed when "WITH_FBSYSTRACE" is defined.
4. Enable ENABLE_JS_SYSTRACE_TO_ETW in patched OSS RN
5. Consolidate preprocessor definitions tp React.cpp.props.
WITH_FBSYSTRACE is checked in Facebook headers, meaning projects
including Facebook headers that didn't copy the definitions may get
mismatched headers. We should expose the definition to more projects to
prevent this.
6. Remove conditional compilation of logMarker, since it builds in
unpatched OSS RN and there are not any apparent divergences that would
impact runtime behavior.

Validated we build:
- Universal Solution with OSS_RN, with and without patches
- Desktop Solution with OSS_RN with patches, and not more broken without
@NickGerleman NickGerleman requested review from a team, acoates-ms and mganandraj January 23, 2020 03:22
@ghost ghost added the vnext label Jan 23, 2020
Copy link
Contributor

@mganandraj mganandraj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Copy link

@NikoAri NikoAri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants