microsoft
/
react-native-windows
зеркало из https://github.com/microsoft/react-native-windows.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
react-native-windows/vnext/Directory.Build.props

83 строки
5.8 KiB
Plaintext
Исходник Постоянная ссылка Обычный вид История

Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
<?xml version="1.0" encoding="utf-8"?>
<Project>
Fix managed nuget to have ref assembly marked AnyCpu (#6493) * Add Targets to check that developers have run yarn install before building * Change files * Update Directory.Build.targets Co-authored-by: Alexander Sklar <asklar@microsoft.com> * Update Directory.Build.targets * Add package.json steps * Add dummy marker to avoid globs of package.json being picked up Co-authored-by: Alexander Sklar <asklar@microsoft.com>
2020-11-13 20:31:39 +03:00
<!-- This import will noop when customer code is built. This import is here to help building the bits in the react-native-windows repository. -->
Update shared props to have csc emit absolute paths on errors and warnings (#5037) * Update shared props to have csc emit absolute paths on errors and warnings * Change files
2020-05-29 00:23:39 +03:00
<Import Condition="Exists($([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)../')))" Project="$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)../'))" />
Fix playground solution build and Remove old playground app (#2965) * Fix playground solution build * Remove old playground app * Change files
2019-08-21 01:24:13 +03:00
Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
<PropertyGroup>
Fix msbuild as more cases of *Undefined* are popping up (#8055) * More cases of *Undefined* are popping up in MsBuild * Change files
2021-06-17 23:52:54 +03:00
<SolutionDir Condition="'$(SolutionDir)' == '' OR '$(SolutionDir)' == '*Undefined*'">$(MSBuildThisFileDirectory)</SolutionDir>
Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
Update shared props to have csc emit absolute paths on errors and warnings (#5037) * Update shared props to have csc emit absolute paths on errors and warnings * Change files
2020-05-29 00:23:39 +03:00
<!-- This property sets the CscTask to print the full path of the csharp file on errors and warnings rather than just the filename. -->
<GenerateFullPaths>true</GenerateFullPaths>
Enabling SourceLink support. (#5533) * Enabeling SourceLink support. * Change files
2020-07-17 18:32:29 +03:00
Use PackageReference for C++ dependencies (#8195) * Migrate `vnext` projects to `PackageReference`. * Allow `run-windows` to directly restore `package.config` files when conflicting with `PackageReference` items. * Allow parameterizing package names and versions which can be handled as any MSBuild property. * Migrate C++ templates to `PackageReference`. * Drop `packages` directory for `vnext` projects NuGet dependencies.\ Dependencies will be accessed directly at the downloaded NuGet `globalPackagesFolder` using `msbuild /restore`.\ This removes redundant copies of downloaded packages.
2021-12-04 10:19:47 +03:00
<!--
Enabling SourceLink support. (#5533) * Enabeling SourceLink support. * Change files
2020-07-17 18:32:29 +03:00
SourceLink is disabled by default since customer projects are still building our projects and therefore we don't want to force customers to use this.
The PR (windows-vs-pr.yml) and CI (publish.yml() turn it back on.
-->
<EnableSourceLink Condition="'$(EnableSourceLink)' == ''">false</EnableSourceLink>
Update custom targets in Folly.vcxproj and fmt.vcxproj (#10349) * Update custom targets in Folly.vcxproj and fmt.vcxproj This PR updates the custom targets within the Folly.vcxproj and fmt.vcxproj projects by: * Speeding up incremental builds by setting `Inputs` and `Outputs` properties * Calculating paths/filenames only once * Normalizing the download/unzip/override pattern between both projects * Improving build logging * Outputting the `cgmanifest.json` file within the repo to be checked-in (rather than under `node_modules` Closes #10212 * Update Directory.Build.props
2022-08-02 00:52:39 +03:00
<!-- When bumping the Folly version, be sure to bump the git hash of that version's commit and build Folly.vcxproj (to update its cgmanifest.json) too. -->
Update to C++20 (#12656) * Update to C++20 * Change files * Fix Desktop Builds * Address Feedback
2024-02-02 00:35:13 +03:00
<FollyVersion>2023.11.06.00</FollyVersion>
<FollyCommitHash>d62707bf4dc8c58bcc317260611b8cbe25c7f444</FollyCommitHash>
Update custom targets in Folly.vcxproj and fmt.vcxproj (#10349) * Update custom targets in Folly.vcxproj and fmt.vcxproj This PR updates the custom targets within the Folly.vcxproj and fmt.vcxproj projects by: * Speeding up incremental builds by setting `Inputs` and `Outputs` properties * Calculating paths/filenames only once * Normalizing the download/unzip/override pattern between both projects * Improving build logging * Outputting the `cgmanifest.json` file within the repo to be checked-in (rather than under `node_modules` Closes #10212 * Update Directory.Build.props
2022-08-02 00:52:39 +03:00
<!-- When bumping the fmt version, be sure to bump the git hash of that version's commit and build fmt.vcxproj (to update its cgmanifest.json) too. -->
Update fmt version to 10.1.0 (#12411) * update fmt to 10.1.0 * Change files
2023-11-16 20:52:28 +03:00
<FmtVersion>10.1.0</FmtVersion>
<FmtCommitHash>ca2e3685b160617d3d95fcd9e789c4e06ca88</FmtCommitHash>
ABI-safe Hermes API and new JSI for Node-API (#11696) * ABI-safe Hermes API and new JSI for Node-API * Change files * Use Hermes version 0.1.13 that supports UAP * Format code * Merge node-api-jsi project into ReactCommon project * Fix x86 issues * Eliminate Linker warnings * Copy Node-API JSI files to MS.RN.Cxx Nuget * Remove unnecessary settings from shared projects * Format code and fix Layout-MSRN-Headers.ps1 * Fix loading Node-API JSI zip * Remove node-api-jsi project from the playground project * Update Hermes package version * Change files * Fix playground project compilation * Use node-api-jsi with fixes for C++20 * Fix building playground apps * Format code * Make sure that the Hermes inspector works * Update packages.lock.json files * Update Hermes version with fixes for prepared scripts * Use Hermes package 0.1.15 to fix UWP .Net projects * Use SafeLoadLibrary and remove thread Id check for Jsi::Runtime
2023-06-13 07:45:47 +03:00
<!-- Commit hash for https://github.com/microsoft/node-api-jsi code. -->
Integration 12/1 (#12571) * integrate c464b215e * Change files * force to use latest JSIDynamic * integrate c30f2b620 * fix lint and snapshot * add issue numbers * add setExternalMemoryPressure * fix build * revert changes * Update NodeApiJsi with the new JSI APIs * Fix Microsoft.ReactNative.Cxx * Remove JSIDynamic overrides * Add missing setExternalMemoryPressure implementations * Fix unused parameter errors * See JSI_VERSION to 11 in Microsoft.ReactNative.Cxx * Disable failing JSI test --------- Co-authored-by: Vladimir Morozov <vmorozov@microsoft.com>
2024-01-23 00:01:09 +03:00
<NodeApiJsiCommitHash>83cfef428a97627c9185c73da097e42742de56eb</NodeApiJsiCommitHash>
Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
</PropertyGroup>
Ensure ReactNativeWindowsDir is set in Directory.Build.props (#11464) ## Description This PR fixes a problem where we use the `ReactNativeWindowsDir` prop to determine where to build intermediate and output files, but we do so *before* verifying that the prop has been set. This regression was introduced in RNW 0.68 and the result is that rather than all build outputs being placed under the root `build` and `target` folders, they are placed deeper in the folder structure. This can cause file paths to exceed the default max path length, which can cause build problems as not every tool supports long paths (even if it's enabled in the system). ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Resolves intermittent issues due to build tools trying to access file paths that are too long by removing the unnecessary extra deep paths the regression caused. Our CodeGen tool (and the tools that make it like Roslyn) are specifically susceptible to this. ### What Switched the order of the props so that the default for `ReactNativeWindowsDir` is set before using it, not after. ## Screenshots N/A ## Testing Successfully built AppServiceDemo, which was affected by this change. ###### Microsoft Reviewers: [Open in CodeFlow](https://portal.fabricbot.ms/api/codeflow?pullrequest=https://github.com/microsoft/react-native-windows/pull/11464)
2023-04-08 00:20:56 +03:00
<!--
IMPORTANT: Traversals left in a directory will break some tools like midl, but we also cannot call
[MSBuild]::NormalizeDirectory on relative paths since cwd is not always correct. This logic should prefer to operate
on full paths and avoid extra normalization.
-->
Enable integration test web application (#12714) * Create TestServices project
2024-03-21 01:42:33 +03:00
<PropertyGroup Label="NodeNativeDeps" Condition="'$(IgnoreNodeNativeDeps)' != 'true'">
Ensure ReactNativeWindowsDir is set in Directory.Build.props (#11464) ## Description This PR fixes a problem where we use the `ReactNativeWindowsDir` prop to determine where to build intermediate and output files, but we do so *before* verifying that the prop has been set. This regression was introduced in RNW 0.68 and the result is that rather than all build outputs being placed under the root `build` and `target` folders, they are placed deeper in the folder structure. This can cause file paths to exceed the default max path length, which can cause build problems as not every tool supports long paths (even if it's enabled in the system). ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Resolves intermittent issues due to build tools trying to access file paths that are too long by removing the unnecessary extra deep paths the regression caused. Our CodeGen tool (and the tools that make it like Roslyn) are specifically susceptible to this. ### What Switched the order of the props so that the default for `ReactNativeWindowsDir` is set before using it, not after. ## Screenshots N/A ## Testing Successfully built AppServiceDemo, which was affected by this change. ###### Microsoft Reviewers: [Open in CodeFlow](https://portal.fabricbot.ms/api/codeflow?pullrequest=https://github.com/microsoft/react-native-windows/pull/11464)
2023-04-08 00:20:56 +03:00
<ReactNativeWindowsDir Condition="'$(ReactNativeWindowsDir)' == ''">$(MSBuildThisFileDirectory)</ReactNativeWindowsDir>
<ReactNativeDir Condition="'$(ReactNativeDir)' == ''">$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), 'node_modules\react-native\package.json'))\node_modules\react-native\</ReactNativeDir>
<YogaDir Condition="'$(YogaDir)' == ''">$(ReactNativeDir)ReactCommon\yoga</YogaDir>
<FollyDir Condition="'$(FollyDir)' == '' AND Exists('$([MSBuild]::NormalizeDirectory($(ReactNativeDir)..\..\node_modules))')">$(ReactNativeDir)..\..\node_modules\.folly\folly-$(FollyVersion)</FollyDir>
<FollyDir>$([MSBuild]::NormalizeDirectory($(FollyDir)))</FollyDir>
<FmtDir Condition="'$(FmtDir)' == '' AND Exists('$([MSBuild]::NormalizeDirectory($(ReactNativeDir)..\..\node_modules))')">$(ReactNativeDir)..\..\node_modules\.fmt\fmt-$(FmtVersion)</FmtDir>
<FmtDir>$([MSBuild]::NormalizeDirectory($(FmtDir)))</FmtDir>
ABI-safe Hermes API and new JSI for Node-API (#11696) * ABI-safe Hermes API and new JSI for Node-API * Change files * Use Hermes version 0.1.13 that supports UAP * Format code * Merge node-api-jsi project into ReactCommon project * Fix x86 issues * Eliminate Linker warnings * Copy Node-API JSI files to MS.RN.Cxx Nuget * Remove unnecessary settings from shared projects * Format code and fix Layout-MSRN-Headers.ps1 * Fix loading Node-API JSI zip * Remove node-api-jsi project from the playground project * Update Hermes package version * Change files * Fix playground project compilation * Use node-api-jsi with fixes for C++20 * Fix building playground apps * Format code * Make sure that the Hermes inspector works * Update packages.lock.json files * Update Hermes version with fixes for prepared scripts * Use Hermes package 0.1.15 to fix UWP .Net projects * Use SafeLoadLibrary and remove thread Id check for Jsi::Runtime
2023-06-13 07:45:47 +03:00
<NodeApiJsiDir Condition="'$(NodeApiJsiDir)' == '' AND Exists('$([MSBuild]::NormalizeDirectory($(ReactNativeDir)..\..\node_modules))')">$(ReactNativeDir)..\..\node_modules\.node-api-jsi\node-api-jsi-$(NodeApiJsiCommitHash)</NodeApiJsiDir>
<NodeApiJsiDir>$([MSBuild]::NormalizeDirectory($(NodeApiJsiDir)))</NodeApiJsiDir>
Ensure ReactNativeWindowsDir is set in Directory.Build.props (#11464) ## Description This PR fixes a problem where we use the `ReactNativeWindowsDir` prop to determine where to build intermediate and output files, but we do so *before* verifying that the prop has been set. This regression was introduced in RNW 0.68 and the result is that rather than all build outputs being placed under the root `build` and `target` folders, they are placed deeper in the folder structure. This can cause file paths to exceed the default max path length, which can cause build problems as not every tool supports long paths (even if it's enabled in the system). ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Resolves intermittent issues due to build tools trying to access file paths that are too long by removing the unnecessary extra deep paths the regression caused. Our CodeGen tool (and the tools that make it like Roslyn) are specifically susceptible to this. ### What Switched the order of the props so that the default for `ReactNativeWindowsDir` is set before using it, not after. ## Screenshots N/A ## Testing Successfully built AppServiceDemo, which was affected by this change. ###### Microsoft Reviewers: [Open in CodeFlow](https://portal.fabricbot.ms/api/codeflow?pullrequest=https://github.com/microsoft/react-native-windows/pull/11464)
2023-04-08 00:20:56 +03:00
</PropertyGroup>
Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
<PropertyGroup Label="Configuration">
<ProjectName Condition="'$(ProjectName)'==''">$(MSBuildProjectName)</ProjectName>
Use PackageReference for C++ dependencies (#8195) * Migrate `vnext` projects to `PackageReference`. * Allow `run-windows` to directly restore `package.config` files when conflicting with `PackageReference` items. * Allow parameterizing package names and versions which can be handled as any MSBuild property. * Migrate C++ templates to `PackageReference`. * Drop `packages` directory for `vnext` projects NuGet dependencies.\ Dependencies will be accessed directly at the downloaded NuGet `globalPackagesFolder` using `msbuild /restore`.\ This removes redundant copies of downloaded packages.
2021-12-04 10:19:47 +03:00
<RootIntDir Condition="'$(RootIntDir)' == ''">$(ReactNativeWindowsDir)build</RootIntDir>
<RootOutDir Condition="'$(RootOutDir)' == ''">$(ReactNativeWindowsDir)target</RootOutDir>
<!-- Visual Studio forces using 'Win32' for the 'x86' platform. -->
<BaseIntDir Condition="'$(BaseIntDir)' == '' AND '$(Platform)' == 'Win32'">$(RootIntDir)\x86\$(Configuration)</BaseIntDir>
<BaseIntDir Condition="'$(BaseIntDir)' == '' AND '$(Platform)' != 'Win32'">$(RootIntDir)\$(Platform)\$(Configuration)</BaseIntDir>
<BaseOutDir Condition="'$(BaseOutDir)' == '' AND '$(Platform)' == 'Win32'">$(RootOutDir)\x86\$(Configuration)</BaseOutDir>
<BaseOutDir Condition="'$(BaseOutDir)' == '' AND '$(Platform)' != 'Win32'">$(RootOutDir)\$(Platform)\$(Configuration)</BaseOutDir>
<IntDir Condition="'$(ProjectName)' != ''">$(BaseIntDir)\$(ProjectName)\</IntDir>
<IntDir Condition="'$(ProjectName)' == ''">$(BaseIntDir)\$(MSBuildProjectName)\</IntDir>
<OutDir Condition="'$(ProjectName)' != ''">$(BaseOutDir)\$(ProjectName)\</OutDir>
<OutDir Condition="'$(ProjectName)' == ''">$(BaseOutDir)\$(MSBuildProjectName)\</OutDir>
<PublishDir>$(OutDir)\Publish\</PublishDir>
<GeneratedFilesDir>$(IntDir)Generated Files\</GeneratedFilesDir>
Scope down usage of PackageReference (#9647) * Scope down usage of PackageReferences * Change files * Normalize Intermediate and Output paths
2022-03-05 11:35:13 +03:00
<IntermediateOutputPath Condition="'$(MSBuildProjectExtension)' == '.csproj'">$(IntDir)</IntermediateOutputPath>
<OutputPath Condition="'$(MSBuildProjectExtension)' == '.csproj'">$(OutDir)</OutputPath>
Enable NuGet restore lock files for all projects (#12002) ## Description This PR specifies that all projects should set the msbuild property `RestorePackagesWithLockFile` to `true` by default, not just the C# ones. This way we can ensure that PR/CI will build reliably because every locked version should be available in the react-native-public ADO feed. Changes to NuGet dependencies in PRs should now explicilty fail if the new package version is not in the ADO feed, and therefore require us to manually approve the addition to the feed (as required by compliance). Closes #11998 ### Type of Change - Bug fix (non-breaking change which fixes an issue) - Breaking change (fix or feature that would cause existing functionality to not work as expected) ### Why This way we can ensure that PR/CI will build reliably because every locked version should be available in the react-native-public ADO feed. Changes to NuGet dependencies in PRs should now explicilty fail if the new package version is not in the ADO feed, and therefore require us to manually approve the addition to the feed (as required by compliance). Closes #11998 ### What This PR specifies that all projects should set the msbuild property `RestorePackagesWithLockFile` to `true` by default, not just the C# ones. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: no
2023-08-12 01:58:36 +03:00
<RestorePackagesWithLockFile Condition="'$(RestorePackagesWithLockFile)' == ''">true</RestorePackagesWithLockFile>
<RestoreForceEvaluate Condition="'$(RestoreForceEvaluate)' == ''">false</RestoreForceEvaluate>
Initial commit of RNW CPP (#2065) In this branch, we are working on a rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native. Note - ONLY CURRENTLY BUILDABLE USING INTERNAL CREDS We are actively working on removing all dependencies internal to Microsoft. This should be completed in the next month.
2019-02-13 22:47:56 +03:00
</PropertyGroup>
Implicitly restore C++/PackageReference in Visual Studio (#9303) * Set RestoreUseStaticGraphEvaluation * Update packages.lock.json * Ensure using BuildingInsideVisualStudio * Change files * Update packages.lock.json * Move settings into vnext * Enable VS implicit restore in app/lib templates
2021-12-28 03:27:30 +03:00
<PropertyGroup Label="NuGet" Condition="'$(MSBuildProjectExtension)' == '.vcxproj'">
Disable RestoreUseStaticGraphEvaluation for VS >= 17.6 (#11681) ## Description This PR disables `RestoreUseStaticGraphEvaluation` if building within Visual Studio >= 17.6, which is not working in our project. Ideally we want `RestoreUseStaticGraphEvaluation` to improve the build speed. However this will unblock folk trying to build our code within the newest versions of Visual Studio. This does not impact building via MSBuild (i.e. using the `run-windows` CLI command). Resolves #11670 ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Unblock building with VS >= 17.6 Resolves #11670 ### What Adds a check for the version of VS to the condition setting `RestoreUseStaticGraphEvaluation`. ## Screenshots N/A ## Testing Verified I can build `Microsoft.ReactNative.sln` with VS 17.6 and 17.5.
2023-06-01 20:40:01 +03:00
<!-- See https://docs.microsoft.com/en-us/nuget/reference/msbuild-targets#restore-target -->
<!-- RestoreUseStaticGraphEvaluation broke in VS 17.6, see https://github.com/microsoft/react-native-windows/issues/11670 -->
<RestoreUseStaticGraphEvaluation Condition="'$(BuildingInsideVisualStudio)' == 'true' AND $([MSBuild]::VersionLessThan('$(MSBuildVersion)', '17.6')) AND '$(DisableRestoreUseStaticGraphEvaluation)' != 'true'">true</RestoreUseStaticGraphEvaluation>
Implicitly restore C++/PackageReference in Visual Studio (#9303) * Set RestoreUseStaticGraphEvaluation * Update packages.lock.json * Ensure using BuildingInsideVisualStudio * Change files * Update packages.lock.json * Move settings into vnext * Enable VS implicit restore in app/lib templates
2021-12-28 03:27:30 +03:00
</PropertyGroup>
Enable integration test web application (#12714) * Create TestServices project
2024-03-21 01:42:33 +03:00
</Project>