Airwindows 2.13.0

AirWindows 2.13.0 on Windows 11 tries to update and fails every time.

Relevant lines in log.txt:

[0.080 info src/plugin.cpp:269 extractPackages] Extracting package C:/Users/Kent Williams/AppData/Local/Rack2/plugins-win-x64/Airwin2Rack-2.13.0-win-x64.vcvplugin Loading plugin from C:/Users/Kent Williams/AppData/Local/Rack2/plugins-win-x64/Airwin2Rack [0.663 warn src/plugin.cpp:237 loadPlugin] Could not load plugin C:/Users/Kent Williams/AppData/Local/Rack2/plugins-win-x64/Airwin2Rack: Failed to load library C:/Users/Kent Williams/AppData/Local/Rack2/plugins-win-x64/Airwin2Rack/plugin.dll: code 12 log.txt (415.8 KB)

I know that’s not a solution, but few month ago somebody here recommended me the “Nightbin” module by Questionable Modules, which updates Airwindows and other modules with github repositories straight from github. And I updated Airwindows to 2.14 without any problems, using this Nightbin thing.

1 Like

How long have you been running Rack on this particular machine? It looks like you have a space in your username, and therefor in the path to all Rack files and plugins. There’s been several cases where this has proven to be a bad idea, and other programs might choke on that as well. If I were you I would definately change that username/path if you can.

Ah, never mind, it looks like it’s this one:

Rack itself has solved the problems with spaces and non-ASCII in paths. These are, after all, perfectly valid paths on the operating system. Rack provides correct and safe file APIs in the system namespace.

Any such issues are a bug in the plugin and should be reported to the developer. Unfortunately, the issue may be a bug in a dependency that the developer isn’t able or willing to pursue.

If that’s too much swimming upstream to get developers to fix their bad code, then yeah, remove spaces and non-ASCII in your paths, including your user name.

That’s not the case here though. This looks like the tool chain ejecting a bad binary somehow since the nightly works. Rack team reverted the library to 2.12

There was an issue where the toolchain cpp lib would crash on windows. A lot of us got bit by that. If that’s the issue, I think there was a toolchain update to fix that? btw, I had that bug for like 5 years. I just wrote my own stdlib functions…

In this case the older tool chain nightly works and the library official does not. Ring any bells?

Airline is lots of code. Gcc bigobj issue maybe?

Sounds familiar. Ask @cschol ?

Oh, here are some of the closed issues that I logged. Looks like they were from 2021.