Hi Rafal,

thanks for the feedback. I think we're on the same page, just have
slightly different thresholds on where the cut is. I think that's OK.
Let's get back to solving actual issues then :-)

Regards,
Ladislav

On Fri, Feb 07, 2025 at 11:30:49AM +0100, Rafał Pietrak wrote:
> Hi Ladislav,
> 
> First of all - I don't think this case is worth any further discussion. I
> fully agree with you, that debian stable has particularly ancient version of
> KiCAD and cmake.
> 
> Having said that....
> 
> On 7.02.2025 09:22, Ladislav Laska wrote:
> > Hi Rafal,
> > 
> > I don't know the details of the protobuf issue. However, I think the
> > comment above says it:
> > 
> >   # Old versions of CMake and/or protobuf can require the 
> > FindProtobuf.cmake,
> >   # but modern platforms require this to be off
> > 
> > Setting this to the ON value would likely break some up to date
> > platform. Other people would have to dig into documentation. In general,
> > recent software should be compatible with recent distributions. Debian
> > 12 relesed on 2023 with kicad 6.0 that released 2021 and cmake 3.25
> > released in 2021. I think this qualifies as older version and you should
> > be expecting to run into issues. I'm surprised this is the only problem.
> 
> Exactly.
> 
> > I wanted to suggest upgrading your distro to fix it, but while writing
> > this paragraph I noticed there seem to be newer cmake & kicad in
> > backports repository. Perhaps this would fix your problems and allow you
> > to build even newer versions? Repo bookworm-backports has cmake 3.31,
> > that should not require this switch. But I haven't tested.
> 
> But here I disagree. As I admit that current software versions (like KiCAD
> v9) should take advantage of new tools as they become available. At the same
> time it's worth keeping compatibility with (at least) one earlier
> "generation" of the "environments". And debian stable is something playing a
> role of such "just previous generation" quite well.
> 
> Then again. IMHO, using cmake (as opposed to automake/make) main purpose is
> that one could easier take into account diversity  of environments - like
> keeping some backward compatibility... I thought (... but I personally never
> needed that. Plain make worked just fine for me, so I'm not particularly
> proficient in tweaking cmake setups).
> 
> But OK. I'm not complaining, and I'm not trying to push anything here. Pls
> have my apologize for triggering this unintended noise on the list.
> 
> best regards to you all,
> 
> -R
> 
> -- 
> 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 [email protected].
> To view this discussion visit 
> https://groups.google.com/a/kicad.org/d/msgid/devlist/e6b9ad31-ec6e-4587-a4e9-195f70fa003f%40electric-sheep.eu.

-- 
S pozdravem Ladislav "Krakonoš" Láska                http://www.krakonos.org/

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/a/kicad.org/d/msgid/devlist/krakonos%2Bmd-20250207.110650.751676.muskox%40krakonos.org.

Reply via email to