As with any major version upgrade, it will make your projects and libraries incompatible with v6. Obvious, but something to think about if you're collaborating with people who may have not upgraded.
KiCAD 7 is not able to integrate my personal libraries, although they have the same names, format, location etc. And there's no function in 7 to fix this.
I have to add each and every personal library manually, which is intolerable.
Won't work, don't try that, please.KiCAD 7 is not able to integrate my personal libraries, although they have the same names, format, location etc. And there's no function in 7 to fix this.
I have to add each and every personal library manually, which is intolerable.
Yes, you need to re-add every non-standard library manually, that's pretty time-consuming if you have many of them.
It may be possible to do this faster by copying the list directly from the corresponding v6 configuration file to the v7 one, although I'm not completely sure if that's all that's required.
Won't work, don't try that, please.KiCAD 7 is not able to integrate my personal libraries, although they have the same names, format, location etc. And there's no function in 7 to fix this.
I have to add each and every personal library manually, which is intolerable.
Yes, you need to re-add every non-standard library manually, that's pretty time-consuming if you have many of them.
It may be possible to do this faster by copying the list directly from the corresponding v6 configuration file to the v7 one, although I'm not completely sure if that's all that's required.
I've found a (somewhat involved) solution, but am flabbergasted that the developers didn't even think that it's an issue. People don't use personal libraries?
Won't work, don't try that, please.KiCAD 7 is not able to integrate my personal libraries, although they have the same names, format, location etc. And there's no function in 7 to fix this.
I have to add each and every personal library manually, which is intolerable.
Yes, you need to re-add every non-standard library manually, that's pretty time-consuming if you have many of them.
It may be possible to do this faster by copying the list directly from the corresponding v6 configuration file to the v7 one, although I'm not completely sure if that's all that's required.
I've found a (somewhat involved) solution, but am flabbergasted that the developers didn't even think that it's an issue. People don't use personal libraries?
The flip side of the coin is if you start using your old libraries under V7 and end up saving them, it's file format will get upgraded and become incompatible with V6. Meanwhile a user may want to use KiCad 6 and 7 in parallel where they just use KiCad 6 for older designs.
The flip side of the coin is if you start using your old libraries under V7 and end up saving them, it's file format will get upgraded and become incompatible with V6. Meanwhile a user may want to use KiCad 6 and 7 in parallel where they just use KiCad 6 for older designs.
/home/me/.config/kicad$ meld 6.0/sym-lib-table 7.0/sym-lib-table
I wonder why doesn't kicad have automatic update feature without the need to download new installer and so on
It's a much harder task than it seems.
but now when going from 7.0.0 to 7.0.1 i will remove old package and install the new one. will this affect my libraries and so on?
Really? You sound angry. ;D
I don't know about MacOS, but I have no difficulties building KiCad from source, both on Linux and on Windows. Even using MSYS2 on Windows, which the KiCad team has seemingly deprecated, but it can still be done.
Maybe you can report your build issues on the KiCad forum: https://forum.kicad.info/
Out of curiosity (I don't use MacOS currently), can you tell us what kind of hack is required? You said too little or too much.
Really? You sound angry. ;D
I don't know about MacOS, but I have no difficulties building KiCad from source, both on Linux and on Windows. Even using MSYS2 on Windows, which the KiCad team has seemingly deprecated, but it can still be done.
Maybe you can report your build issues on the KiCad forum: https://forum.kicad.info/
Out of curiosity (I don't use MacOS currently), can you tell us what kind of hack is required? You said too little or too much.
On a Mac, you need `kicad-mac-builder`, a whole separate repo of cmake scripts. They have their own issues.
They also are unnecessary if the core kicad build scripts were maintained properly. Even for at-the-time cmake, which admittedly sucked hard, they aren't using best practices.
I'm upstreaming my fixes to the build as I modularize them. I've lost enough time to weird Kicad quirks.
Are there any hints about when a stable version is being released on Fedora? I'm weighing up whether I should uninstall the native install and go with a flatpak from now on, as flatpak seems to be a prioritised release format with a few software packages I've seen.
Really? You sound angry. ;D
I don't know about MacOS, but I have no difficulties building KiCad from source, both on Linux and on Windows. Even using MSYS2 on Windows, which the KiCad team has seemingly deprecated, but it can still be done.
Maybe you can report your build issues on the KiCad forum: https://forum.kicad.info/
Out of curiosity (I don't use MacOS currently), can you tell us what kind of hack is required? You said too little or too much.
On a Mac, you need `kicad-mac-builder`, a whole separate repo of cmake scripts. They have their own issues.
They also are unnecessary if the core kicad build scripts were maintained properly. Even for at-the-time cmake, which admittedly sucked hard, they aren't using best practices.
I'm upstreaming my fixes to the build as I modularize them. I've lost enough time to weird Kicad quirks.
Ok, I see. I really haven't looked into the Mac build thing.
I can confirm the cmake stuff is not all that great though for all platforms.
For the lack of a better place to ask, I'll use this thread: can KiCAD do interactive simulation? Such as e.g. Proteus, where you can build a ciruit, hit a "play" button and watch how the probe measurements change in (quasi) real time, use virtual oscilloscope, push buttons and toggle switches interactively, etc.
I tried it once in the past but couldn't find anything for interactive simulation. Maybe I overlooked something obvious.
Proteus works, but it's not Linux-native, so I have to use wine, and a pirated copy as well, which sucks. I'd much prefer something that's FOSS and Linux-native, if it's at all available.
It took me two days to fix the build to work properly on a Mac without their awful builder hack, and that's before adding any features.
Are there any hints about when a stable version is being released on Fedora? I'm weighing up whether I should uninstall the native install and go with a flatpak from now on, as flatpak seems to be a prioritised release format with a few software packages I've seen.
My understanding is that 7.x will be part of next Fedora release (38) in late April. It's policy with a few exceptions to not update software major versions during a Fedora version life cycle. So major releases often end up in next version of Fedora.
Why 'without their awful builder hack'? As much as its existence and/or necessity may annoy you, doesn't it make sense to use the same build tooling used by the project's other developers and release pipeline? Improving the build process is a laudable goal in itself, but you don't seem interested in that, so why not just use the existing tooling?
If a major revision takes place its common in software to add in version data converters.
Like V6 to V7 that converts all the file formats accordingly.
The Arch based Manjaro offered the new KiCAD in the latest group of updates. I installed it, because i have not done much, if anything, with KiCAD in the last year.
But now i am a bit curious. I am relatively new to Linux as a daily driver, and until now i always just installed everything that the updater presented.
How should i have proceeded if, for compatibility reasons, i would not want to upgrade KiCAD? It was just a single entry in a large list of hundreds of updates, i could easily have missed it.
How would i do a downgrade? Looking for KiCAD in the repository only shows the latest version.
I have a personal library, but each symbol is in its own .lib file and .pretty folder. To use one I copy it to a project as needed; this may seem like redundant copying, but it ensures each project is self-contained so if someone else clones it they don't get a bunch of dead library references, and I don't have to share my entire collection of symbols.
Not because I would mind, but because some are embarrassingly ad-hoc.Time to do some maintenance and clean up your mess...
There's an inherent value in not needing anything other than a single repo for a project, including firmware, openocd config, gdb macros, fonts, python build help tools, etc if relevant.Yes, of course, but starting from KiCad V6, you just need 4 files, the project file, the kicad_prl file and the schematic and PCB files. Libraries are optional.
The other is that if I change the symbol to fix something in project B it will likely break project A;No it won't anymore,because of the embedded symbols. KiCad does maintain a link to the original source of schematic symbols (so you can update them if you want, and ERC warns you if your symbol is different from the libary symbol, but updating it is a manual process as it should be.
In fact, I wish kicad would handle this automatically, that when I add a symbol from a library to a project, it makes a local copy of it in the project.So again, indeed this is what KiCad does now. but because that copy is directly in the schematic file you had not noticed it. If you do not believe me, then check it yourself:
If I want to update them I could easily just replace them with an updated version later.Indeed, KiCad also supports this now. It makes a local copy, but a link to the original source is maintained, so you can easily update schematic symbols if the "master library" changed.
My experience has been that sharing a single lib file between multiple projects tends to create a lot of problems in the long term. Not just related to changes to the symbol, but also some projects might still even be kicad v5 while libraries might have gotten updated to v7.
How does KiCad compare to Altium? I want a simple software that doesn't require hours and hours of training to get comfortable with. Easyeda looks pretty simple to use.
How does KiCad compare to Altium? I want a simple software that doesn't require hours and hours of training to get comfortable with. Easyeda looks pretty simple to use.I migrated from easyeda to kicad. Way better imo, it's not that difficult actually, you just have to learn a few idiosyncrasies of the software. I think that that training is required just to use it at the best of its capabilities. You can use it just like easyeda, no problem. But I think that learning it better is a good use of your time