Summary:
Nothing interesting here, just adding necessary sources from Flipper into the VS Studio solution.
As a consequence, some warnings had to be turned off as otherwise they're treated as errors and the solution doesn't build.
Reviewed By: passy
Differential Revision: D36760242
fbshipit-source-id: 2f5e615f8a465554dd35c245756f94bcace6e34a
Summary:
This change brings in Folly and Boost into our solution.
Boost is resolved with NuGet. Folly is resolved by re-using the RNW integration.
For reference:
Flipper depends on Folly. Folly depends on a few things:
- Boost
- FMT
- Glog
- Double-Conversion
Folly from RNW uses some stubs to resolve fmt, glog, and double-conversion. That's OK.
Only Boost needs resolving.
On Visual Studio, we can use the following package managers: NuGet and vcpkg.
Boost can be resolved using either.
Using NuGet as otherwise vcpkg needs to be run locally by anybody wanting to build the solution. NuGet makes things easier.
Reviewed By: aigoncharov
Differential Revision: D36759384
fbshipit-source-id: 31a9a398ce5c5dc2f3def02689ae4bb8c42fbb99
Summary:
This change adds the template for a RNW module to the existing react-native flipper project.
Basically, the changes in this diff are the product of executing the react-native-windows init for the existing library.
See:
https://microsoft.github.io/react-native-windows/docs/getting-startedhttps://microsoft.github.io/react-native-windows/docs/native-modules-setup
Notes:
There's some auto-generated module code contained in this change: ReactNativeModule (.h/.cpp)
allow-large-files
Reviewed By: passy
Differential Revision: D36751772
fbshipit-source-id: 41207bedb00ea147883f6d13336ed6c1da4454d7
