EEVblog Electronics Community Forum

Electronics => PCB/EDA/CAD => KiCad => Topic started by: westfw on January 15, 2021, 09:40:17 am

Title: Churn, especially WRT Mac...
Post by: westfw on January 15, 2021, 09:40:17 am
I decided to give KICAD another chance on my main computer.  A Mac (actually, a "Hackintosh"), running MacOS 10.13.6
The most recent KICAD won't run on 10.13.Older versions of KICAD will run, but apparently cant' read (OSHW) files generated with the newer versions. :-(
While I realize that maintaining backward compatibility can be a trap, this seems a bit extreme in the opposite direction :-(  10.13 (High Sierra) is only about 3 years old :-(
Title: Re: Churn, especially WRT Mac...
Post by: MitjaN on January 15, 2021, 05:10:19 pm
You might want to read the topic at:
https://forum.kicad.info/t/compiling-kicad-for-macos-high-sierra/25186/14
Title: Re: Churn, especially WRT Mac...
Post by: Bassman59 on January 15, 2021, 10:37:29 pm
I decided to give KICAD another chance on my main computer.  A Mac (actually, a "Hackintosh"), running MacOS 10.13.6
The most recent KICAD won't run on 10.13.Older versions of KICAD will run, but apparently cant' read (OSHW) files generated with the newer versions. :-(
While I realize that maintaining backward compatibility can be a trap, this seems a bit extreme in the opposite direction :-(  10.13 (High Sierra) is only about 3 years old :-(

Kicad has never guaranteed that older versions can read files created by newer versions.
Title: Re: Churn, especially WRT Mac...
Post by: Bassman59 on January 15, 2021, 10:40:01 pm
While I realize that maintaining backward compatibility can be a trap, this seems a bit extreme in the opposite direction :-(  10.13 (High Sierra) is only about 3 years old :-(

There was a lot of discussion about this among the developers, and basically it came down to dealing with the moving targets of the dependencies.
Title: Re: Churn, especially WRT Mac...
Post by: delfinom on February 12, 2021, 01:30:18 am
While I realize that maintaining backward compatibility can be a trap, this seems a bit extreme in the opposite direction :-(  10.13 (High Sierra) is only about 3 years old :-(

There was a lot of discussion about this among the developers, and basically it came down to dealing with the moving targets of the dependencies.

Apple is really the driver here. The newer macOS can't build for the old ones too easily. Our only macOS packager doesn't have the luxury of multiple machines. Apple has declared 10.13 obsolete on January 31st 2021 as well.

You can still build for 10.13 if you desire, it's open source, it's just not something that can be officially provided.