Running the Windows version of Kicad in Wine: cannot copy global symbol library table file

Hi All,

I was bored, so I tried to run the windows version of Kicad in Wine. This works fine, until Kicad tries to copy global symbol library table file. I’ve made a wine bug report:

Should I make a bug report here as well, or is running Kicad in Wine unsupported?

Yes Cedric, I agree you were bored :wink:
I’m a native Spanish speaker who speaks English quite well but not perfectly.
So instead of writing an email in Spanish, I write it in English and then I use googletranslator.

Apparently you were not bored enough or you would have tried to run Kicad in Wine in WSL on Windows.

1 Like

Since by definition anything that works on real Windows is executing correctly, the fault then lies with Wine. However there might be some value to the Wine project to figure out where it goes wrong and if it can be avoided by programmers. The fact the KiCad source is open might help. Then again nobody may have the time to look into it, bugs longa, vita brevis. Maybe it could be your next boredom project?

My hunch is that KiCAD figures out at runtime if it’s running in Windows or Linux, and then chooses the location of the global library table file accordingly.

Where is the code that makes that decision? I guess that code is looking for something that wine is presenting differently to the program than real windows is doing.

Which is just another way of saying that Wine is not doing a sufficiently convincing job to the application.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.