Re: [Kicad-developers] GSOC 2022 | LTSpice schematic importer for KiCad

[Roberto Fernández Bautista]

His Chetan,

Welcome to the mailing list!

Before you start, make sure to read through the contributing guidelines, so
that you can make sure your patches conform to the required policies (link:
https://dev-docs.kicad.org/en/contribute/ ), in particular code style and
commit message format policies. We will be asking you to correct any
non-conformances before your code changesets can be accepted.

Also, as I mentioned in the discord chat - it might be a good idea to see
if you can fix a few starter bugs first. In the gitlab bug tracker you will
be able to find some issues tagged "starter" (link:
https://gitlab.com/kicad/code/kicad/-/issues?sort=created_date=opened_name[]=starter
). These are issues that should be suitable for a newcomer to address. You
could pick one or two of them and then submit a patch via a gitlab merge
request.  This will help you familiarise with a small part of the code as
well as understand the general process for submitting changes to the
codebase.

As for your LTspice importer, just a few things of note:

- The KiCad file extensions from version 6.0 onwards are .kicad_pro and
.kicad_sch (.pro and .sch are v5 and earlier), but it doesn't matter
anyway: The importer should follow the architecture of other schematic
importers (e.g. Altium or CADSTAR). This means your importer wouldn't
directly generate a .kicad_sch file. Instead, it should load the input file
into an interim data structure which later gets converted into KiCad
internal objects. There is existing code already for saving KiCad objects
as .kicad_sch and .kicad_pro

- Ideally, the importer should also import the spice models as part of the
process (I'd only expect to import the unencrypted models - encrypted ones
could be troublesome in several ways).

- As Thomas (@pointhi) mentioned in the discord chat it is good to start
simple: "code a minimum KiCad plugin to show everything works on you side.
So no logic, just that a new plugin entry is shown in the import UI and
writes "Hello World" to the console when executed. I guess this should be
around 50 lines of code split a few files, most of it making a child class
of SCH_PLUGIN." Once you have this ready, you can open a "work in progress"
merge request where we can discuss the code and you can ask detailed
specific questions (so as to not bombard the mailing list).


As always - feel free to ask any questions if you get stuck!

Roberto (Qbort)




On Mon, Apr 18, 2022, 20:50 chetan shinde 
wrote:

> Hi all,
>
> I am Chetan Shinde. First of all thanks for adding me to the developer's
> group.
>
> It's great to be officially included in the team. 
>
> I do have coding experience in C+, Java, and Python.
>
> In this year's GSOC,  I am proposing writing KiCad importer for LTSpice.
>
> Just a quick brief, about what I am proposing.
>
> In the KiCad importer for LTSpice, we will be reading the LTspice
> symbols(.asy) and schematics(.asc) files
> and converting them into something that the KiCad can understand i.e
> generating the (.pro) and (.sch) files.
>
> I am really excited about my proposal and looking forward to connecting
> with the team. Regards Chetan
>
> ___
> 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] New lead developer announcement

[Roberto Fernández Bautista]

Thank you all!

I look forwards to continue making KiCad even better!

Roberto

On Tue, 6 Jul 2021, 14:30 Steven A. Falco,  wrote:

> Congrats Roberto!  Glad to have you in a most prominent position!
>
> Steve
>
> On 7/6/21 8:03 AM, Wayne Stambaugh wrote:
> > I am happy to announce that Roberto Fernandez Bautista has accepted an
> invitation to the KiCad lead development team.  Roberto has made some
> significant contributions to the KiCad project and I look forward to his
> contributions as lead developer.  Please join me in congratulating Roberto
> in his new role.
> >
> > 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] Any release candidates fro V6 planned.

[Roberto Fernández Bautista]

Hi David,

You could download the latest nightly version now and start testing
already. Bug reports now will be better than bug reports when rc1 comes out.

For what it's worth, I'm already using KiCad nightly at work for real
projects. There are still some bugs being worked on but it is very usable
as it stands. The more people using KiCad nightly now and reporting bugs,
the more likely it will be stable when rc1 comes out.

Hope that helps.

Roberto


On Sun, 20 Jun 2021, 12:24 David,  wrote:

> Hi,
> I'm hoping to get version 6 of Kicad installed for the students in the
> University where I work. Are there any release candidates planned leading
> up to the final release? I'd like pass on this information to our IT
> department to help convince them that V6 will be stable when it arrives.
> I'm acting as a kind of Beta tester and release candidates would be useful.
> Thanks.
>
> David.
> ___
> 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] MSVC compile: missing s3d_plugin_oce.dll

[Roberto Fernández Bautista]

Just one thing to check: Are you running the "install" target through
visual studio? Note that for each executable you can either install it and
debug or debug standalone
[image: image.png]
[image: image.png]

I've fallen under the mistake before of debugging without installing and
then wondering why I am getting error messages of dlls missing.


On Wed, 2 Dec 2020 at 08:11,  wrote:

> I copied over ALL of the dlls, just in case, and it did not help. If it is
> about dependencies, maybe I missed to install something in vcpkg. I
> installed the recommended libraries as per the web documentation:
>
> boost cairo curl glew gettext glm icu ngspice opencascade opengl openssl
> python3 wxwidgets zlib.
>
> Anything missing?
>
>
>
>
>
> *Von:* Mark Roszko 
> *Gesendet:* 21 November 2020 14:01
> *An:* deve...@worldinone.at
> *Cc:* KiCad Developers 
> *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
>
>
>
> If the kiface file exists in that path, the failure to load is because you
> are missing more dependencies in the install\bin folder that need to be
> copied from vcpkg debug\bin or bin.
>
>
>
>
>
> On Sat, Nov 21, 2020 at 3:00 AM  wrote:
>
> I got it sorted out, partially. After copying the right jpeg62.dll and
> lzmad.dll to the install directory for debug, KiCad started all right.
>
> When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an
> error about failing *.kiface to load.
>
> Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with
> the correct path (in my case
> 
>
> but that returns NULL, as it fails to load the library. Unfortunately,
> RawLoad does not provide any error codes.
>
> Is this the bug you mentioned? But then, the path passed to RawLoad is
> correct, so I do not see what can be wrong here. Other modules like ntdll,
> comctrl32 e.a. are loaded ok.
>
> Only thing I can image is that – out of the blue - there’s a problem with
> the path string. Is it a MSVC specific thing (the nightlies obviously are
> built all right)? Ok, the nightlies are built with wxwidgets 3.0.5
>
> and I'm on wxwidgets 3.1.4. But one week or so ago, everything was ok.
> Trouble started after upgrading vcpkg.
>
> -Martin
>
>
>
> *Von:* Mark Roszko 
> *Gesendet:* 16 November 2020 20:56
> *An:* deve...@worldinone.at
> *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
>
>
>
> Probably a few weeks waitI have it on my queue to revisit vcpkg at
> some point and upstream also takes time to merge fixes.
>
>
>
> It's just easier to copy the DLLs like I noted.
>
>
>
> On Mon, Nov 16, 2020 at 2:45 PM  wrote:
>
> Ok. Can you notify me when it’s fixed? Thanks a lot!
>
> -Martin
>
>
>
> *Von:* Mark Roszko 
> *Gesendet:* Montag, 16. November 2020 20:14
> *An:* deve...@worldinone.at
> *Cc:* KiCad Developers 
> *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
>
>
>
> Ah it's a bug in vcpkg I need to fix upstream.
>
>
>
> For now you'll need to include in your kicad install folder for debug, the
> non-debug versions of freetype, zlib, bz2 and libpng
>
>
>
> On Mon, Nov 16, 2020 at 1:44 PM Mark Roszko  wrote:
>
> Ah I've been meaning to fix that. There's something wrong with the
> compilation settings and/or wxdynamiclibrary loader that's causing it not
> to load DLLs from the application's executable directory, very specifically
> for the OCE plugin.
>
>
>
> On Mon, Nov 16, 2020 at 6:22 AM  wrote:
>
> Compiling the current source (7043) with MSVC and the proposed
> CMakeSettings.json I get a missing s3d_plugin_oce.dll error when starting
> the 3D viewer.
>
> What is wrong here?
>
>
>
> -Martin.
>
> ___
> 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
>
>
>
>
> --
>
> Mark
>
>
>
>
> --
>
> Mark
>
>
>
>
> --
>
> Mark
>
>
>
>
> --
>
> Mark
> ___
> 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] mingw64 build issue.

[Roberto Fernández Bautista]

Yes, sorry I realised the long conversation that happened between me
starting the MSYS build and sending the email reply to you. Definitely MSVC
is much faster compile time (20 mins vs 2 hours on my computer). It only
needs a CMakeSettings.json file in the root folder of the project and it
works like magic - no other configuration is required (other than vcpkg and
installing the required dependencies).

