As a first time user it took a while to get it working. Had some errors running Make. Then realised that I needed to create the folder on my C drive - error seemed to be linked to me having initially placed folder on my D drive.
Also on first run, make sure you have loads of time… I’m running a dinosaur quad-core and at least 2hrs to get made
Mine builds on D drive…
Hmm. Is it linked to the folder name I wonder? Installed mine in a renamed folder in the root of D. Logged as a bug anyway, will see what the clever folks come back with
I’ve unzipped the winbuilder directly into the D:\ root, didn’t change the folder name (so it lives in d:\kicad-winbuilder-3.4).
But I did the builds with different folder names too, I don’t remember having issues because of that. Just avoid putting it in subfolders or having spaces in the folder name…
And yes, check available space, damn thing grows a lot during the build process.
Where did you download it from. I use Bitdefinder and said it had Trojan.Arcbomb.bzip virus in it.
I got it from here, although I seem to be cursed - it didn’t work on first or second go. Eventually, I edited the KiCadWinbuilder.cmake file, changing the line:
set( DOCUMENTATION ON )
to
set( DOCUMENTATION OFF )
I was getting the error:
– Installing KiCad locally. Use RunKiCad.bat to run this version
CMake Error at KiCadWinbuilder.cmake:1051 (file):
file COPY cannot find “C:/kicad-winbuilder-3.4/src/doc/doc/help”.
Then it worked like a dream, but no documentation which I was ok with.
Good luck, and let me know if you win
I downloaded it still had the trojan so I will just wait until comes out in an installed version.
thanks for the help
Have you logged it to the Winbuilder team that your A-V is reporting a trojan so they can look into it? This could affect other users, or perhaps your A-V is giving a false-positive?
Looking at other posts, there doesn’t seem much clarity on when (or if!) an installation file will be released - latest was in 2013…
I have not done that but I will. Thanks for reminding me.
I downloaded and un-zipped it. Biddefender remove the code it thinks is a virus.
I did let the guy know, no response yet.
Where did you download the Kicad source from? Guess you can tell I am a bit new at this.
It just finished building. Ver BZR 5067 seems to work.
@James_Cullins just did the same with winbuilder-3.4 and can confirm that there were no build errors.
I have to ask a question though: Has anyone experienced the search in the “choose component” (Hotkey: A) dialog in EEschema to be extremely slow on Windows builds using winbuilder? It seems like it starts the search immediately when entering the first character and it freezes until it has listed all componens/libraries containing that character until I can enter another character. Then it goes through the whole procedure again with that substring etc.
I have to say that is the bug that is currently slowing down my work flow the most.
I am experiencing this error ever since I started building using winbuilder-3.3
I checked mine and it works well in getting parts after I clicked on the + by the lib name. Are your other programs working normal?
Mine just hung up, had to use Task Manager to kill it.
I did notice it slow with footprints but I think that is because it pulling from Gethub. Maybe if the were local it would work better.
I have removed Winbuilder. I have another computer and will try UBUNTU and KiCad.
I also faced similar issues with the recent winbuilder.
However, I found this website which offers automatic builds for both Linux and Windows
The only thing I still needed to do was set a simple .bat script to set the ENV variables for the library tables before running KiCad. (Similar the the RunKicad.bat of Winbuilder)
Thanks for the link, I’ll have a look
Downloaded installed and so far working well.
I built kicad correctly using Winbuilder a week ago in 3 hrs in a Win7 vm on an i7 t420 Win 10 thinkpad host.10. Winbuilder was great, and I hope the first update goes without a hitch when I try.
By the way… I copied the \bin directory from the vm to the host, and RunKCad, eeschema and pcbnew all seem to work correctly. Is that an ok way to install kicad on another machine? I need the same version of kicad on another laptop, it would be nice to just copy the directory again.
The way the trojan arrives ressemble the infection vector for crryptic malware. It is a deadly poison for computers. Behold! http://nabzsoftware.com/types-of-threats/ccc-file