ShuriZma
/
BizHawk
mirror of https://github.com/TASEmulators/BizHawk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Actually fix indentation in project files

This commit is contained in:
James Groom 2024-05-10 18:38:26 +10:00 committed by GitHub
parent 702080e582
commit 1c33e2bad8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ExternalProjects/NLua/NLua.csproj
View File

@ -28,6 +28,6 @@
</PropertyGroup>
<ItemGroup>
<PackageReference Include="System.Memory" />
<PackageReference Include="System.Memory" />
</ItemGroup>
</Project>

4
ExternalToolProjects/DATParser/DATParser.csproj
View File

@ -14,10 +14,10 @@
<Compile Update="DATConverter.cs" SubType="Form" />
<Compile Update="DATConverter.Designer.cs" DependentUpon="DATConverter.cs" />
<Compile Update="Properties/Settings.Designer.cs" AutoGen="true" DependentUpon="Settings.settings" DesignTime="true">
<DesignTimeSharedInput>True</DesignTimeSharedInput>
<DesignTimeSharedInput>True</DesignTimeSharedInput>
</Compile>
<None Update="Properties/Settings.settings" LastGenOutput="Settings.Designer.cs">
<Generator>SettingsSingleFileGenerator</Generator>
<Generator>SettingsSingleFileGenerator</Generator>
</None>
</ItemGroup>
</Project>

8
src/MainSlnExecutable.props
View File

@ -2,19 +2,19 @@
<Import Project="MainSlnCommon.props" />
<PropertyGroup>
<!-- Output path will contain the executable along with all its dependencies. We copy the executable up one directory up later on.
This allows us to have the executable dependencies automagically copied over to our dll folder while still keeping the executable in the output folder. -->
This allows us to have the executable dependencies automagically copied over to our dll folder while still keeping the executable in the output folder. -->
<OutputPath>$(MSBuildProjectDirectory)/../../output/dll/</OutputPath>
<ExecFilesDest>$(MSBuildProjectDirectory)/../../output/</ExecFilesDest>
<!-- Setting TargetFileName does not change the AssemblyName (as setting TargetName would), but also does not change the output file name
for the executable on build (as one would expect). So we still need to rename the executable file below. Using this method has the advantage
of IDEs respecting the TargetFileName and expecting it. -->
for the executable on build (as one would expect). So we still need to rename the executable file below. Using this method has the advantage
of IDEs respecting the TargetFileName and expecting it. -->
<TargetFileName>$(MSBuildProjectName.Substring($([MSBuild]::Add($(MSBuildProjectName.LastIndexOf('.')), 1)))).exe</TargetFileName>
<!-- This also doesn't actually change where the executable is output, rather it's just a hint to the IDE to know where the executable is (since we move it). -->
<TargetPath>$(ExecFilesDest)$(TargetFileName)</TargetPath>
</PropertyGroup>
<ItemGroup>
<!-- This is somewhat wasteful for DiscoHawk, but it still relies on some unmanaged libraries
Note that LinkBase is simply something added to OutputPath, it doesn't replace it -->
Note that LinkBase is simply something added to OutputPath, it doesn't replace it -->
<None Include="$(MSBuildProjectDirectory)/../../Assets/**/*.*" LinkBase=".." CopyToOutputDirectory="PreserveNewest" />
</ItemGroup>
<PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">