[Kicad-developers] KiCad git-based libraries as a way to harvest users' contributions - does it work?
Hello guys, I have been mildly interested in the move of the kicad components library to a github repo. Mainly interested in adding a section in the kicad getting started tutorial I decided to learn how it works. A little bit from Carl and a little more from here and there, I learn that an average kicad user can/could/should contribute to the quality of the kicad comp lib via its new github thing by submitting patches, so the librarians group is born, etc. Try to put myself on the kicad seat, I have some hard time understand how git can be appealing to them. So I decided to ask this question to you guys. Your opinion would be great. Here it goes. When you get a repo because you want to contribute (either is kicad it self or the kicad lib repo) u clone the master repo, you do your modifications, you create and send to developers your patch, Done. Few days after your patch gets applied and ideally your would like to re-synch your current repo with the newest repo but it is not possible because your current repo is out of synch since you did your modifications locally. One solution to that is create a branch, do the modification (create and send the patch), go back to the original branch and resynch the current repo, done. Well all this procedure seems to me quite complicated especially when to contribute is some kicad users who is trying to update a lib component but when really his interest is in making PCBs. Also, git was born for code, so the average kicad user will have to do the editing of the lib component part using the kicad component editor, import, export, etc. Do you actually agree that, in almost any open-source project, it is already nearly impossible to get a contribution from somebody who is not a coding guy. Let alone expect a contribution from a pcb developer who already has to learn all the kicad moves, deal with his boss, buy the components, do the soldering, oscilloscope, tester, the board works but some soldering is needed, etc. etc. Once again, in my opinion, git is made for developers not for (pcb designers) who we are trying to take advantage of for improving kicad lib quality. Don't get me wrong I love git as I love vegemite but still are we sure this will bring lib contributions from PCBs developers? Maybe, some sort of intermediate tool that sits between the pcb guy and git is needed? Thank you for your time Best regards Fabrizio ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] KiCad git-based libraries as a way to harvest users' contributions - does it work?
Hello, I've recently learn the process to get the libraries modify them and request a merge using git and I have to agree with you. I'm not a coding guy but I know how to code and I've already work with SubVersion which helps me. Anyway, I agree that an average electronics guy won't know and won't want to do such a process just to update the community library. Instead they will probably maintain their on library locally and forget about git. In fact, last night I was listening to The Amp Hour (Electronics related podcast) and in their last podcast they were talking about that one of the things that they think is a problem in KiCad is not having already built stable versions of KiCad for each OS and the fact that an electronics guy normally won't want to build it themselves. In my humble opinion, following the guides for building KiCad in Linux is not much harder than updating a component for the git libraries, so I agree that some kind of intermediate tool should be added at least in the future if we want a real contribution from any KiCad user. Regards 2014-03-21 9:10 GMT+01:00 Fabrizio Tappero fabrizio.tapp...@gmail.com: Hello guys, I have been mildly interested in the move of the kicad components library to a github repo. Mainly interested in adding a section in the kicad getting started tutorial I decided to learn how it works. A little bit from Carl and a little more from here and there, I learn that an average kicad user can/could/should contribute to the quality of the kicad comp lib via its new github thing by submitting patches, so the librarians group is born, etc. Try to put myself on the kicad seat, I have some hard time understand how git can be appealing to them. So I decided to ask this question to you guys. Your opinion would be great. Here it goes. When you get a repo because you want to contribute (either is kicad it self or the kicad lib repo) u clone the master repo, you do your modifications, you create and send to developers your patch, Done. Few days after your patch gets applied and ideally your would like to re-synch your current repo with the newest repo but it is not possible because your current repo is out of synch since you did your modifications locally. One solution to that is create a branch, do the modification (create and send the patch), go back to the original branch and resynch the current repo, done. Well all this procedure seems to me quite complicated especially when to contribute is some kicad users who is trying to update a lib component but when really his interest is in making PCBs. Also, git was born for code, so the average kicad user will have to do the editing of the lib component part using the kicad component editor, import, export, etc. Do you actually agree that, in almost any open-source project, it is already nearly impossible to get a contribution from somebody who is not a coding guy. Let alone expect a contribution from a pcb developer who already has to learn all the kicad moves, deal with his boss, buy the components, do the soldering, oscilloscope, tester, the board works but some soldering is needed, etc. etc. Once again, in my opinion, git is made for developers not for (pcb designers) who we are trying to take advantage of for improving kicad lib quality. Don't get me wrong I love git as I love vegemite but still are we sure this will bring lib contributions from PCBs developers? Maybe, some sort of intermediate tool that sits between the pcb guy and git is needed? Thank you for your time Best regards Fabrizio ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp -- アレッカス ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Build failed in Jenkins: kicad-qa #91
See http://ci.kicad-pcb.org/job/kicad-qa/91/changes Changes: [Dick Hollenbeck] Enable GITHUB as default, include typeinfo into kiway_holder.cpp -- Started by an SCM change Building in workspace http://ci.kicad-pcb.org/job/kicad-qa/ws/ $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 4762 jp.char...@wanadoo.fr-20140321115004-idvc6cw8f3qz06al stderr: [kicad-qa] $ bzr pull --overwrite lp:kicad You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. http://bazaar.launchpad.net/~kicad-product-committers/kicad/product is permanently redirected to http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/changes You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. M CMakeLists.txt M common/kiway_holder.cpp All changes applied successfully. Now on revision 4763. [kicad-qa] $ bzr revert $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 4763 d...@softplc.com-20140321122054-owxbcqh5sfgiqkw0 stderr: [kicad-qa] $ bzr log -v -r revid:jp.char...@wanadoo.fr-20140321115004-idvc6cw8f3qz06al..revid:d...@softplc.com-20140321122054-owxbcqh5sfgiqkw0 --long --show-ids Getting local revision... $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 4763 d...@softplc.com-20140321122054-owxbcqh5sfgiqkw0 stderr: RevisionState revno:4763 revid:d...@softplc.com-20140321122054-owxbcqh5sfgiqkw0 [kicad-qa] $ /bin/sh -xe /tmp/hudson1326426466949028795.sh + OPTS=' -DCMAKE_BUILD_TYPE=Release -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON' + '[' -d build ']' + cd build + /usr/bin/cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON -- Check for installed OpenGL -- found -- Found Glew: /usr/lib64/libGLEW.so -- Check for installed GLEW -- found -- Check for installed Cairo -- found -- Check for installed wxWidgets -- found -- Check for installed Python Interpreter -- found -- Python module install path: /usr/lib/python2.6/site-packages -- Bazaar version control system version found. -- Kicad Bazaar build version: (2014-03-21 BZR 4763) -- Configuring done -- Generating done -- Build files have been written to: http://ci.kicad-pcb.org/job/kicad-qa/ws/build + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx.o + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx + make -j4 _pcbnew [ 0%] [ 1%] Built target lib-dependencies Built target boost [ 1%] Generating headers containing GLSL source code [ 3%] [ 3%] Headers are up-to-date Built target avhttp Built target lib_dxf [ 3%] Built target shader_headers [ 52%] Built target bitmaps [ 54%] Built target polygon [ 54%] Built target 3d-viewer [ 54%] Built target github_plugin [ 55%] Built target pcad2kicadpcb [ 57%] Built target gal [ 63%] Built target pcbcommon [ 65%] Built target pnsrouter Scanning dependencies of target common [ 65%] Building CXX object common/CMakeFiles/common.dir/build_version.cpp.o [ 65%] Building CXX object common/CMakeFiles/common.dir/kiway_holder.cpp.o Linking CXX static library libcommon.a [ 77%] Built target common [ 77%] Swig source http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:673: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/class_drawsegment.h:69: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/class_edge_mod.h:58: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:517: Warning 325: Nested class not currently supported (RELEASER ignored) http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:332: Warning 401: Nothing known about base class 'KIGFX::VIEW_ITEM'. Ignored. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/pcb_plot_params.h:40: Warning 401: Nothing known about base class 'PCB_PLOT_PARAMS_LEXER'. Ignored. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:41: Warning 401: Nothing known about base class 'std::map std::string,UTF8 '. Ignored. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:41: Warning 401: Maybe you forgot to instantiate 'std::map std::string,UTF8 ' using %template. Scanning dependencies of target _pcbnew [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/scripting/pcbnewPYTHON_wrap.cxx.o Linking CXX shared module _pcbnew.so [100%] Built target _pcbnew + make qa running qa /bin/sh: line 1: 6854 Segmentation fault
Re: [Kicad-developers] KiCad git-based libraries as a way to harvest users' contributions - does it work?
On 21 March 2014 08:10, Fabrizio Tappero fabrizio.tapp...@gmail.com wrote: When you get a repo because you want to contribute (either is kicad it self or the kicad lib repo) u clone the master repo, you do your modifications, you create and send to developers your patch, Done. Few days after your patch gets applied and ideally your would like to re-synch your current repo with the newest repo but it is not possible because your current repo is out of synch since you did your modifications locally. No, at this point you could switch your fp_lib_table to use the KiCad github repo for that libary or keep it pointing to your local repo as they should be the same. If there are additional changes in the KiCad repo then you can pull those changes. If you have additional changes since you made the patch you can make a new patch. Maybe, some sort of intermediate tool that sits between the pcb guy and git is needed? I think this is a good idea. Libgit2 could help with this. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Build failed in Jenkins: kicad-qa #93
See http://ci.kicad-pcb.org/job/kicad-qa/93/changes Changes: [Dick Hollenbeck] single_top.c logic, improved OpenProjectFiles() documentation. -- [...truncated 11867 lines...] [ 77%] Building CXX object pcbnew/router/CMakeFiles/pnsrouter.dir/pns_router.cpp.o [ 77%] Building CXX object pcbnew/router/CMakeFiles/pnsrouter.dir/pns_optimizer.cpp.o [ 77%] Building CXX object pcbnew/router/CMakeFiles/pnsrouter.dir/pns_itemset.cpp.o [ 77%] Building CXX object pcbnew/router/CMakeFiles/pnsrouter.dir/router_tool.cpp.o [ 77%] Building CXX object pcbnew/router/CMakeFiles/pnsrouter.dir/router_preview_item.cpp.o Linking CXX static library libpnsrouter.a [ 77%] Built target pnsrouter [ 77%] [ 77%] [ 77%] Swig source creating http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/dialogs/dialog_freeroute_exchange_help_html.h Generating pcbnew_wrap.cxx, pcbnew.py from http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/dialogs/dialog_freeroute_exchange_help.html http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:673: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:673: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/class_drawsegment.h:69: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/class_edge_mod.h:58: Warning 362: operator= ignored class_drawsegment.h:69: Warning 362: operator= ignored class_edge_mod.h:58: Warning 362: operator= ignored http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:517: Warning 325: Nested class not currently supported (RELEASER ignored) http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:332: Warning 401: Nothing known about base class 'KIGFX::VIEW_ITEM'. Ignored. io_mgr.h:517: Warning 325: Nested class not currently supported (RELEASER ignored) http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/pcb_plot_params.h:40: Warning 401: Nothing known about base class 'PCB_PLOT_PARAMS_LEXER'. Ignored. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:41: Warning 401: Nothing known about base class 'std::map std::string,UTF8 '. Ignored. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/io_mgr.h:41: Warning 401: Maybe you forgot to instantiate 'std::map std::string,UTF8 ' using %template. http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/../include/base_struct.h:332: Warning 401: Nothing known about base class 'KIGFX::VIEW_ITEM'. Ignored. pcb_plot_params.h:40: Warning 401: Nothing known about base class 'PCB_PLOT_PARAMS_LEXER'. Ignored. io_mgr.h:41: Warning 401: Nothing known about base class 'std::map std::string,UTF8 '. Ignored. io_mgr.h:41: Warning 401: Maybe you forgot to instantiate 'std::map std::string,UTF8 ' using %template. swig_import_helper fixed for http://ci.kicad-pcb.org/job/kicad-qa/ws/build/pcbnew/pcbnew.py Scanning dependencies of target _pcbnew [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/scripting/pcbnewPYTHON_wrap.cxx.o [ 77%] [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/__/scripting/python_scripting.cpp.o Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/__/scripting/wx_python_helpers.cpp.o [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/scripting/pcbnew_scripting_helpers.cpp.o http://ci.kicad-pcb.org/job/kicad-qa/ws/scripting/wx_python_helpers.cpp: In function ‘wxString* newWxStringFromPy(PyObject*)’: http://ci.kicad-pcb.org/job/kicad-qa/ws/scripting/wx_python_helpers.cpp:104: warning: suggest explicit braces to avoid ambiguous ‘else’ http://ci.kicad-pcb.org/job/kicad-qa/ws/scripting/wx_python_helpers.cpp:107: warning: suggest explicit braces to avoid ambiguous ‘else’ [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/scripting/pcbnew_footprint_wizards.cpp.o [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/pcbnew.cpp.o http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/scripting/pcbnew_footprint_wizards.cpp: In member function ‘PyObject* PYTHON_FOOTPRINT_WIZARD::CallMethod(const char*, PyObject*)’: http://ci.kicad-pcb.org/job/kicad-qa/ws/pcbnew/scripting/pcbnew_footprint_wizards.cpp:83: warning: suggest explicit braces to avoid ambiguous ‘else’ [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/rect_placement/rect_placement.cpp.o [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/move_and_route_event_functions.cpp.o [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/auto_place_footprints.cpp.o [ 77%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/autorout.cpp.o [ 78%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/routing_matrix.cpp.o [ 78%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/dist.cpp.o [ 78%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/queue.cpp.o [ 78%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/autorouter/spread_footprints.cpp.o [ 78%] Building CXX object
Re: [Kicad-developers] KiCad git-based libraries as a way to harvest users' contributions - does it work?
Maybe KiCad could be made to pull the new changes automatically (git pull https://github.com/KiCad/kicad-library; or git fetch upstream if it's a fork) on startup? However this would require the libraries to be installed in a user-writeable directory. On Fri, Mar 21, 2014 at 9:59 AM, Kaspar Emanuel kaspar.eman...@gmail.comwrote: On 21 March 2014 08:10, Fabrizio Tappero fabrizio.tapp...@gmail.com wrote: When you get a repo because you want to contribute (either is kicad it self or the kicad lib repo) u clone the master repo, you do your modifications, you create and send to developers your patch, Done. Few days after your patch gets applied and ideally your would like to re-synch your current repo with the newest repo but it is not possible because your current repo is out of synch since you did your modifications locally. No, at this point you could switch your fp_lib_table to use the KiCad github repo for that libary or keep it pointing to your local repo as they should be the same. If there are additional changes in the KiCad repo then you can pull those changes. If you have additional changes since you made the patch you can make a new patch. Maybe, some sort of intermediate tool that sits between the pcb guy and git is needed? I think this is a good idea. Libgit2 could help with this. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] KiCad git-based libraries as a way to harvest users' contributions - does it work?
An other issue is that the current github setup require the hypothetical contributor to have a github account. On Fri, Mar 21, 2014 at 6:36 PM, Carl Poirier carl.poirie...@gmail.com wrote: Maybe KiCad could be made to pull the new changes automatically (git pull https://github.com/KiCad/kicad-library; or git fetch upstream if it's a fork) on startup? However this would require the libraries to be installed in a user-writeable directory. On Fri, Mar 21, 2014 at 9:59 AM, Kaspar Emanuel kaspar.eman...@gmail.com wrote: On 21 March 2014 08:10, Fabrizio Tappero fabrizio.tapp...@gmail.com wrote: When you get a repo because you want to contribute (either is kicad it self or the kicad lib repo) u clone the master repo, you do your modifications, you create and send to developers your patch, Done. Few days after your patch gets applied and ideally your would like to re-synch your current repo with the newest repo but it is not possible because your current repo is out of synch since you did your modifications locally. No, at this point you could switch your fp_lib_table to use the KiCad github repo for that libary or keep it pointing to your local repo as they should be the same. If there are additional changes in the KiCad repo then you can pull those changes. If you have additional changes since you made the patch you can make a new patch. Maybe, some sort of intermediate tool that sits between the pcb guy and git is needed? I think this is a good idea. Libgit2 could help with this. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] OSX build fails consistently with same error
Hello all, Since today, I cannot succeed to build OSX version of Kicad (BZR 4764). I can build all the modules (kicad, eeschema, common, cvpcb, pcb_calculator) except “pcbnew”. Before, I was able to address the issue with a “make” followed by a “make common”, and finally another “make”. But now, I cannot find a way that solve the issue. I do not know which part is supposed to create the missing header file. Please help. Jean-Paul (AC9GH) Jean-Pauls-MacBook-Pro:kicad-build jean-paullouis$ make pcbnew [ 1%] Built target boost [ 2%] Built target pixman [ 4%] Built target libwxpython [ 5%] Built target libpng [ 5%] Built target pkgconfig [ 7%] Built target cairo [ 7%] Built target pcre [ 7%] Built target swig [ 7%] Built target lib-dependencies [ 7%] Built target polygon [ 7%] Building CXX object pcbnew/pcad2kicadpcb_plugin/CMakeFiles/pcad2kicadpcb.dir/pcad_plugin.cpp.o In file included from /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/pcad2kicadpcb_plugin/pcad_plugin.cpp:38: In file included from /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/pcad2kicadpcb_plugin/./pcb.h:36: In file included from /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/pcad2kicadpcb_plugin/./pcb_module.h:36: In file included from /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/pcad2kicadpcb_plugin/./pcb_component.h:38: In file included from /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/./class_board.h:44: /Users/jean-paullouis/Soft_Dev/kicad-build/pcbnew/./pcb_plot_params.h:27:10: fatal error: 'pcb_plot_params_lexer.h' file not found #include pcb_plot_params_lexer.h ^ 1 error generated. make[3]: *** [pcbnew/pcad2kicadpcb_plugin/CMakeFiles/pcad2kicadpcb.dir/pcad_plugin.cpp.o] Error 1 make[2]: *** [pcbnew/pcad2kicadpcb_plugin/CMakeFiles/pcad2kicadpcb.dir/all] Error 2 make[1]: *** [pcbnew/CMakeFiles/pcbnew.dir/rule] Error 2 make: *** [pcbnew] Error 2 Jean-Pauls-MacBook-Pro:kicad-build jean-paullouis$ signature.asc Description: Message signed with OpenPGP using GPGMail ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] OSX build fails consistently with same error
I tried to send an email to Jean Paul earlier today about this, but four hours later a kindly email server told me I sent from the wrong address. This is a bug that is already in the bug tracker. Do exactly what Dick says--cd common, make, cd back, make again. I know Marco was looking into it, but I'm not sure if it's gotten anywhere yet. I've been watching the Mac builds like a hawk lately--it's interesting that you haven't been bit by this one yet. Adam Wolf Wayne and Layne LLC On Mar 21, 2014 5:12 PM, Dick Hollenbeck d...@softplc.com wrote: On 03/21/2014 04:06 PM, Jean-Paul Louis wrote: Hello all, Since today, I cannot succeed to build OSX version of Kicad (BZR 4764). I can build all the modules (kicad, eeschema, common, cvpcb, pcb_calculator) except pcbnew. Before, I was able to address the issue with a make followed by a make common, and finally another make. But now, I cannot find a way that solve the issue. I do not know which part is supposed to create the missing header file. Please help. Jean-Paul (AC9GH) pcb_plot_params.h is generated by CMake, driven from make, on line 340 of pcbnew/CMakeList.txt. It is placed into src/pcbnew/pcb_plot_params.h as it is generated. 1) First verify it is missing by looking for it in src/common/ dir. 2) If missing, then $ cd build/common i.e. go into one directory below your build directory into one named common. 3) make help | grep pcb_plot_params_keywords.o common$ make help | grep pcb_plot_params_keywords.o ... pcb_plot_params_keywords.o If you don't see this, punt, go back to step 2. 4) force the damn file to be built, while still in that dir: $ make pcb_plot_params_keywords.o 5) verify it was built and placed into src/pcbnew/pcb_plot_params.h If not, send me your computer and $2,000. :) Dick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] OSX build fails consistently with same error
Thanks for the help guys. It progressed a bit further. But it died building cvpcb. I will send the error message on my new trial Jean-Paul On Mar 21, 2014, at 7:40 PM, Adam Wolf adamw...@feelslikeburning.com wrote: I tried to send an email to Jean Paul earlier today about this, but four hours later a kindly email server told me I sent from the wrong address. This is a bug that is already in the bug tracker. Do exactly what Dick says--cd common, make, cd back, make again. I know Marco was looking into it, but I'm not sure if it's gotten anywhere yet. I've been watching the Mac builds like a hawk lately--it's interesting that you haven't been bit by this one yet. Adam Wolf Wayne and Layne LLC On Mar 21, 2014 5:12 PM, Dick Hollenbeck d...@softplc.com wrote: On 03/21/2014 04:06 PM, Jean-Paul Louis wrote: Hello all, Since today, I cannot succeed to build OSX version of Kicad (BZR 4764). I can build all the modules (kicad, eeschema, common, cvpcb, pcb_calculator) except “pcbnew”. Before, I was able to address the issue with a “make” followed by a “make common”, and finally another “make”. But now, I cannot find a way that solve the issue. I do not know which part is supposed to create the missing header file. Please help. Jean-Paul (AC9GH) pcb_plot_params.h is generated by CMake, driven from make, on line 340 of pcbnew/CMakeList.txt. It is placed into src/pcbnew/pcb_plot_params.h as it is generated. 1) First verify it is missing by looking for it in src/common/ dir. 2) If missing, then $ cd build/common i.e. go into one directory below your build directory into one named common. 3) make help | grep pcb_plot_params_keywords.o common$ make help | grep pcb_plot_params_keywords.o ... pcb_plot_params_keywords.o If you don't see this, punt, go back to step 2. 4) force the damn file to be built, while still in that dir: $ make pcb_plot_params_keywords.o 5) verify it was built and placed into src/pcbnew/pcb_plot_params.h If not, send me your computer and $2,000. :) Dick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp signature.asc Description: Message signed with OpenPGP using GPGMail ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
