Open jameswalmsley opened 8 years ago
Been working on it myself on OSX. I'm using homebrew as a package manager, so I had to make sure Kicad was pointing to the correct python. Right now I'm calling the following from within the BOM manager:
/usr/local/bin/python "/Users/red/Documents/!PC_Shared/KiCad_REDS_PROJECTS/BOM_Exporters/Boms-Away/bomsaway.py" "%I" "%O"
It's opening a blank wx window without any parts.....what am I missing?
@mizraith: This isn't a kicad bom exporter, it's a standalone application that directly reads/writes kicad schematics.
Just launch it by itself, then open your top-level schematic file using file->open.
Sidenote: I no longer have access to an OSX machine, Anyone with access to one who would be willing to write up some basic instructions would be greatly appreciated :)
Jeff -- THAT TOTALLY HELPED! I was completely dumbfounded as to "what to do next"..... I suggest that your main Read Me file has a section on what to do once you get to the main screen, because that is where I was stuck....
Instructions follow that should work for a reasonably mac-savvy user.
You will need to have the following fields in this order:
Question: Can BOMs-Away handle additional fields, like Description, Notes
Ability to use Terminal, or at least get yourself into and out of trouble.
brew install python
pip install sqlalchemy
brew install wx
(or use pip install
. Both seem to work)which python
to make sure you are using the homebrew pythonpython
launch your instance and >>>import sqlalchemy
and >>>import wx
to verify that you have properly installed the required packages.cd /directory/where/you/want/bomsaway/to/live
git clone https://github.com/Jeff-Ciesielski/Boms-Away.git
(I think git is standard on OS X now...if not, then brew install git
)
cd /path/to/your/kicad_project_directory
HINT: on the mac you can drop a folder into the Terminal window to resolve the path...saves on typing.
2 python /path/to/bomsaway.py
This will open the wx GUI. I haven't been able to close or resize KiCAD windows since installing this due to wxwidgets conflict. Didn't realize until now but thankfully others have had the issue. Going to try the patch mentioned here.
Hi Jeff,
I spent over an hour trying to get this to run on OSX. I assume that the wxWidgets version will be easier to use, but if thats not ready a quick howto on getting it up and running on OSX would be great.
I had no problems on ubuntu.
J