Closed barbeque-squared closed 2 months ago
why do we build projectM for Windows each time anyways? Wouldn't just getting the official dll download be a better fix while also saving buil-pipeline minutes?
why do we build projectM for Windows each time anyways?
We don't. The CI just thinks that it will be asked to build the .vcproj file.
example: https://ci.appveyor.com/project/basisbit/usdx/builds/49748770
I can't do anything with this error as it's a Windows thing. I like the part where github isn't showing failed pipelines, hence I only noticed it now. It apparently also prevents the non-Windows builds from being built. I know there's plans to move away from AppVeyor but right now this is blocking making a new release.
For completeness future reference, the entire build output is:
Possible solutions Well, let's be real, we should probably just fix the CI. The other option would be to just stop using ProjectM, which although I'm personally totally in favour of, this is the wrong reason to drop it.