Hi,

The current Kicad build cmake code is a man-made horror beyond my 
comprehension. It's clearly been accreted over the years without a lot of 
understanding of what cmake can do. Admittedly cmake itself is the cause of 
most of the horror, but we can do better.

I'm no cmake expert, but a few days of fixing the code has yielded some 
decent improvements. I expect more significant modularization changes to 
happen as well as the dependency graph is made more explicit. There's a lot 
of zombie code being carried in the Kicad repo for unclear gain, or for 
reasons that no longer apply in 2023.

Having to use kicad-mac-builder is also another pain to get kicad building 
on a Mac, and it is gating my ability to improve Kicad itself. It works, 
but isn't actually needed if the cmake is written correctly. This also 
helps other systems since fewer stuff is added globally, and there's less 
system-specific code in Kicad itself.

I'll also look into rebuilding the install/bundle/app code, as that's its 
own mess. Kicad should not be this difficult to package.

Nimish

-- 
You received this message because you are subscribed to the Google Groups 
"KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to devlist+unsubscr...@kicad.org.
To view this discussion on the web visit 
https://groups.google.com/a/kicad.org/d/msgid/devlist/490e5cea-ff23-4b23-948f-62e88876a916n%40kicad.org.

Reply via email to