Fix cake build project producing debug builds for HarmonyX and Hardware.Info#28
Fix cake build project producing debug builds for HarmonyX and Hardware.Info#28
Conversation
…id Debug builds via cake build project
|
Download the artifacts for this pull request: |
|
apparently is a intended behavior in msbuild dotnet/msbuild#5116 (comment) |
|
wtf happened with the sln file? I don't think it needs all that stuff. also do we really have a problem with using debug builds of stuff? is there any measurable difference? if not, might as well have the extra debug info (whatever that might mean in our case) |
|
We literally ship release builds of everything else, there is no reason why we should be shipping debug builds of HarmonyX and Hardware.Info in production. This was a regression on our end, normal BepInEx does only does release builds as well. As I already explained in the PR Body, we have to add HarmonyX and Hardware.Info (At least HarmonyX if #32 is merged) only the top part is relevant the rest of the stuff was just generated by IDE stuff. I didn't change manually it. solution file is not meant to be tampered with manually, so I let the IDE do it's thing. |
|
Could you do it? I don't have access to my PC for the next few days. This command should remove it. (Idk how it works in VS)
|
For some reason if projects were not added to the BepInEx solution file, they were somehow being built in debug config in the cake build project. This is exclusively happening with the cake build and not when building with
dotnet packfor example. This might be a cake bug.We were distributing debug builds of HarmonyX and Hardware.Info this whole time.
I only found out while trying to figure out why MonoDetour is broken after they added HarmonyX interop. (It's because they prepatch HarmonyX and expect a unoptimized version of HarmonyX.