On Fri, 25 Sep 2020 at 22:50, Wayne Stambaugh  wrote:

> They were all clean config and build.
>
> On 9/25/20 5:46 PM, Roberto Fernández Bautista wrote:
> > Hi Wayne
> >
> > I just did a clean build of master in MingW64 / msys2 and did not see
> > the error you report (using gcc 10.1)
> >
> > Maybe there is something strange in your configuration / might just need
> > to do a clean before re-building?
> >
> > Roberto.
> >
> > On Fri, 25 Sep 2020 at 18:11, Wayne Stambaugh  > <mailto:stambau...@gmail.com>> wrote:
> >
> > Is anyone else seeing the following error when building with
> > MinGW64/msys2?
> >
> >
>  ../common/libcommon.a(libcontext.cpp.obj):libcontext.cpp:(.text+0x19e):
> > relocation truncated to fit: R_X86_64_PC32 against `*ABS*'
> >
> > I did some digging around and it looks like it's a bug in the context
> > assembly code but I've never seen the error before.  I tried
> downgrading
> > gcc from 10.2 to 10.1 but no luck.  It also happens when building the
> > 5.1 branch.  It doesn't happen when building with MinGW32/msys2.
> >
> > Thanks,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto: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] mingw64 build issue.

[Roberto Fernández Bautista]

Hi Wayne

I just did a clean build of master in MingW64 / msys2 and did not see the
error you report (using gcc 10.1)

Maybe there is something strange in your configuration / might just need to
do a clean before re-building?

Roberto.

On Fri, 25 Sep 2020 at 18:11, Wayne Stambaugh  wrote:

> Is anyone else seeing the following error when building with MinGW64/msys2?
>
> ../common/libcommon.a(libcontext.cpp.obj):libcontext.cpp:(.text+0x19e):
> relocation truncated to fit: R_X86_64_PC32 against `*ABS*'
>
> I did some digging around and it looks like it's a bug in the context
> assembly code but I've never seen the error before.  I tried downgrading
> gcc from 10.2 to 10.1 but no luck.  It also happens when building the
> 5.1 branch.  It doesn't happen when building with MinGW32/msys2.
>
> Thanks,
>
> 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

Re: [Kicad-developers] Fedevel openRex Module migrated to KiCad

[Roberto Fernández Bautista]

Hi Alexander,

I'd suggest that you post this in the forum instead as you will get a wider
audience of KiCad users: https://forum.kicad.info/

Looks interesting though!

Roberto

On Thu, 10 Sep 2020 at 13:03, Alexander Shuklin  wrote:

> Hi All!
> I hope somebody will find it useful, I migrated openRex imx6 SOM (
> https://www.imx6rex.com/ ) to KiCad. That's an open source ARM SOM module
> from Fedevel courses. You can find it in my gitlab:
> https://gitlab.com/jasuramme/imx6-openrex-kicad-port
>
> The course I just finished is Advanced PCB Layout Course. (
> https://academy.fedevel.com/courses/online-advanced-pcb-layout-course )
> That's a really nice one and I would recommend it.
>
> I hope Robert Feranec, author, will create a course based on KiCad as well
> someday.
> ___
> 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] New Build Dependency

[Roberto Fernández Bautista]

Ah I see! Sorry I thought it was maybe a special "dev" package or something.

Thanks for this!

Roberto

On Mon, 17 Aug 2020 at 20:50, Ian McInerney 
wrote:

> It will be `zlib`.
>
> -Ian
>
> On Mon, Aug 17, 2020 at 8:20 PM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Hi Seth,
>>
>> Thanks for heads up. Any ideas what the new dependency might be called in
>> VCPKG? Or if not available, could you let me know which CMAKE variable
>> should I set to "OFF" in order to compile without the dependency?
>>
>> Thanks
>>
>> Roberto.
>>
>> On Mon, 17 Aug 2020 at 17:44, Seth Hillbrand  wrote:
>>
>>> I should have the MR ready today and I'll send along the branch info.
>>>
>>> Best-
>>> Seth
>>>
>>> On Mon, Aug 17, 2020 at 9:38 AM Adam Wolf 
>>> wrote:
>>>
>>>> I love the heads up! Thanks!
>>>>
>>>> Is there a sample branch I can try before it's merged into master?
>>>>
>>>> Adam
>>>>
>>>> On Mon, Aug 17, 2020 at 10:23 AM Seth Hillbrand 
>>>> wrote:
>>>>
>>>>> Hi Folks (Packagers especially)-
>>>>>
>>>>> We are adding a new build dependency to KiCad in the next few days.
>>>>> zlib1g-dev (on debian) will be required to support stream
>>>>> compression/decompression of model files.
>>>>>
>>>>> Please update your build environment to include this (if it doesn't
>>>>> already).  The critical file for KiCad is "zlib.h" in one of the standard
>>>>> include locations.  Let me know if you have any questions.
>>>>>
>>>>> Best-
>>>>> Seth
>>>>>
>>>>> --
>>>>> [image: KiCad Services Corporation Logo]
>>>>> Seth Hillbrand
>>>>> *Lead Developer*
>>>>> +1-530-302-5483‬ <+12126039372>
>>>>> Davis, CA
>>>>> www.kipro-pcb.comi...@kipro-pcb.com
>>>>>
>>>>
>>>
>>> --
>>> [image: KiCad Services Corporation Logo]
>>> Seth Hillbrand
>>> *Lead Developer*
>>> +1-530-302-5483‬ <+12126039372>
>>> Davis, CA
>>> www.kipro-pcb.comi...@kipro-pcb.com
>>> ___
>>> 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] New Build Dependency

[Roberto Fernández Bautista]

Hi Seth,

Thanks for heads up. Any ideas what the new dependency might be called in
VCPKG? Or if not available, could you let me know which CMAKE variable
should I set to "OFF" in order to compile without the dependency?

Thanks

Roberto.

On Mon, 17 Aug 2020 at 17:44, Seth Hillbrand  wrote:

> I should have the MR ready today and I'll send along the branch info.
>
> Best-
> Seth
>
> On Mon, Aug 17, 2020 at 9:38 AM Adam Wolf 
> wrote:
>
>> I love the heads up! Thanks!
>>
>> Is there a sample branch I can try before it's merged into master?
>>
>> Adam
>>
>> On Mon, Aug 17, 2020 at 10:23 AM Seth Hillbrand 
>> wrote:
>>
>>> Hi Folks (Packagers especially)-
>>>
>>> We are adding a new build dependency to KiCad in the next few days.
>>> zlib1g-dev (on debian) will be required to support stream
>>> compression/decompression of model files.
>>>
>>> Please update your build environment to include this (if it doesn't
>>> already).  The critical file for KiCad is "zlib.h" in one of the standard
>>> include locations.  Let me know if you have any questions.
>>>
>>> Best-
>>> Seth
>>>
>>> --
>>> [image: KiCad Services Corporation Logo]
>>> Seth Hillbrand
>>> *Lead Developer*
>>> +1-530-302-5483‬ <+12126039372>
>>> Davis, CA
>>> www.kipro-pcb.comi...@kipro-pcb.com
>>>
>>
>
> --
> [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> ___
> 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] Build broken?

[Roberto Fernández Bautista]

Dear Jean Pierre,

Thanks for the commit (and subsequent commit from Ian) - this now compiles
fine on MSVC.

Roberto.

On Mon, 10 Aug 2020 at 10:42, jp charras  wrote:

> Le 10/08/2020 à 11:18, Roberto Fernández Bautista a écrit :
> > Hi Jon,
> >
> > Thanks for that commit - it does appear that it fixed one compile issue,
> however it appears there is
> > a second one. Just to make sure it was nothing related to my branch, I
> pulled latest from master
> > (commit 370bc89d) and did a clean build on MSVC, resulting in the
> following compile error:
> >
> > Error C1083 Cannot open include file: 'Python.h': No such file or
> directory
> > C:\src\kicad-sources\master\build\x64-Debug\master
> > C:\src\kicad-sources\master\pcbnew\swig\python_scripting.h 37
> >
> > Thanks
> >
> > Roberto.
>
> I just coàmmitted a fix.
>
>
> --
> 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

Re: [Kicad-developers] Build broken?

[Roberto Fernández Bautista]

Sorry forgot to add: I am compiling using your CMakeSettings.json file,
which has the following CMake variables defined (i.e. *python scripting is
off*)

