Ok, big news! It turns out the crashes when using the push and shove/route around routing mode were entirely my fault and caused by how I was handling the boost dependency. I’ve fixed this issue with the tap, the router now works flawlessly!
Additionally, I believe I have fixed the issue that has been preventing compilation on OS X 10.7 and 10.8. I hope. Let me know!
Oh, since the formula updated, don’t forget to run brew update first. Then install kicad as normal, or for people who have already installed, you can run brew reinstall kicad --without-kicad-library to update to the latest revision and to build it such that there are no routing issues anymore.
I added the needed ARCHFLAGs, please brew update and try again. And I apologize, I know its not fun waiting on a huge build just to get an error. I am pulling the patched wxpython out into it’s own formula, which should cut down on build times considerably.
@Airic: What version of OS X are you on again? Can you dump the verbose build output to a file and gist it or attach it or whatever you prefer?
No worries at all! I’m sure it isn’t fun to have a bunch of people complaining about your project not working either; I appreciate your hard work in making life easier for the rest of us
That said, I just updated and tried it again but I get the same error
unfortunately the routing error still exists. Also, when switching to OpenGL I loose all scroll bars and also the ability to right click, which makes this mode unusable. I built today (1. Feb) and I am on OS X 10.10. Anyone else having this problem?
Hmmm, this is odd, it builds fine and without scroll bar issues or the routing crashes on my system. I have none of those issues you’re having, Markus. There is something different between our Yosemite systems, but given I’m the only one not having issues, I suspect I’ve done something on my system that I’ve overlooked and forgotten to include in the formula, rather than something unusual causing breakage on your system
I’m installing 10.7 and 10.8 in a virtual machine to see what’s up, I’ll get to the bottom of this, sooh I hope.
Hmmmm. I do have all the dependencies built with the --universal flag set, and also Cairo --without-X11. And I pointedly do not have the homebrew version of Python installed, or have any $PYTHONPATH set. I’m not going to ask anyone to unset PYTHONPATH and reinstall all the dependencies with my flags… It probably won’t change anything but if anyone is desperate, who knows.
For now, if all the people experiencing experiencing compilation failures or issues besides non-working pull down menus (especially push and shove crashes) problems could post or send me via message the output of brew --config, it might help me resolve these issues sooner.
just having installed the windows version, I see also the missing scroll bars when switching to OpenGL thus rendering the push and shove router unusable. I suspect this to be a kicad problem, not a install problem!
One more thing: where do I need to place the freeroute.jar file? The bin folder does not work…
Thanks a lot for your great work. You are really filling the gap for OS X users diving into KiCad!
I recently, about 3 months ago, successfully compiled myself the KiCad sources for OS X Yosemite (10.10.1). Not without much trouble. As I want to stay on the bleeding edge of the latest KiCad development versions, I am now trying your homebrew tap.
Is there anything you would like me to test? I’d love to lend you a hand on this.
All was working well with my build (listed in kicad as after 2015-jan-16 BZR unknown) until I tried routing today and I also ran into the ‘route around’ issue. You asked for others experiencing the problem to post info so here it is. Thanks for the great work by the way!
–Matthew
I tried to update by first running brew update and then I ran brew reinstall kicad --without-kicad-library and got the following errors:
Because I thought there is a newer build, I tried to rebuild and got an error
You must `brew link glib’ before kicad can be installed
I found out, that the user rights seemed to be the problem, I did a
sudo chown -R $USER /usr/local
afterwards, KiCad built fine, and I cannot duplicate the crash error anymore! You might want to try!
Still, can anybody tell me in which directory the freerouter.jar file needs to go to be recognised by Pcbnew???
Just wanted to tell everyone that I’m not dead. I’ve had a drought of spare time lately, so it’s taken quite some time to finish any update, as I’ve only been able to work on it in brief spurts over the past couple weeks+. The good news is everyone’s debug posts were extremely helpful and I believe I’ve located several problems that are causing all this seemingly different issues.
I’m hoping to post it any day now (I am shooting for today, but I am not too confident I will manage that, sorry. And thanks everyone for your patience.
On the plus, when I do finish it, it’s been completely reworked essentially from scratch. It also has cut out wx and wxpython into their own keg-only formula, meaning those will only need to be built the first time and will be reused after that. This makes kicad build in less than 1/3rd the time it currently takes, at least on my system. That should make things a bit less painful for everyone.
Markus: you can put freerouter.jar in the same folder as the Kicad.app (the actual .app, not the alias. Right click on the alias in your /Applications folder and select ‘Show Original’ and just drop freerouter.jar in the window that opens up).
Oh snap, while I was typing that, some problems I had been stuck on were fixed by my latest changes, and everything built successfully. A release later today is looking a lot more likely! I still need to check to see if this resolved a problem on earlier versions of OS X, so gotta wait on a virtualized 10.7 build, but things are looking pretty promising.
Tried a to build but got an error during the install KiCad stage. I’m using 10.10.2. I have a previous version of KiCad installed (not using brew). I’ll update brew formulas and uninstall the previous version of KiCad. Below is the last part of the output from the build, in case it gives any pointers.
OK, everyone, please run brew update to pull in the latest changes from the tap, then give it one more try. I’ve committed a ton of fixes and I am hoping I’ve finally got most, or hopefully all, of these issues sorted and it should finally begin working for the majority of users. Sorry for all the problems. For a while it seemed like fixing one issue would also cause 2 new ones, so it was a long and drawn out mess of commits.
I shouldn’t be nearly so busy now, so if there are remaining issues, I will try to fix them as quickly as possible.
Thanks for your efforts! I just compiled it but I still got the “route around crash”. It takes longer to make KiCAD crash but it still does. Everything else seems to work wonderfully and I certainly can live without the “route-around” feature!
I have a compile log and a crash report - let me know if any of those would be of any value - I’d send them to you via post mail.