omartijn

@JackBoosY It seems the pipeline failed `x86_windows`, but not with any error I can understand. Looks like the "Test Modified Ports and Prepare Test Logs" failed, but the message simply...

@JackBoosY: Can you shed a light on this build failure: https://dev.azure.com/vcpkg/public/_build/results?buildId=66849&view=logs&j=878666d5-db33-5b27-9e7d-b0c7ee352005&t=d914c609-a9aa-5880-221f-cbd46db9069e It says it's failed, but I don't understand why.

Thanks, @JackBoosY, I would have never guessed that from the output!

> Can you please resolve the file conflicts? > > Thanks. Certainly. I thought I had, but I think I must've rebased on an older version of the master branch....

> What would a generic way to do it in the tool look like? Would we actually do the complete build/install for the packages for each architecture required? That way...

> Can you please merge to master first? I guess you mean "merge master in first"? Just as an aside, merging to master would be when we finally get this...

> > Is this related to your changes? I'd be very surprised if it were, given that the changes are only enabled on macos. It's possible I made a mistake...

I've tried building the package on the master branch, and that also failed in the `mesa:x64-windows` package. So it seems the package is simply broken.

I've taken a look into using `rel_command` and `dbg_command`, and I cannot get it to work the way I expect. I have tried removing the `CMAKE_INSTALL_PREFIX` from both commands and...

Yes, there are many ports where this won't work. Another example of this was `ffmpeg`, for which a custom build-script was written to enable this functionality. Maybe we can find...