Closed bilhox closed 1 month ago
I see the root problem as the buildconfig being too picky about dependency versions. If the new bundled is 2.30.7 and I only have 2.30.6 downloaded it should still build fine.
But I see why the meson buildconfig was written the way it was, it's not trying to change too much stuff from the setup.py buildconfig, so it doesn't change the directories so that the SDL version number isn't in the directory name.
This was kinda intentional really. As starbuck said, it just follows closely what the old buildconfig is doing. So I don't see anything that needs fixing here
@ankith26 As I said, it's more an enhancement proposal (forgot to add the label btw). I know it's intentional, but could be interesting to make the install program smarter.
Hmm, thinking about it, I think the current behavior is actually better than what you propose because it gives the developer more control. With the current system, you just gotta delete the existing prebuilts folder to force an upgrade.
Now I'm not a windows user, but I can see the usecase for a dev downgrading SDL. If the buildconfig is going to "auto upgrade", it may lead to conflicts
I think there might be a better solution, proposing a better error message if it fails to find the correct version.
Hello,
First of all, this is more an enhancement proposal. A fast solution is just to delete
prebuild
directories, and let meson (download_win_prebuilt.py
) recreate them.Currently this is how meson checks if libraries are downloaded and download them if it's not the case :
As you can see it only checks if the directory is here. So basically if the version does not match with the downloaded version, it should delete the directories, and redownload them.