"variables": [
{
  "name": "KICAD_SPICE",
  "value": "OFF",
  "type": "STRING"
},
{
  "name": "KICAD_USE_OCE",
  "value": "OFF",
  "type": "STRING"
},
{
  "name": "KICAD_SCRIPTING",
  "value": "OFF",
  "type": "STRING"
},
{
  "name": "KICAD_SCRIPTING_WXPYTHON",
  "value": "OFF",
  "type": "STRING"
},
{
  "name": "KICAD_SCRIPTING_MODULES",
  "value": "OFF",
  "type": "STRING"
}
  ],

On Mon, 10 Aug 2020 at 10:18, Roberto Fernández Bautista <
roberto.fer@gmail.com> wrote:

> Hi Jon,
>
> Thanks for that commit - it does appear that it fixed one compile issue,
> however it appears there is a second one. Just to make sure it was nothing
> related to my branch, I pulled latest from master (commit 370bc89d) and did
> a clean build on MSVC, resulting in the following compile error:
>
> Error C1083 Cannot open include file: 'Python.h': No such file or
> directory C:\src\kicad-sources\master\build\x64-Debug\master
> C:\src\kicad-sources\master\pcbnew\swig\python_scripting.h 37
>
> Thanks
>
> Roberto.
>
> On Sun, 9 Aug 2020 at 23:27, Jon Evans  wrote:
>
>> Can you see if it's fixed by abc64f22?
>>
>> On Sun, Aug 9, 2020 at 6:16 PM Roberto Fernández Bautista <
>> roberto.fer@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I just rebased my branch to master and got the following errors
>>> unrelated to the changes in my branch (compiling in MSVC, Windows 10)
>>>
>>> Severity Code Description Project File Line Suppression State
>>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>>> 'wxString' to 'const char *'
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>>> 317
>>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>>> 'wxString' to 'const char *'
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>>> 786
>>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>>> 'wxString' to 'const char *'
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>>> 789
>>> Error C2660 'DIALOG_BOARD_REANNOTATE::BuildChangeArray': function does
>>> not take 4 arguments
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>>> 789
>>>
>>>
>>> Does anyone else also see this?
>>>
>>> Thanks
>>>
>>> Roberto.
>>> ___
>>> 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] Build broken?

[Roberto Fernández Bautista]

Hi Jon,

Thanks for that commit - it does appear that it fixed one compile issue,
however it appears there is a second one. Just to make sure it was nothing
related to my branch, I pulled latest from master (commit 370bc89d) and did
a clean build on MSVC, resulting in the following compile error:

Error C1083 Cannot open include file: 'Python.h': No such file or directory
C:\src\kicad-sources\master\build\x64-Debug\master
C:\src\kicad-sources\master\pcbnew\swig\python_scripting.h 37

Thanks

Roberto.

On Sun, 9 Aug 2020 at 23:27, Jon Evans  wrote:

> Can you see if it's fixed by abc64f22?
>
> On Sun, Aug 9, 2020 at 6:16 PM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Hi all,
>>
>> I just rebased my branch to master and got the following errors unrelated
>> to the changes in my branch (compiling in MSVC, Windows 10)
>>
>> Severity Code Description Project File Line Suppression State
>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>> 'wxString' to 'const char *'
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>> 317
>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>> 'wxString' to 'const char *'
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>> 786
>> Error C2664 'int atoi(const char *)': cannot convert argument 1 from
>> 'wxString' to 'const char *'
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>> 789
>> Error C2660 'DIALOG_BOARD_REANNOTATE::BuildChangeArray': function does
>> not take 4 arguments
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
>> C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
>> 789
>>
>>
>> Does anyone else also see this?
>>
>> Thanks
>>
>> Roberto.
>> ___
>> 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 broken?

[Roberto Fernández Bautista]

Hi all,

I just rebased my branch to master and got the following errors unrelated
to the changes in my branch (compiling in MSVC, Windows 10)

Severity Code Description Project File Line Suppression State
Error C2664 'int atoi(const char *)': cannot convert argument 1 from
'wxString' to 'const char *'
C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
317
Error C2664 'int atoi(const char *)': cannot convert argument 1 from
'wxString' to 'const char *'
C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
786
Error C2664 'int atoi(const char *)': cannot convert argument 1 from
'wxString' to 'const char *'
C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
789
Error C2660 'DIALOG_BOARD_REANNOTATE::BuildChangeArray': function does not
take 4 arguments
C:\src\kicad-sources\cadstar_pcb_archive_importer\build\x64-Debug\cadstar_pcb_archive_importer
C:\src\kicad-sources\cadstar_pcb_archive_importer\pcbnew\dialogs\dialog_board_reannotate.cpp
789


Does anyone else also see this?

Thanks

Roberto.
___
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] ngspice vcpkg port

[Roberto Fernández Bautista]

Excellent news!

Which KiCad dependencies are left to be ported to VCPKG?

It seems we are very close to a complete KiCad build system in Visual
Studio :)

On Thu, 6 Aug 2020, 02:05 Mark Roszko,  wrote:

> ngspice and wxwidgets 3.1.4 have been merged on vcpkg.
>
> On Sun, Aug 2, 2020 at 5:55 PM Wayne Stambaugh 
> wrote:
>
>> +1
>>
>> On 8/2/20 2:08 PM, Seth Hillbrand wrote:
>> > Nice work!  Thanks, Mark
>> >
>> > On Sat, Aug 1, 2020 at 11:26 PM Mark Roszko > > > wrote:
>> >
>> > Hot off the press, a ngspice port for
>> > vcpkg. https://github.com/marekr/vcpkg/tree/kicad/ports/ngspice
>> > I will try and upstream this port package to vcpkg but there's a
>> > good chance they will reject it for being too niche but who knows, I
>> > haven't tried before.
>> >
>> >
>> > But that doesn't stop us from using it. You can simply dump in the
>> > ngspice folder into your vcpkg/ports folder locally and tell it to
>> >
>> > vcpkg install ngspice
>> >
>> > This means you can turn on KICAD_SPICE with msvc.
>> >
>> >
>> > KiCad cmake's itself however needs newer logic to copy over
>> ngspice.dll.
>> >
>> >
>> > image.png
>> >
>> > I'm going to work on wxPython next. SWIG is already done as it has a
>> > precompiled binary and is a compile time tool only.
>> >
>> >
>> > --
>> > Mark
>> > ___
>> > 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 Services Corporation Logo
>> > Seth Hillbrand
>> > *Lead Developer*
>> > +1-530-302-5483‬ 
>> > Davis, CA
>> > www.kipro-pcb.com i...@kipro-pcb.com
>> > 
>> >
>> >
>> > ___
>> > 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
>>
>
>
> --
> Mark
> ___
> 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] New Build Dependencies: Lemon + GTK3

[Roberto Fernández Bautista]

Thanks for that Ian - that sounds great! Definitely a much cleaner
solution. Did you create a separate branch for this change or is it in
master?

Thanks.



On Mon, 3 Aug 2020 at 18:40, Ian McInerney  wrote:

