Re: [Kicad-developers] I know it's a trivial thing...
On Fri, Oct 07, 2016 at 08:51:34AM +0200, Marco Ciampa wrote: > I know it's a trivial / unimportant particular but it puzzles me ... > > Why in Edit->Search dialog, Sorry, Edit->Find of course... TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ 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] I know it's a trivial thing...
I know it's a trivial / unimportant particular but it puzzles me ... Why in Edit->Search dialog, pressing the "alt" key "Search all component fields" (and all its translations) has no shortcut key highlighted? TIA -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ 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] Spice simulation on windows.
I have some additional information that may prove useful:
1) Using relative paths in the spinit file does not work on windows.
2) Placing a spinit file in the path where the ngspice and libngspice
binaries reside works with no need to set any environment variables.
Option 2 could be used by the installer. The installer itself would
have to create the spinit file by substituting the install path for the
path of the .cm files. I'm not sure if this would work on osx. Maybe
one of our osx devs could test this. If it does, than that would
resolve the simulation init issues.
I've attached a simple circuit that demonstrates the issue. When the
.cm files are not located, the simulation will run with the following
warnings and cause the output of the op-amp to be an impossibly high 260V:
Error on line 0 :
a$poly$e.xu1.eos %vd [ xu1.53 xu1.98 ] %vd ( xu1.3 net-_u1-pad1_ )
a$poly$e.xu1.eos
MIF-ERROR - unable to find definition of model a$poly$e.xu1.eos
Warning: Model issue on line 0 :
.model a$poly$e.xu1.eos spice2poly coef = [ 1.7e-3 1 ] ...
Unknown model type spice2poly - ignored
Error on line 0 :
a$poly$e.xu1.eref1 %vd [ vdd 0 0 0 ] %vd ( xu1.98 0 ) a$poly$e.xu1.eref1
MIF-ERROR - unable to find definition of model a$poly$e.xu1.eref1
Warning: Model issue on line 0 :
.model a$poly$e.xu1.eref1 spice2poly coef = [ 0 0.5 0.5 ] ...
Unknown model type spice2poly - ignored
Error on line 0 :
a$poly$e.xu1.eref2 %vd [ net-_u1-pad1_ 0 /out 0 ] %vd ( xu1.97 0 )
a$poly$e.xu1.eref2
MIF-ERROR - unable to find definition of model a$poly$e.xu1.eref2
Warning: Model issue on line 0 :
.model a$poly$e.xu1.eref2 spice2poly coef = [ 0 0.5 0.5 ] ...
Unknown model type spice2poly - ignored
Error on line 0 :
a$poly$e.xu1.eo3 %vd [ xu1.98 xu1.30 ] %vd ( vdd xu1.42 ) a$poly$e.xu1.eo3
MIF-ERROR - unable to find definition of model a$poly$e.xu1.eo3
Warning: Model issue on line 0 :
.model a$poly$e.xu1.eo3 spice2poly coef = [ 0.7175 0.5 ] ...
Unknown model type spice2poly - ignored
Error on line 0 :
a$poly$e.xu1.eo4 %vd [ xu1.30 xu1.98 ] %vd ( xu1.44 0 ) a$poly$e.xu1.eo4
MIF-ERROR - unable to find definition of model a$poly$e.xu1.eo4
Warning: Model issue on line 0 :
.model a$poly$e.xu1.eo4 spice2poly coef = [ 0.7355 0.5 ] ...
Unknown model type spice2poly - ignored
Reducing trtol to 1 for xspice 'A' devices
Doing analysis at TEMP = 27.00 and TNOM = 27.00
Warning: vv3: no DC value, transient time 0 value used
Let me know if you have any other questions or comments.
Cheers,
Wayne
On 10/6/2016 10:56 AM, Nick Østergaard wrote:
> Hi Maciej
>
> In the latest nightlies they are now stored in lib/ngspice/
>
> I guess that should equate to a relative path to the executables to
> ../lib/ngspice/*.cm, given that the exe's are in the bin folder on the
> same level as lib.
>
> So feel free to submit your fix. Also, are there any demos that make
> use of those cm libs such that it can be tested?
>
> Nick
>
> 2016-10-05 23:16 GMT+02:00 Maciej Sumiński :
>> Hi Nick,
>>
>> Are the .cm files included in the Windows nightlies installer? If so,
>> could you tell me what is the relative path to the directory storing
>> them? The easiest way to fix the problem is to send a few commands to
>> ngspice before a simulation starts.
>>
>> Regards,
>> Orson
>>
>> On 10/05/2016 10:23 PM, Nick Østergaard wrote:
>>> Is this really needed? What exactly does the .cm files provide?
>>>
>>> When I run the latest nightly I can run the allen key demo without
>>> problems as far as I can see. Maybe some other simulation modes do
>>> not work properly?
>>>
>>> 2016-09-30 14:37 GMT+02:00 Wayne Stambaugh :
That would work as a long term solution as well. I was trying to at
least prove that it can be done without make changes to the current
code. Until a full solution is implemented, users (me) will have an
interim solution if they want to use the spice simulator.
Cheers,
Wayne
On 9/30/2016 3:40 AM, Maciej Sumiński wrote:
> We have also discussed on IRC another possibility, which is loading the
> extensions manually instead of having ngspice process its initialization
> file (spinit). This way we can adjust the paths during runtime.
>
> Regards,
> Orson
>
> On 09/29/2016 08:51 PM, Wayne Stambaugh wrote:
>> After much cursing and many config attempts, I finally have a working
>> spice simulation solution on windows. I'm guessing similar parallels
>> can be applied to osx as well.
>>
>>
>> Option A: running from a mingw32 or mingw64 terminal.
>>
>> 1) copy the installed spinit file (by default will be in
>> ${MINGW-PACKAGE-PREFIX}/share/ngspice/scripts) to ~/.spiceinit.
>> 2) change the msys2 paths (/mingw##) in ~/.spiceinit to absolute windows
>> paths with / not \ (in my case C:/msys64/mingw##).
>> 3) Launch kicad.exe from the terminal.
>>
>> I realize this is not very elegant and will only work with either the 64
>>
Re: [Kicad-developers] Spice simulation on windows.
Hi Maciej
In the latest nightlies they are now stored in lib/ngspice/
I guess that should equate to a relative path to the executables to
../lib/ngspice/*.cm, given that the exe's are in the bin folder on the
same level as lib.
So feel free to submit your fix. Also, are there any demos that make
use of those cm libs such that it can be tested?
Nick
2016-10-05 23:16 GMT+02:00 Maciej Sumiński :
> Hi Nick,
>
> Are the .cm files included in the Windows nightlies installer? If so,
> could you tell me what is the relative path to the directory storing
> them? The easiest way to fix the problem is to send a few commands to
> ngspice before a simulation starts.
>
> Regards,
> Orson
>
> On 10/05/2016 10:23 PM, Nick Østergaard wrote:
>> Is this really needed? What exactly does the .cm files provide?
>>
>> When I run the latest nightly I can run the allen key demo without
>> problems as far as I can see. Maybe some other simulation modes do
>> not work properly?
>>
>> 2016-09-30 14:37 GMT+02:00 Wayne Stambaugh :
>>> That would work as a long term solution as well. I was trying to at
>>> least prove that it can be done without make changes to the current
>>> code. Until a full solution is implemented, users (me) will have an
>>> interim solution if they want to use the spice simulator.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 9/30/2016 3:40 AM, Maciej Sumiński wrote:
We have also discussed on IRC another possibility, which is loading the
extensions manually instead of having ngspice process its initialization
file (spinit). This way we can adjust the paths during runtime.
Regards,
Orson
On 09/29/2016 08:51 PM, Wayne Stambaugh wrote:
> After much cursing and many config attempts, I finally have a working
> spice simulation solution on windows. I'm guessing similar parallels
> can be applied to osx as well.
>
>
> Option A: running from a mingw32 or mingw64 terminal.
>
> 1) copy the installed spinit file (by default will be in
> ${MINGW-PACKAGE-PREFIX}/share/ngspice/scripts) to ~/.spiceinit.
> 2) change the msys2 paths (/mingw##) in ~/.spiceinit to absolute windows
> paths with / not \ (in my case C:/msys64/mingw##).
> 3) Launch kicad.exe from the terminal.
>
> I realize this is not very elegant and will only work with either the 64
> or 32 bit mingw (not both without editing .spiceinit) but it works and
> is handy for mingw users.
>
>
> Option B: configuring windows and run kicad from a shortcut.
>
> 1) locate the installed spinit file
> ($INSTALL_PATH/share/ngspice/scripts) and change the msys2 paths
> (/mingw##) to absolute windows paths with / not \ (in my case
> C:/msys64/mingw##).
> 2) Run kicad, open the config paths dialog, and add an environment
> variable SPICE_LIB_DIR with path to the spinit file minus the last
> "scripts" path ($INSTALL_PATH/share/ngspice).
>
> I also tried copying the .spiceinit file from option A to %USERPROFILE%
> but that did not work when launching kicad from a shortcut.
>
> Option B a cleaner solution but still requires some configuration by the
> user. This is going to be an interesting problem to solve for our
> package devs. We need to figure out a way to generate or modify the
> spinit file base on where it gets installed by the installer on
> platforms where this is relevant. We will also either have to set an
> the SPICE_LIB_DIR environment variable or teach ngspice how to find the
> correct spinit file at run time.
>
> At least now windows users have a way to have the same functional spice
> simulation as linux users.
>
> Cheers,
>
> Wayne
>
> ___
> 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
>
___
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 promotion in help menu
On Thu, Oct 06, 2016 at 06:34:34PM +1100, Cirilo Bernardo wrote: > I think the main reason the patch is that size is that I had to touch > quite a few files to add the help item to the many different Help menus > (eeschema, schematic symbol editor, footprint editor, pcbnew, etc). I think > the About dialog is so full of information now that people will miss the > link if we put it there. Adding the actual menu item in each different > Help menu and the wxWidgets code to run the browser are actually > only a very few lines. I suggested adding an item to the About dialog at > one stage but many of our current contributors told me that they thought > it wasn't the best thing to do. Sorry for being so "naive", you see I am not a dev... but I am wondering if it could spare some code using an unique "about" or help dialog and dialog code across all KiCad apps... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ 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] -Wsuggest-override with scripting enabled
On 10/6/2016 8:42 AM, jp charras wrote: > Le 06/10/2016 à 14:30, Wayne Stambaugh a écrit : >> On 10/6/2016 2:58 AM, John Beard wrote: >>> On Thu, Oct 6, 2016 at 7:10 AM, jp charras wrote: It works for me, but I had to modify the patch the change in pcbnew/CMakeLists.txt is if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) set_source_files_properties(pcbnew_wrap.cxx pcbnewPYTHON_wrap.cxx PROPERTIES COMPILE_FLAGS -Wno-suggest-override ) instead of if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) set_source_files_properties(pcbnew_wrap.cxx PROPERTIES COMPILE_FLAGS -Wno-suggest-override ) >> >> @JP, I will go ahead and commit John's patch as is. If you want me to, >> I can add your changes as a separate commit or you can commit the >> changes. Please let me know. > > If my changes are also working for you, add them. > Thanks. That fixed it so I committed the change. Thanks. > >> >>> >>> That's seems strange that adding the file to that list would just >>> work. Since CMake doesn't know about that file (it's not declared as >>> an output or a compiled file anywhere), how does it ever get compiled >>> in the first place, let alone get special flags applied to it? Are you >>> sure the file is being rebuilt the second time? >> >> I was wondering about that myself. I grepped pcbnew/CMakeLists.txt and >> there is no pcbnewPYTHON_wrap.cxx so I'm not sure where this is getting >> pulled in unless it's something swig is generating. > > I did not found it in CMakeLists.txt. > However it is in a .make autogenerated file. > > Unfortunately I have a very limited knowledge of cmake an swig, and I don't > know exactly what tool > has generated the commands (in build.make) to build/compile > pcbnewPYTHON_wrap.cxx. > > >> >>> >>> I may have missed the warnings from the pcbnewPYTHON file, as they did >>> overrun my terminal scrollback, but on cleaning and rebuilding, I >>> don't actually see that file being created or compiled at all. I do >>> see pcbnew_wrap.cpp being created and compiled as expected. When do >>> others see that file appear in the build tree (I assume at the same >>> time as pcbnew_wrap.cxx?) and when does pcbnewPYTHON_wrap.cxx appear >>> in the compilation output (approximately, exact result depend on >>> CMake's multithreading)? >>> >>> GCC 6.2.1 is the compiler, CMake 3.6.2, SWIG 3.0.10, on Arch Linux. > > ___ 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] -Wsuggest-override with scripting enabled
Patches committed. Thanks. On 10/5/2016 10:05 AM, John Beard wrote: > Hi, > > Rather than blanket-disabling -Wsuggest-override when scripting is > enabled, it's possible to turn the warnings off for just the > problematic pcbnew_wrap.cxx file using set_source_file_properties(). > > This means when building with scripting (which I always do), the > warnings are still enabled for all other files. > > Second patch is an override opportunity which was previously silenced > by the blanket disabling of the warning. > > Thanks, > > John > > > > ___ > 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 promotion in help menu
On 10/6/2016 3:23 AM, Chris Pavlina wrote: > On Thu, Oct 06, 2016 at 08:51:54AM +0200, jp charras wrote: >> Le 06/10/2016 à 08:13, Cirilo Bernardo a écrit : >>> Hi folks, >>> >>> Any comments on this patch I proposed a few weeks ago? >>> >>> https://lists.launchpad.net/kicad-developers/msg26412.html >>> >>> The patch adds a menu item in the main menu Help list to launch the >>> system's default browser and bring up the "Contribute to KiCad" page >>> (http://kicad-pcb.org/contribute/). The idea is to promote awareness >>> of how users can get involved, whether it's helping with documentation, >>> libraries, etc. I think we have a great little group at the moment, but >>> more experts helping out or new users learning about the internals of >>> the software is always better. :) >>> >>> >>> - Cirilo >> @Cirilo, I didn't forget about it I've just been really busy. I will try to get to it this weekend. >> To be honest, if I like the idea, I am not thrilled by this (large?) patch. >> A link in our About Kicad dialog (Information panel) could be better (only 2 >> lines of code to add). >> On this Information panel (the default panel when opening the dialog) there >> are already the most >> important links. > > As we discussed with Wayne on IRC a while ago, nobody will ever see it > there. AFAIR I suggested adding this link to the about dialog as well but I don't really have a strong opinion one way or the other. Cirilo is correct that it could get lost along with all of the other information in the about dialog. > >> >> >> -- >> Jean-Pierre CHARRAS >> >> ___ >> 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 > ___ 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] -Wsuggest-override with scripting enabled
Le 06/10/2016 à 14:30, Wayne Stambaugh a écrit : > On 10/6/2016 2:58 AM, John Beard wrote: >> On Thu, Oct 6, 2016 at 7:10 AM, jp charras wrote: >>> >>> It works for me, but I had to modify the patch >>> the change in pcbnew/CMakeLists.txt is >>> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >>> set_source_files_properties(pcbnew_wrap.cxx pcbnewPYTHON_wrap.cxx >>> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >>> ) >>> >>> instead of >>> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >>> set_source_files_properties(pcbnew_wrap.cxx >>> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >>> ) > > @JP, I will go ahead and commit John's patch as is. If you want me to, > I can add your changes as a separate commit or you can commit the > changes. Please let me know. If my changes are also working for you, add them. Thanks. > >> >> That's seems strange that adding the file to that list would just >> work. Since CMake doesn't know about that file (it's not declared as >> an output or a compiled file anywhere), how does it ever get compiled >> in the first place, let alone get special flags applied to it? Are you >> sure the file is being rebuilt the second time? > > I was wondering about that myself. I grepped pcbnew/CMakeLists.txt and > there is no pcbnewPYTHON_wrap.cxx so I'm not sure where this is getting > pulled in unless it's something swig is generating. I did not found it in CMakeLists.txt. However it is in a .make autogenerated file. Unfortunately I have a very limited knowledge of cmake an swig, and I don't know exactly what tool has generated the commands (in build.make) to build/compile pcbnewPYTHON_wrap.cxx. > >> >> I may have missed the warnings from the pcbnewPYTHON file, as they did >> overrun my terminal scrollback, but on cleaning and rebuilding, I >> don't actually see that file being created or compiled at all. I do >> see pcbnew_wrap.cpp being created and compiled as expected. When do >> others see that file appear in the build tree (I assume at the same >> time as pcbnew_wrap.cxx?) and when does pcbnewPYTHON_wrap.cxx appear >> in the compilation output (approximately, exact result depend on >> CMake's multithreading)? >> >> GCC 6.2.1 is the compiler, CMake 3.6.2, SWIG 3.0.10, on Arch Linux. -- Jean-Pierre CHARRAS ___ 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] -Wsuggest-override with scripting enabled
On 10/6/2016 2:58 AM, John Beard wrote: > On Thu, Oct 6, 2016 at 7:10 AM, jp charras wrote: >> >> It works for me, but I had to modify the patch >> the change in pcbnew/CMakeLists.txt is >> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >> set_source_files_properties(pcbnew_wrap.cxx pcbnewPYTHON_wrap.cxx >> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >> ) >> >> instead of >> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >> set_source_files_properties(pcbnew_wrap.cxx >> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >> ) @JP, I will go ahead and commit John's patch as is. If you want me to, I can add your changes as a separate commit or you can commit the changes. Please let me know. > > That's seems strange that adding the file to that list would just > work. Since CMake doesn't know about that file (it's not declared as > an output or a compiled file anywhere), how does it ever get compiled > in the first place, let alone get special flags applied to it? Are you > sure the file is being rebuilt the second time? I was wondering about that myself. I grepped pcbnew/CMakeLists.txt and there is no pcbnewPYTHON_wrap.cxx so I'm not sure where this is getting pulled in unless it's something swig is generating. > > I may have missed the warnings from the pcbnewPYTHON file, as they did > overrun my terminal scrollback, but on cleaning and rebuilding, I > don't actually see that file being created or compiled at all. I do > see pcbnew_wrap.cpp being created and compiled as expected. When do > others see that file appear in the build tree (I assume at the same > time as pcbnew_wrap.cxx?) and when does pcbnewPYTHON_wrap.cxx appear > in the compilation output (approximately, exact result depend on > CMake's multithreading)? > > GCC 6.2.1 is the compiler, CMake 3.6.2, SWIG 3.0.10, on Arch Linux. > > ___ > 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] PATCH: To facilitate easier Via Curtain/Filling
Sorry for Gravedigging. Maybe some heretic (and mostlikely stupid) questions but: why is there even an automatic relabeling implement? Would not it be much more convenient to have it as seperate tool instead of a mandatory step (like the cleaning up)? Further more it seems like /RecalculateAllTracksNetcode /recognize the legacy version of zones (SEGZONE) correctly as SEGZONE is a TRACK while the newer ZONE_CONTAINER is "only" a BOARD_CONNECTED_ITEM . If one stick to the automatic relabeling: Would not it be a bit more logical to consider all BOARD_CONNECTED_ITEM instead of only TRACKS? ___ 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] -Wsuggest-override with scripting enabled
Le 06/10/2016 à 08:58, John Beard a écrit : > On Thu, Oct 6, 2016 at 7:10 AM, jp charras wrote: >> >> It works for me, but I had to modify the patch >> the change in pcbnew/CMakeLists.txt is >> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >> set_source_files_properties(pcbnew_wrap.cxx pcbnewPYTHON_wrap.cxx >> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >> ) >> >> instead of >> if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE ) >> set_source_files_properties(pcbnew_wrap.cxx >> PROPERTIES COMPILE_FLAGS -Wno-suggest-override >> ) > > That's seems strange that adding the file to that list would just > work. Since CMake doesn't know about that file (it's not declared as > an output or a compiled file anywhere), how does it ever get compiled > in the first place, let alone get special flags applied to it? Are you > sure the file is being rebuilt the second time? I am sure *both* pcbnew_wrap.cxx and pcbnewPYTHON_wrap.cxx were recompiled and must be in set_source_files_properties list to avoid warnings. In my install (W7, 32 bits, msys2), the file: /Build/Release/pcbnew/CMakeFiles/_pcbnew.dir/build.make (Generated by "MSYS Makefiles" Generator, CMake Version 3.4) contains the commands to compile pcbnewPYTHON_wrap.cxx > > I may have missed the warnings from the pcbnewPYTHON file, as they did > overrun my terminal scrollback, but on cleaning and rebuilding, I > don't actually see that file being created or compiled at all. I do > see pcbnew_wrap.cpp being created and compiled as expected. When do > others see that file appear in the build tree (I assume at the same > time as pcbnew_wrap.cxx?) and when does pcbnewPYTHON_wrap.cxx appear > in the compilation output (approximately, exact result depend on > CMake's multithreading)? > > GCC 6.2.1 is the compiler, CMake 3.6.2, SWIG 3.0.10, on Arch Linux. -- Jean-Pierre CHARRAS ___ 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 promotion in help menu
On Thu, Oct 6, 2016 at 5:51 PM, jp charras wrote: > Le 06/10/2016 à 08:13, Cirilo Bernardo a écrit : >> Hi folks, >> >> Any comments on this patch I proposed a few weeks ago? >> >> https://lists.launchpad.net/kicad-developers/msg26412.html >> >> The patch adds a menu item in the main menu Help list to launch the >> system's default browser and bring up the "Contribute to KiCad" page >> (http://kicad-pcb.org/contribute/). The idea is to promote awareness >> of how users can get involved, whether it's helping with documentation, >> libraries, etc. I think we have a great little group at the moment, but >> more experts helping out or new users learning about the internals of >> the software is always better. :) >> >> >> - Cirilo > > To be honest, if I like the idea, I am not thrilled by this (large?) patch. > A link in our About Kicad dialog (Information panel) could be better (only 2 > lines of code to add). > On this Information panel (the default panel when opening the dialog) there > are already the most > important links. > > > -- > Jean-Pierre CHARRAS > I think the main reason the patch is that size is that I had to touch quite a few files to add the help item to the many different Help menus (eeschema, schematic symbol editor, footprint editor, pcbnew, etc). I think the About dialog is so full of information now that people will miss the link if we put it there. Adding the actual menu item in each different Help menu and the wxWidgets code to run the browser are actually only a very few lines. I suggested adding an item to the About dialog at one stage but many of our current contributors told me that they thought it wasn't the best thing to do. - Cirilo > ___ > 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 promotion in help menu
On Thu, Oct 06, 2016 at 08:51:54AM +0200, jp charras wrote: > Le 06/10/2016 à 08:13, Cirilo Bernardo a écrit : > > Hi folks, > > > > Any comments on this patch I proposed a few weeks ago? > > > > https://lists.launchpad.net/kicad-developers/msg26412.html > > > > The patch adds a menu item in the main menu Help list to launch the > > system's default browser and bring up the "Contribute to KiCad" page > > (http://kicad-pcb.org/contribute/). The idea is to promote awareness > > of how users can get involved, whether it's helping with documentation, > > libraries, etc. I think we have a great little group at the moment, but > > more experts helping out or new users learning about the internals of > > the software is always better. :) > > > > > > - Cirilo > > To be honest, if I like the idea, I am not thrilled by this (large?) patch. > A link in our About Kicad dialog (Information panel) could be better (only 2 > lines of code to add). > On this Information panel (the default panel when opening the dialog) there > are already the most > important links. As we discussed with Wayne on IRC a while ago, nobody will ever see it there. > > > -- > Jean-Pierre CHARRAS > > ___ > 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
