57e6662a46
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
5 lines
273 B
Plaintext
5 lines
273 B
Plaintext
// Hint files help the Visual Studio IDE interpret Visual C++ identifiers
|
|
// such as names of functions and macros.
|
|
// For more information see https://go.microsoft.com/fwlink/?linkid=865984
|
|
#define REACT_MODULE(__VA_ARGS__) INTERNAL_REACT_MODULE(__VA_ARGS__)(__VA_ARGS__)
|