> I have now updated this so that we bundle the lemon parser code inside
> thirdparty and build it for ourselves (it is only 1 main c file that was
> released into the public domain). CMake then takes care of all the pathing
> for the template and executable file for the targets. This should work on
> all platforms now with no extra steps. It also means that there is no need
> to install lemon on dev computers anymore.
>
> -Ian
>
> On Sun, Aug 2, 2020 at 11:46 PM Mark Roszko  wrote:
>
>> LOL, "lemon" in VCPKG is not Lemon the grammar generator, it's Lemon the
>> boost graph library.
>>
>> And lemon grammar itself, isn't a real library. It's a single C file.
>> It's very unlikely to be accepted into vcpkg.
>>
>> We may as well just build it on the fly in kicad
>> https://www.sqlite.org/src/file/tool/lemon.c
>>
>>
>> On Sun, Aug 2, 2020 at 6:37 PM Mark Roszko  wrote:
>>
>>> MSVC support is a work in progress so it's not that its not supported,
>>> it's just someone needs to fix it ;)
>>>
>>> On Sun, Aug 2, 2020 at 6:06 PM Roberto Fernández Bautista <
>>> roberto.fer@gmail.com> wrote:
>>>
>>>> Just tried your branch and unfortunately couldn't get it to compile on
>>>> Visual Studio (even after a "vcpkg install lemon:x64-windows" and "vcpkg
>>>> integrate install")... I got the cmake error "lemon not found"
>>>>
>>>> I know Visual Studio isn't officially supported but any ideas what I
>>>> could do to install lemon correctly so visual studio/ cmake can recognise
>>>> it?
>>>>
>>>> Thanks
>>>>
>>>> Roberto
>>>>
>>>> On Sun, 2 Aug 2020 at 22:06, Ian McInerney 
>>>> wrote:
>>>>
>>>>> Yes, I have a branch on my fork [1] called "im/lemon" that can be
>>>>> used. It can be found here:
>>>>> https://gitlab.com/imcinerney/kicad/-/tree/im/lemon. If the build
>>>>> passes with that, it means lemon integration is working. CMake should 
>>>>> error
>>>>> during configuration if the lemon executable can't be found
>>>>>
>>>>> -Ian
>>>>>
>>>>> [1] https://gitlab.com/imcinerney/kicad
>>>>>
>>>>> On Sun, Aug 2, 2020 at 10:01 PM Adam Wolf <
>>>>> adamw...@feelslikeburning.com> wrote:
>>>>>
>>>>>> Is there a branch packages can use to make sure their lemon
>>>>>> integration is working?
>>>>>>
>>>>>> On Sun, Aug 2, 2020, 4:00 PM Ian McInerney 
>>>>>> wrote:
>>>>>>
>>>>>>> Two new build-time dependencies are being added to the master branch
>>>>>>> for v6:
>>>>>>> * lemon - The lemon parser generator
>>>>>>> * GTK3 (linux only) - the GTK3 libraries (only GTK3, not GTK2 - that
>>>>>>> is not supported anymore). This is technically also a runtime 
>>>>>>> dependency,
>>>>>>> but we also need GTK3 for wxWidgets, so it shouldn't be a new runtime 
>>>>>>> dep
>>>>>>> (only needing the build headers are new).
>>>>>>>
>>>>>>> The lemon parser is needed to fix
>>>>>>> https://gitlab.com/kicad/code/kicad/-/issues/5013 by changing how
>>>>>>> the files are generated (in MR
>>>>>>> https://gitlab.com/kicad/code/kicad/-/merge_requests/318). GTK3 is
>>>>>>> needed to enable new functionality inside the platform-specific
>>>>>>> KIPLATFORM library for Linux (such as overriding menu settings, moving
>>>>>>> files to trash, etc.)
>>>>>>>
>>>>>>> All developers should make sure they have these new dependencies
>>>>>>> installed, and nightly builds should add them to their build script 
>>>>>>> (Steve,
>>>>>>> thanks for updating Fedora's so quick!) I have opened issue on GitLab 
>>>>>>> for
>>>>>>> the builders on there:
>>>>>>> https://gitlab.com/kicad/packaging/kicad-win-builder/-/issues/101
>>>>&

[Kicad-developers] Fwd: New Build Dependencies: Lemon + GTK3

[Roberto Fernández Bautista]

forgot to copy in the mailing list...(see below)

-- Forwarded message -
From: Roberto Fernández Bautista 
Date: Sun, 2 Aug 2020 at 23:38
Subject: Re: [Kicad-developers] New Build Dependencies: Lemon + GTK3
To: 


Ah! No "lemon.exe", but a "lemon.lib". After a bit of digging I found that
the "lemon" package in vcpkg actually installs "lib-lemon", which is
something else (see https://github.com/Microsoft/vcpkg/pull/3779).

However, I managed to get it working by installing lemon in MSYS2/MINGW64
(pacman -S lemon) and then telling cmake the location of lemon.exe by
adding the variable "LEMON=C:\msys64\usr\bin" to the cMakeSettings.json (as
per your suggestion). That seemed to work: I'm not getting the cmake error
anymore. I'll see if it finishes compiling tomorrow.

Thanks for your help!

On Sun, 2 Aug 2020 at 23:14, Ian McInerney  wrote:

> Do you know if is called "lemon.exe" and is on the path by default? If it
> isn't on the path, then CMake might have difficulty finding it. You can try
> passing "-DLEMON=" in the CMake command line and I believe it will
> use that path instead of searching for it. Other than that, I might need
> Jon to take a look at it since he has a MSVC setup currently I believe (but
> we are relying on the built-in CMake FindLemon script, not our own).
>
> -Ian
>
> On Sun, Aug 2, 2020 at 11:06 PM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Just tried your branch and unfortunately couldn't get it to compile on
>> Visual Studio (even after a "vcpkg install lemon:x64-windows" and "vcpkg
>> integrate install")... I got the cmake error "lemon not found"
>>
>> I know Visual Studio isn't officially supported but any ideas what I
>> could do to install lemon correctly so visual studio/ cmake can recognise
>> it?
>>
>> Thanks
>>
>> Roberto
>>
>> On Sun, 2 Aug 2020 at 22:06, Ian McInerney 
>> wrote:
>>
>>> Yes, I have a branch on my fork [1] called "im/lemon" that can be used.
>>> It can be found here:
>>> https://gitlab.com/imcinerney/kicad/-/tree/im/lemon. If the build
>>> passes with that, it means lemon integration is working. CMake should error
>>> during configuration if the lemon executable can't be found
>>>
>>> -Ian
>>>
>>> [1] https://gitlab.com/imcinerney/kicad
>>>
>>> On Sun, Aug 2, 2020 at 10:01 PM Adam Wolf 
>>> wrote:
>>>
>>>> Is there a branch packages can use to make sure their lemon integration
>>>> is working?
>>>>
>>>> On Sun, Aug 2, 2020, 4:00 PM Ian McInerney 
>>>> wrote:
>>>>
>>>>> Two new build-time dependencies are being added to the master branch
>>>>> for v6:
>>>>> * lemon - The lemon parser generator
>>>>> * GTK3 (linux only) - the GTK3 libraries (only GTK3, not GTK2 - that
>>>>> is not supported anymore). This is technically also a runtime dependency,
>>>>> but we also need GTK3 for wxWidgets, so it shouldn't be a new runtime dep
>>>>> (only needing the build headers are new).
>>>>>
>>>>> The lemon parser is needed to fix
>>>>> https://gitlab.com/kicad/code/kicad/-/issues/5013 by changing how the
>>>>> files are generated (in MR
>>>>> https://gitlab.com/kicad/code/kicad/-/merge_requests/318). GTK3 is
>>>>> needed to enable new functionality inside the platform-specific
>>>>> KIPLATFORM library for Linux (such as overriding menu settings, moving
>>>>> files to trash, etc.)
>>>>>
>>>>> All developers should make sure they have these new dependencies
>>>>> installed, and nightly builds should add them to their build script 
>>>>> (Steve,
>>>>> thanks for updating Fedora's so quick!) I have opened issue on GitLab for
>>>>> the builders on there:
>>>>> https://gitlab.com/kicad/packaging/kicad-win-builder/-/issues/101
>>>>> https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues/332
>>>>>
>>>>> https://gitlab.com/kicad/packaging/kicad-ubuntu-builder/kicad-daily-package/-/issues/2
>>>>>
>>>>> I haven't merged any code into master that needs them yet, but I would
>>>>> like to merge the lemon fix as soon as possible (the problem it is solving
>>>>> has attracted increased attention it seems).
>>>>>
>>>>> -Ian
>>>>> ___
>>>>> 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] New Build Dependencies: Lemon + GTK3

[Roberto Fernández Bautista]

Just tried your branch and unfortunately couldn't get it to compile on
Visual Studio (even after a "vcpkg install lemon:x64-windows" and "vcpkg
integrate install")... I got the cmake error "lemon not found"

I know Visual Studio isn't officially supported but any ideas what I could
do to install lemon correctly so visual studio/ cmake can recognise it?

Thanks

Roberto

On Sun, 2 Aug 2020 at 22:06, Ian McInerney  wrote:

> Yes, I have a branch on my fork [1] called "im/lemon" that can be used. It
> can be found here: https://gitlab.com/imcinerney/kicad/-/tree/im/lemon.
> If the build passes with that, it means lemon integration is working. CMake
> should error during configuration if the lemon executable can't be found
>
> -Ian
>
> [1] https://gitlab.com/imcinerney/kicad
>
> On Sun, Aug 2, 2020 at 10:01 PM Adam Wolf 
> wrote:
>
>> Is there a branch packages can use to make sure their lemon integration
>> is working?
>>
>> On Sun, Aug 2, 2020, 4:00 PM Ian McInerney 
>> wrote:
>>
>>> Two new build-time dependencies are being added to the master branch for
>>> v6:
>>> * lemon - The lemon parser generator
>>> * GTK3 (linux only) - the GTK3 libraries (only GTK3, not GTK2 - that is
>>> not supported anymore). This is technically also a runtime dependency, but
>>> we also need GTK3 for wxWidgets, so it shouldn't be a new runtime dep (only
>>> needing the build headers are new).
>>>
>>> The lemon parser is needed to fix
>>> https://gitlab.com/kicad/code/kicad/-/issues/5013 by changing how the
>>> files are generated (in MR
>>> https://gitlab.com/kicad/code/kicad/-/merge_requests/318). GTK3 is
>>> needed to enable new functionality inside the platform-specific
>>> KIPLATFORM library for Linux (such as overriding menu settings, moving
>>> files to trash, etc.)
>>>
>>> All developers should make sure they have these new dependencies
>>> installed, and nightly builds should add them to their build script (Steve,
>>> thanks for updating Fedora's so quick!) I have opened issue on GitLab for
>>> the builders on there:
>>> https://gitlab.com/kicad/packaging/kicad-win-builder/-/issues/101
>>> https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues/332
>>>
>>> https://gitlab.com/kicad/packaging/kicad-ubuntu-builder/kicad-daily-package/-/issues/2
>>>
>>> I haven't merged any code into master that needs them yet, but I would
>>> like to merge the lemon fix as soon as possible (the problem it is solving
>>> has attracted increased attention it seems).
>>>
>>> -Ian
>>> ___
>>> 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] Something wrong with Windows nightly builds (1 Aug)?

[Roberto Fernández Bautista]

Thanks Ian. I stand corrected.

On Sat, 1 Aug 2020, 23:21 Ian McInerney,  wrote:

> No, it isn't a build error that is causing it. If you look at the status
> page showing the pipeline results (
> https://jenkins.simonrichter.eu/view/KiCad%20Status/job/windows-kicad-msys2-pipeline/),
> you'll see the builds finish successfully.
>
> Eeli, can you try downloading the most recent lite build and see which
> version string is being reported by the program itself? I downloaded the
> log from one of the runs on July 31, and it seems to have downloaded the
> most recent commit as of that time and was supposed to have built a package
> with "r16610.61c817377". Perhaps that is just contained in the most
> recently uploaded package for some reason?
>
> My guess is the packaging script can't handle the "-dirty" being appended
> to the KiCad build string. It is being marked as dirty right now due to
> https://gitlab.com/kicad/code/kicad/-/issues/5013, and the fix for it is
> in https://gitlab.com/kicad/code/kicad/-/merge_requests/318, but I can't
> apply the fix until all packaging setups are updated to contain lemon (so I
> now know that Windows has it, but OSX and many Linux ones don't).
>
> -Ian
>
> On Sat, Aug 1, 2020 at 9:40 PM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Hi Eeli,
>>
>> I assume this was due to what I highlighted in my previous email (
>> https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg38706.html).
>> The build was broken for Windows.
>>
>> I submitted a merge request (
>> https://gitlab.com/kicad/code/kicad/-/merge_requests/322) which was
>> merged last night, hence you are only seeing it today.
>>
>> Thanks.
>>
>> Roberto.
>>
>>
>> On Sat, 1 Aug 2020, 14:04 Eeli Kaikkonen, 
>> wrote:
>>
>>> [image: image.png]
>>>
>>> Something wrong with the Windows nightly builds?
>>>
>>> The commit 0c77 is from 30 July, I remember seeing that same commit
>>> dated to 30 and I downloaded it then (the link has different color) and I
>>> have it installed, but now the date is 1 Aug. There seems to be no newer
>>> nightly build available, I think there should be one or two of them.
>>>
>>> Eeli Kaikkonen
>>> ___
>>> 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] Something wrong with Windows nightly builds (1 Aug)?

[Roberto Fernández Bautista]

Hi Eeli,

I assume this was due to what I highlighted in my previous email (
https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg38706.html).
The build was broken for Windows.

I submitted a merge request (
https://gitlab.com/kicad/code/kicad/-/merge_requests/322) which was merged
last night, hence you are only seeing it today.

Thanks.

Roberto.


On Sat, 1 Aug 2020, 14:04 Eeli Kaikkonen,  wrote:

> [image: image.png]
>
> Something wrong with the Windows nightly builds?
>
> The commit 0c77 is from 30 July, I remember seeing that same commit dated
> to 30 and I downloaded it then (the link has different color) and I have it
> installed, but now the date is 1 Aug. There seems to be no newer nightly
> build available, I think there should be one or two of them.
>
> Eeli Kaikkonen
> ___
> 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] Compile errors in commits 577c1be3, 128ae8b4 & bd19892c

[Roberto Fernández Bautista]

(oops forgot to copy the mailing list)

Here is the merge request:
https://gitlab.com/kicad/code/kicad/-/merge_requests/322


On Fri, 31 Jul 2020 at 18:25, Seth Hillbrand  wrote:

> Yes, please if you have time.  Otherwise, I'll get to it eventually from
> the diff but it might take some time.
>
> -S
>
> On Fri, Jul 31, 2020 at 10:24 AM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Dear Seth,
>>
>> Okay I will do in the future. I thought it wasn't worth an MR due to only
>> 7 lines being changed, but I take your point.
>>
>> Shall I go ahead and create a merge request or are you happy to commit?
>>
>> Thanks.
>>
>> Roberto
>>
>


>>
>> On Fri, 31 Jul 2020 at 18:05, Seth Hillbrand  wrote:
>>
>>> Hi Roberto-
>>>
>>> Thank you for the diff.  In the future, can you please create a MR for
>>> all source changes.  This keeps it part of our standard formatting/test
>>> suite checks.
>>>
>>> Best-
>>> Seth
>>>
>>>
>>> On Fri, Jul 31, 2020 at 7:44 AM Roberto Fernández Bautista <
>>> roberto.fer@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I just tried compiling from master and seems there is a bug in commits
>>>> 577c1be3, 128ae8b4 &  bd19892c .  I am building in MSVC (Windows 10) using
>>>> Jon's CMakeSettings.json configuration file (with modified file paths),
>>>> using the "x64-Debug" configuration.
>>>>
>>>>
>>>> It seems this was a simple fix. See attached diff that fixed the
>>>> compile errors for me. Could someone with commit rights please review and
>>>> push the attached diff if happy?
>>>>
>>>> Extract below of locations of the compile errors:
>>>>
>>>> *Commit  577c1be3  *
>>>> --- pcbnew/dialogs/panel_setup_rules.cpp line 262 ---
>>>> line = (int) strtol( parts[0], nullptr, 10 );
>>>> offset = (int) strtol( parts[1], nullptr, 10 );
>>>> --- end ---
>>>>
>>>>
>>>> Error C2664 'long strtol(const char *,char **,int)': cannot convert
>>>> argument 1 from '_Ty' to 'const char *'
>>>> C:\MySources\kicad\build\x64-Debug\kicad
>>>> C:\MySources\kicad\pcbnew\dialogs\panel_setup_rules.cpp 262
>>>> Error C2664 'long strtol(const char *,char **,int)': cannot convert
>>>> argument 1 from '_Ty' to 'const char *'
>>>> C:\MySources\kicad\build\x64-Debug\kicad
>>>> C:\MySources\kicad\pcbnew\dialogs\panel_setup_rules.cpp 263
>>>>
>>>> *Commits 128aeb4 & bd19892c*
>>>>
>>>> --- qa/drc_proto/drc_engine.cpp line 245 ---
>>>>
>>>> drc_dbg(8, "   -> check condition '%s'\n", (const char*)
>>>> condition->m_Expression );
>>>>
>>>> bool result = condition->EvaluateFor( a, b );
>>>> if( result )
>>>> {
>>>> drc_dbg(8, "   -> rule '%s' matches, triggered by
>>>> condition '%s'\n", (const char*) rcond->rule->m_Name.c_str(), (const char*)
>>>> condition->m_Expression );
>>>> return rcond->rule;
>>>> }
>>>>
>>>> --- end ---
>>>>
>>>> Error C2440 'type cast': cannot convert from 'wxString' to 'const char
>>>> *' C:\MySources\kicad\build\x64-Debug\kicad
>>>> C:\MySources\kicad\qa\drc_proto\drc_engine.cpp 245
>>>> Error C2440 'type cast': cannot convert from 'wxString' to 'const char
>>>> *' C:\MySources\kicad\build\x64-Debug\kicad
>>>> C:\MySources\kicad\qa\drc_proto\drc_engine.cpp 250
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Roberto
>>>> ___
>>>> 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
>>>>
>>>
>>>
>>> --
>>> [image: KiCad Services Corporation Logo]
>>> Seth Hillbrand
>>> *Lead Developer*
>>> +1-530-302-5483‬ <+12126039372>
>>> Davis, CA
>>> www.kipro-pcb.comi...@kipro-pcb.com
>>>
>>
>
> --
> [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
>
___
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] Compile errors in commits 577c1be3, 128ae8b4 & bd19892c

[Roberto Fernández Bautista]

Hi all,

I just tried compiling from master and seems there is a bug in commits
577c1be3, 128ae8b4 &  bd19892c .  I am building in MSVC (Windows 10) using
Jon's CMakeSettings.json configuration file (with modified file paths),
using the "x64-Debug" configuration.


It seems this was a simple fix. See attached diff that fixed the compile
errors for me. Could someone with commit rights please review and push the
attached diff if happy?

Extract below of locations of the compile errors:

*Commit  577c1be3  *
--- pcbnew/dialogs/panel_setup_rules.cpp line 262 ---
line = (int) strtol( parts[0], nullptr, 10 );
offset = (int) strtol( parts[1], nullptr, 10 );
--- end ---


Error C2664 'long strtol(const char *,char **,int)': cannot convert
argument 1 from '_Ty' to 'const char *'
C:\MySources\kicad\build\x64-Debug\kicad
C:\MySources\kicad\pcbnew\dialogs\panel_setup_rules.cpp 262
Error C2664 'long strtol(const char *,char **,int)': cannot convert
argument 1 from '_Ty' to 'const char *'
C:\MySources\kicad\build\x64-Debug\kicad
C:\MySources\kicad\pcbnew\dialogs\panel_setup_rules.cpp 263

*Commits 128aeb4 & bd19892c*

--- qa/drc_proto/drc_engine.cpp line 245 ---

drc_dbg(8, "   -> check condition '%s'\n", (const char*)
condition->m_Expression );

bool result = condition->EvaluateFor( a, b );
if( result )
{
drc_dbg(8, "   -> rule '%s' matches, triggered by condition
'%s'\n", (const char*) rcond->rule->m_Name.c_str(), (const char*)
condition->m_Expression );
return rcond->rule;
}

--- end ---

Error C2440 'type cast': cannot convert from 'wxString' to 'const char *'
C:\MySources\kicad\build\x64-Debug\kicad
C:\MySources\kicad\qa\drc_proto\drc_engine.cpp 245
Error C2440 'type cast': cannot convert from 'wxString' to 'const char *'
C:\MySources\kicad\build\x64-Debug\kicad
C:\MySources\kicad\qa\drc_proto\drc_engine.cpp 250


Thanks

Roberto
 pcbnew/dialogs/panel_setup_rules.cpp | 6 +++---
 qa/drc_proto/drc_engine.cpp  | 6 --
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/pcbnew/dialogs/panel_setup_rules.cpp 
b/pcbnew/dialogs/panel_setup_rules.cpp
index 978452b98..4222d6327 100644
--- a/pcbnew/dialogs/panel_setup_rules.cpp
+++ b/pcbnew/dialogs/panel_setup_rules.cpp
@@ -253,14 +253,14 @@ void PANEL_SETUP_RULES::OnErrorLinkClicked( 
wxHtmlLinkEvent& event )
 {
 wxString  link = event.GetLinkInfo().GetHref();
 wxArrayString parts;
-int   line = 0, offset = 0;
+long   line = 0, offset = 0;
 
 wxStringSplit( link, parts, ':' );
 
 if( parts.size() > 1 )
 {
-line = (int) strtol( parts[0], nullptr, 10 );
-offset = (int) strtol( parts[1], nullptr, 10 );
+parts[0].ToLong(  );
+parts[1].ToLong(  );
 }
 
 int pos = m_textEditor->PositionFromLine( line - 1 ) + ( offset - 1 );
diff --git a/qa/drc_proto/drc_engine.cpp b/qa/drc_proto/drc_engine.cpp
index 4391db88a..079c854ef 100644
--- a/qa/drc_proto/drc_engine.cpp
+++ b/qa/drc_proto/drc_engine.cpp
@@ -242,12 +242,14 @@ test::DRC_RULE* test::DRC_ENGINE::EvalRulesForItems( 
test::DRC_RULE_ID_T ruleID,
 {
 for( auto condition : rcond->conditions )
 {
-drc_dbg(8, "   -> check condition '%s'\n", (const char*) 
condition->m_Expression );
+drc_dbg(8, "   -> check condition '%s'\n", (const char*) 
condition->m_Expression.c_str() );
 
 bool result = condition->EvaluateFor( a, b );
 if( result )
 {
-drc_dbg(8, "   -> rule '%s' matches, triggered by condition 
'%s'\n", (const char*) rcond->rule->m_Name.c_str(), (const char*) 
condition->m_Expression );
+drc_dbg( 8, "   -> rule '%s' matches, triggered by condition 
'%s'\n",
+(const char*) rcond->rule->m_Name.c_str(),
+(const char*) condition->m_Expression.c_str() );
 return rcond->rule;
 }
 }
___
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] Net Tie specification?

[Roberto Fernández Bautista]

Thank you all for the messages.

Maybe if  Simon sees this thread, he can send what he has?

The main thing I wanted to ensure was in there was support single pad net
ties (what is commonly known as a "star point"). I believe most of the
existing net tie support relies on separate pads being defined at different
positions.

CADSTAR uses star points which are defined as multiple through hole pads
with the exact same dimensions and same position. At this point I don't
know what KiCad's equivalent might be so wanted to ensure it was at least
considered when designing net tie specification.

Thanks.

Roberto.

On Thu, 30 Jul 2020 at 07:07, jp charras  wrote:

> Currently, the best doc about net ties ( and microwave components that
> create similar problems) is:
>
> https://lists.launchpad.net/kicad-developers/msg24455.html
> ([RFC] On net ties, microwave tools & custom pad shapes, altogether.)
>
> Le 30/07/2020 à 01:59, Jon Evans a écrit :
> > From this comment, maybe Simon has something that is not published yet?
> > https://gitlab.com/kicad/code/kicad/-/merge_requests/85#note_282728454
> >
> > On Wed, Jul 29, 2020 at 7:34 PM Seth Hillbrand 
> wrote:
> >>
> >> On Wed, Jul 29, 2020 at 4:16 PM Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I see from the road map that net ties are planned for v6 (
> https://gitlab.com/kicad/code/kicad/-/wikis/KiCad-6.0-Roadmap). In the
> "current status" it mentions that the specification is in development.
> >>>
> >>> Could someone please send me a link to the work in progress, so I can
> add some comments?
> >>>
> >>> Thanks
> >>>
> >>> Roberto.
> >>>
> >>
> >> I think Simon had some ideas here but I don't recall seeing a
> specification document.
> >>
>
>
>
> --
> 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

[Kicad-developers] Net Tie specification?

[Roberto Fernández Bautista]

Hi all,

I see from the road map that net ties are planned for v6 (
https://gitlab.com/kicad/code/kicad/-/wikis/KiCad-6.0-Roadmap). In the
"current status" it mentions that the specification is in development.

Could someone please send me a link to the work in progress, so I can add
some comments?

Thanks

Roberto.
___
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] Pin-swap / gate-swap - what is required?

[Roberto Fernández Bautista]

Hi all,

I thought I'd send a message here regarding
https://gitlab.com/kicad/code/kicad/-/issues/1950

Is there already a design document available? I'll happily make a start on
one if not, but want to make sure I'm not duplicating efforts.

Thanks.

Roberto.
___
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] OpenVentilator project update

[Roberto Fernández Bautista]

Very nice indeed!

Thanks for sharing.

On Thu, 23 Jul 2020 at 16:00, Wayne Stambaugh  wrote:

> For those of you who have been following the development of the
> OpenVentilator project[1].  A video[2] has been posted of a prototype
> being tested.  Kudos to the OpenVentilator project.
>
> Enjoy,
>
> Wayne
>
> [1]: http://openventilator.gitlab.io/
> [2]: https://www.youtube.com/watch?v=JCBr3W3eey8
>
> ___
> 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] CADSTAR Importer & Pad Stacks

[Roberto Fernández Bautista]

Dear Wayne,

Thanks for taking the time to look at this. However, I should credit Seth
for the hard work he has put on the document to get it to the shape it is
in now - thanks Seth!

I've made you editor now - feel free to edit directly. I suppose I should
make everyone from the lead development team an editor of this document -
could you send me a private email with their email addresses, so I can add
them?

Roberto.

On Thu, 16 Jul 2020 at 13:13, Wayne Stambaugh  wrote:

> Hi Roberto,
>
> Sorry it took so long to reply but I've been busy.  I did read your
> draft and it looks promising.   Please give me permission to at least
> add comments.  I don't necessarily need full edit permission.
>
> Thanks,
>
> Wayne
>
> On 7/11/20 8:01 AM, Roberto Fernández Bautista wrote:
> > Hi all,
> >
> > Has anybody had a chance to check the draft document I made on Pad
> > Stacks
> > <
> https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing
> >?
> >
> > I would like at least some feedback if this is the kind of document you
> > would be looking for, or if not what to change about it/what it should
> > focus on.
> >
> > I'm keen on pad stacks in KiCad since CADSTAR heavily relies on them -
> > at the moment the importer wouldn't be able to handle complex cases.
> >
> > I would like to help wherever I can to get this in before v6 feature
> freeze.
> >
> > Thanks.
> >
> > Roberto.
> >
> > On Sun, 21 Jun 2020 at 12:19, Roberto Fernández Bautista
> > mailto:roberto.fer@gmail.com>> wrote:
> >
> > Jon,
> >
> > Thanks for the advice. It will still be a while until I have
> > something working but yes, I will create a merge request once I have
> > a skeleton for the importer.
> >
> > @Jeff Young - I've made you an editor of the document I made on Pad
> > Stacks
> > <
> https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing
> >.
> > Hopefully you will have received a separate email with an editor's
> > link. Let me know if that wasn't the case.
> >
> > Roberto
> >
> > On Sun, 21 Jun 2020 at 02:51, Jon Evans  > <mailto:j...@craftyjon.com>> wrote:
> >
> > Hi Roberto,
> >
> > Welcome!  Thanks for pointing that out about Altium, I learn
> > something
> > new every day!
> >
> > I recommend that you open a merge request for your CADSTAR
> importer
> > once it is far enough along for people to do some basic tests.
> You
> > can mark it as "WIP", but having the MR open early will help get
> > early
> > testing and review so that we can help get it in for V6.
> >
> > Regarding Pad Stacks, @Jeff Young is probably the best person to
> > sync
> > with on the lead dev team as he has recently been doing some of
> the
> > groundwork.
> >
> > Best,
> > Jon
> >
> > On Sat, Jun 20, 2020 at 9:07 PM Roberto Fernández Bautista
> > mailto:roberto.fer@gmail.com>>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I'm new to the mailing list. I just wanted to make you aware
> > that I'm starting work on a native Zuken CADSTAR importer for
> > KiCad. I intend to follow a similar approach to @pointhi in the
> > forums for his Altium importer - trying to stick to similar
> > class structure where possible. My "short" term plan is to
> > provide an importer for the CADSTAR PCB archive format (which is
> > an ASCII file that is based on S-expressions). Since I'm doing
> > this in my free time, I expect it will take a few months but
> > hopefully the PCB importer would be ready before KiCad v6
> > feature freeze. Once I have something that sort of works, I'll
> > make a merge request and ask for further feedback on how to
> > improve it.
> > >
> > > Now, on a second note, I'd like to provide some input on Pad
> > Stacks. I joined the mailing list after the last post on the
> > thread "How do we envision Pad Stacks?"
> > (https://lists.launchpad.net/kicad-developers/msg44006.html), so
> > I can't reply to that thread directly, unfortunately. However,
> > the topic discussed in that thread

Re: [Kicad-developers] CADSTAR Importer & Pad Stacks

[Roberto Fernández Bautista]

Hi Seth,

Thank you very much for taking the time to look at it. I have made you an
editor now. Is there anyone else I should make editor as well?

Thanks.

Roberto


On Sun, 12 Jul 2020 at 02:55, Seth Hillbrand  wrote:

> Hi Roberto-
>
> Thank you for starting this process.  It would be very good to get a
> padstack implementation specification written.  Padstacks will be
> definitely be useful for many importers but whether it gets implemented
> will depend on developer resources to navigate the various issues (PNS,
> plotters, connectivity, draw items, etc).  We do currently take a number of
> shortcuts on the assumption that our pads are consistent across their layer
> range, so this will take a fair amount of work.
>
> I've sent a request for edit access to your document.  I'll do my best to
> help get it into implementation shape.
>
> Best-
> Seth
> KiCad Services Corporation [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬ <+12126039372>
> Davis, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> https://twitter.com/KiProEDA <https://twitter.com/KiProEDA>
> https://www.linkedin.com/company/kicad
> <https://www.linkedin.com/company/kicad>
>
>
> On 2020-07-11 05:01, Roberto Fernández Bautista wrote:
>
> Hi all,
>
> Has anybody had a chance to check the draft document I made on Pad Stacks
> <https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing>
> ?
>
> I would like at least some feedback if this is the kind of document you
> would be looking for, or if not what to change about it/what it should
> focus on.
>
> I'm keen on pad stacks in KiCad since CADSTAR heavily relies on them - at
> the moment the importer wouldn't be able to handle complex cases.
>
> I would like to help wherever I can to get this in before v6 feature
> freeze.
>
> Thanks.
>
> Roberto.
>
> On Sun, 21 Jun 2020 at 12:19, Roberto Fernández Bautista <
> roberto.fer@gmail.com> wrote:
>
>> Jon,
>>
>> Thanks for the advice. It will still be a while until I have something
>> working but yes, I will create a merge request once I have a skeleton for
>> the importer.
>>
>> @Jeff Young - I've made you an editor of the document I made on Pad
>> Stacks
>> <https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing>.
>> Hopefully you will have received a separate email with an editor's link.
>> Let me know if that wasn't the case.
>>
>> Roberto
>>
>> On Sun, 21 Jun 2020 at 02:51, Jon Evans  wrote:
>>
>>> Hi Roberto,
>>>
>>> Welcome!  Thanks for pointing that out about Altium, I learn something
>>> new every day!
>>>
>>> I recommend that you open a merge request for your CADSTAR importer
>>> once it is far enough along for people to do some basic tests.  You
>>> can mark it as "WIP", but having the MR open early will help get early
>>> testing and review so that we can help get it in for V6.
>>>
>>> Regarding Pad Stacks, @Jeff Young is probably the best person to sync
>>> with on the lead dev team as he has recently been doing some of the
>>> groundwork.
>>>
>>> Best,
>>> Jon
>>>
>>> On Sat, Jun 20, 2020 at 9:07 PM Roberto Fernández Bautista
>>>  wrote:
>>> >
>>> > Hi all,
>>> >
>>> > I'm new to the mailing list. I just wanted to make you aware that I'm
>>> starting work on a native Zuken CADSTAR importer for KiCad. I intend to
>>> follow a similar approach to @pointhi in the forums for his Altium importer
>>> - trying to stick to similar class structure where possible. My "short"
>>> term plan is to provide an importer for the CADSTAR PCB archive format
>>> (which is an ASCII file that is based on S-expressions). Since I'm doing
>>> this in my free time, I expect it will take a few months but hopefully the
>>> PCB importer would be ready before KiCad v6 feature freeze. Once I have
>>> something that sort of works, I'll make a merge request and ask for further
>>> feedback on how to improve it.
>>> >
>>> > Now, on a second note, I'd like to provide some input on Pad Stacks. I
>>> joined the mailing list after the last post on the thread "How do we
>>> envision Pad Stacks?" (
>>> https://lists.launchpad.net/kicad-developers/msg44006.html), so I can't
>>> reply to that thread directly, unfortunately. However, the topic discussed
>>> in that threa

Re: [Kicad-developers] CADSTAR Importer & Pad Stacks

[Roberto Fernández Bautista]

Hi all,

Has anybody had a chance to check the draft document I made on Pad Stacks
<https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing>
?

I would like at least some feedback if this is the kind of document you
would be looking for, or if not what to change about it/what it should
focus on.

I'm keen on pad stacks in KiCad since CADSTAR heavily relies on them - at
the moment the importer wouldn't be able to handle complex cases.

I would like to help wherever I can to get this in before v6 feature freeze.

Thanks.

Roberto.

On Sun, 21 Jun 2020 at 12:19, Roberto Fernández Bautista <
roberto.fer@gmail.com> wrote:

> Jon,
>
> Thanks for the advice. It will still be a while until I have something
> working but yes, I will create a merge request once I have a skeleton for
> the importer.
>
> @Jeff Young - I've made you an editor of the document I made on Pad Stacks
> <https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing>.
> Hopefully you will have received a separate email with an editor's link.
> Let me know if that wasn't the case.
>
> Roberto
>
> On Sun, 21 Jun 2020 at 02:51, Jon Evans  wrote:
>
>> Hi Roberto,
>>
>> Welcome!  Thanks for pointing that out about Altium, I learn something
>> new every day!
>>
>> I recommend that you open a merge request for your CADSTAR importer
>> once it is far enough along for people to do some basic tests.  You
>> can mark it as "WIP", but having the MR open early will help get early
>> testing and review so that we can help get it in for V6.
>>
>> Regarding Pad Stacks, @Jeff Young is probably the best person to sync
>> with on the lead dev team as he has recently been doing some of the
>> groundwork.
>>
>> Best,
>> Jon
>>
>> On Sat, Jun 20, 2020 at 9:07 PM Roberto Fernández Bautista
>>  wrote:
>> >
>> > Hi all,
>> >
>> > I'm new to the mailing list. I just wanted to make you aware that I'm
>> starting work on a native Zuken CADSTAR importer for KiCad. I intend to
>> follow a similar approach to @pointhi in the forums for his Altium importer
>> - trying to stick to similar class structure where possible. My "short"
>> term plan is to provide an importer for the CADSTAR PCB archive format
>> (which is an ASCII file that is based on S-expressions). Since I'm doing
>> this in my free time, I expect it will take a few months but hopefully the
>> PCB importer would be ready before KiCad v6 feature freeze. Once I have
>> something that sort of works, I'll make a merge request and ask for further
>> feedback on how to improve it.
>> >
>> > Now, on a second note, I'd like to provide some input on Pad Stacks. I
>> joined the mailing list after the last post on the thread "How do we
>> envision Pad Stacks?" (
>> https://lists.launchpad.net/kicad-developers/msg44006.html), so I can't
>> reply to that thread directly, unfortunately. However, the topic discussed
>> in that thread is very relevant to the work I am trying to do with the
>> CADSTAR importer (and I bet also important for the Altium importer
>> @pointhi  made).
>> >
>> > I'd like to point out two small inaccuracies in Jon's message:
>> >
>> > In Altium you can define a full pad stack when editing footprints:
>> Altium uses a default 14-electrical-layer board stackup which is then
>> mapped to whatever layers you actually use in your design when you include
>> the footprint.
>> > You can define a SMD pad in an inner layer.
>> >
>> > Please see attached screenshots from v20.1 showing above two cases,
>> maybe earlier versions didn't allow this?.  More details can be found here:
>> https://www.altium.com/documentation/altium-designer/pcb-prop-padpad-properties-ad
>> .
>> >
>> >
>> > To keep this email short, I've created a document with other bits of
>> information that I feel might be useful (such as how CADSTAR handles Pad
>> Stacks) as well as some suggestions for Pad Stack implementation in KiCad -
>> maybe this could be the start of a more complex design document?
>> https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing
>> >
>> > Since this mailing list is public, I have made the above link view only
>> access, but if you'd like to edit, just request it.
>> >
>> > Please let me know what you think.
>> >
>> > Roberto Fernandez (Qbort)
>> >
>> >
>> > ___
>> > 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] WYSISYG pad editor

[Roberto Fernández Bautista]

Hi Jeff,

Did you have a chance to look at the draft document I sent on padstacks a
few days ago? I briefly explain how Altium and Cadstar handle pads and vias
in that document - hopefully it is helpful?

I'd like to point out that custom pad shapes are not actually well
supported in most other commercial EDAs, so what you are doing at KiCad is
definitely above and beyond! Great stuff!

The prototype shape editor that you are talking about: is this in pcbnew or
in the footprint editor? I suppose it would be valid to use this both for
editing vias in the PCB as well as pads in a footprint, in the library.
Maybe this could be done in the properties window of the pad/via where you
could have a basic drawing canvas to draw the shape of the pad/via (maybe
in the future you could even import a DXF or other similar format to define
the pad shape). Each shape could maybe be saved into a library that can be
re-used/selected.

I'd suggest that regardless of it being a "high contrast mode" or a
"properties" window: if you are creating custom shapes for a pad, you
should *only *be doing that: i.e. you are entering "pad editing mode" - you
don't want to be accidentally moving other things around while you are
doing that and certain certain things should be restricted while in this
"mode" - e.g.

   - if you "paste other stuff", you should look at what is being pasted
   and if it is a valid shape object, you could accept it, otherwise just
   don't do anything;
   - you should not allow to "delete the pad anchor" - only to move it
   - new objects on different layers - isn't the idea of this to be a
   padstack editor? If so, then assign those shapes to the specific layer.

I'm not sure I understand your second approach of exploding pads into
shapes? Seems to me like you might end up with a lot of random shapes that
don't get recombined if you forget to run the "recombine" command? Also I
can see that you'd end up joining up several pads together accidentally...
I'd suggest the "editing" mode should restrict editing to a single pad

Roberto (Qbort)

On Thu, 25 Jun 2020 at 21:53, Jeff Young  wrote:

> I implemented a prototype of a WYSIWYG custom-pad shape editor.
>
> You can ctrl-E on a pad and it explodes it and puts you into high-contrast
> mode with the shapes.  After editing the shapes a second ctrl-E re-combines
> everything and exits high-contrast mode.
>
> While it’s pretty neat if you do exactly that, it turns out to have a
> bazillion corner cases.  (What happens if you paste other stuff in; what
> happens if you delete the pad anchor; what happens if you create new
> objects on different layers; etc.)
>
> So I was considering a different idea which would be more “regular” (from
> an implementation perspective).
>
> Basically it would be a command to explode *all* pads in the current
> footprint, and a command to recombine everything.  The recombine would
> expand outwards from each pad to consume touching copper shapes.  (It might
> still need a few edge cases for net-ties.)
>
> Thoughts?
> ___
> 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] CADSTAR Importer & Pad Stacks

[Roberto Fernández Bautista]

Jon,

Thanks for the advice. It will still be a while until I have something
working but yes, I will create a merge request once I have a skeleton for
the importer.

@Jeff Young - I've made you an editor of the document I made on Pad Stacks
<https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing>.
Hopefully you will have received a separate email with an editor's link.
Let me know if that wasn't the case.

Roberto

On Sun, 21 Jun 2020 at 02:51, Jon Evans  wrote:

> Hi Roberto,
>
> Welcome!  Thanks for pointing that out about Altium, I learn something
> new every day!
>
> I recommend that you open a merge request for your CADSTAR importer
> once it is far enough along for people to do some basic tests.  You
> can mark it as "WIP", but having the MR open early will help get early
> testing and review so that we can help get it in for V6.
>
> Regarding Pad Stacks, @Jeff Young is probably the best person to sync
> with on the lead dev team as he has recently been doing some of the
> groundwork.
>
> Best,
> Jon
>
> On Sat, Jun 20, 2020 at 9:07 PM Roberto Fernández Bautista
>  wrote:
> >
> > Hi all,
> >
> > I'm new to the mailing list. I just wanted to make you aware that I'm
> starting work on a native Zuken CADSTAR importer for KiCad. I intend to
> follow a similar approach to @pointhi in the forums for his Altium importer
> - trying to stick to similar class structure where possible. My "short"
> term plan is to provide an importer for the CADSTAR PCB archive format
> (which is an ASCII file that is based on S-expressions). Since I'm doing
> this in my free time, I expect it will take a few months but hopefully the
> PCB importer would be ready before KiCad v6 feature freeze. Once I have
> something that sort of works, I'll make a merge request and ask for further
> feedback on how to improve it.
> >
> > Now, on a second note, I'd like to provide some input on Pad Stacks. I
> joined the mailing list after the last post on the thread "How do we
> envision Pad Stacks?" (
> https://lists.launchpad.net/kicad-developers/msg44006.html), so I can't
> reply to that thread directly, unfortunately. However, the topic discussed
> in that thread is very relevant to the work I am trying to do with the
> CADSTAR importer (and I bet also important for the Altium importer
> @pointhi  made).
> >
> > I'd like to point out two small inaccuracies in Jon's message:
> >
> > In Altium you can define a full pad stack when editing footprints:
> Altium uses a default 14-electrical-layer board stackup which is then
> mapped to whatever layers you actually use in your design when you include
> the footprint.
> > You can define a SMD pad in an inner layer.
> >
> > Please see attached screenshots from v20.1 showing above two cases,
> maybe earlier versions didn't allow this?.  More details can be found here:
> https://www.altium.com/documentation/altium-designer/pcb-prop-padpad-properties-ad
> .
> >
> >
> > To keep this email short, I've created a document with other bits of
> information that I feel might be useful (such as how CADSTAR handles Pad
> Stacks) as well as some suggestions for Pad Stack implementation in KiCad -
> maybe this could be the start of a more complex design document?
> https://docs.google.com/document/d/1lxBI7_X_I7pO-nuDHPRVlfRBH24XTmwuuN69o_Bqk3s/edit?usp=sharing
> >
> > Since this mailing list is public, I have made the above link view only
> access, but if you'd like to edit, just request it.
> >
> > Please let me know what you think.
> >
> > Roberto Fernandez (Qbort)
> >
> >
> > ___
> > 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