reinstalling patchutils...
reinstalling pkg-config...
reinstalling quilt...
-- Success 0: pacman --noconfirm -S base-devel
-- lock file exists
-- Running pacman --noconfirm -S git
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
CMake Error at KiCad-Winbuilder.cmake:285 (message):
Error running pacman --noconfirm -S git
Output in: C:/kb/.logs/last_error
Call Stack (most recent call first):
KiCad-Winbuilder.cmake:333 (execute_msys2_bash)
Path length does not seem to be the issue, I hacked KiCad-Winbuilder.cmake to just install git at line 319, and that fails too. It appears that line 318 runs ok but leaves a lock file… weird.
It appears that the build script is reinstalling quilt package which actually fails with no error message, and leaves lock file and quilt package corrupted.
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/quilt-0.65-2/desc: No such file or directory
warning: could not fully load metadata for package quilt-0.65-2
error: failed to prepare transaction (invalid or corrupted package)
CMake Error at KiCad-Winbuilder.cmake:285 (message):
Error running pacman --noconfirm -S base-devel
– Found ngspice: C:/msys64/mingw64/include
CMake Error at CMakeLists.txt:583 (find_package):
By not providing “FindOCE.cmake” in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by “OCE”, but
CMake did not find one.
Could not find a package configuration file provided by “OCE” (requested
version 0.16) with any of the following names:
OCEConfig.cmake
oce-config.cmake
Add the installation prefix of “OCE” to CMAKE_PREFIX_PATH or set “OCE_DIR”
to a directory containing one of the above files. If “OCE” provides a
separate development package or SDK, be sure it has been installed.
– Configuring incomplete, errors occurred!
See also “C:/msys64/home/palcobia/kicad-build/src/MINGW-packages/mingw-w64-kicad-git/src/build-x86_64-w64-mingw32/CMakeFiles/CMakeOutput.log”.
See also “C:/msys64/home/palcobia/kicad-build/src/MINGW-packages/mingw-w64-kicad-git/src/build-x86_64-w64-mingw32/CMakeFiles/CMakeError.log”.
==> ERROR: A failure occurred in build().
Aborting…
Is there a Known Good development image with everything set, that we can use strait out of the box? I could put my efforts in coding instead of spending so much time doing boring and unproductive stuff like setting up the environment. It would be much appreciated. I just wanted to add a few features to Eeschema, test them and share it with the community but I’m finding it hard to start. feels like “Aborting…”
A quick workaround would be to try building with -DKICAD_USE_OCE=OFF in your cmake command line.
Also I recommend joining the developer’s mailing list if you haven’t already, it’s a better place to discuss issues about development and get feedback on your new features.
I recently built KiCad from scratch on Windows and took some notes about what I had to do over on this launchpad issue.
You put the -D options in the cmake command line, in “MSYS2 the Hard Way”
I am pretty sure the “easy way” doesn’t work at the moment, but I was able to get it built using the “hard way”
I added some notes a few weeks ago under “Known MSYS2 Build Issues” below – you need to either disable OCE with the cmake flag, or build it from source.
I just tested the instructions on my Windows 10 VM and confirmed that they do work on a fresh msys2 installation.
I pushed some updates to the documentation to remove the “easy way” because it is currently broken.
The hard way is not too hard, just a few more steps to follow
Please let me know if anyone has trouble building following those instructions. Keep in mind you do need to update your msys2 packages using the pacman command in the first paragraph before you try building KiCad.
Thanks to @craftyjon, I finally got a Windows build! I had to abandon the kicad-winbuilder script and go off piste, it helps to have experience with Unix and cmake etc.
After I wrote that guide I also updated the official build docs. I found that on a fresh Windows 10 / mingw64 install after updating all the mingw packages, I didn’t need to build ngspice from source.
I also got confused with mingw-w64-ngspice-git, which is a dependency for KiCad in PKGBUILD, not mingw-w64-ngspice.
Also confused by Kicad-winbuilder which seems to overwrite the latest PKGBUILD with its own, older version.
Later I will try doing a fresh build with latest instructions, and see how it goes. Maybe this time I will remember to write down exactly what I did
I had to abandon the kicad-winbuilder script and go off piste, it helps to have experience with Unix and cmake etc.