Re: [Kicad-developers] macos notarization status

[Wayne Stambaugh]

Way to go Adam!

On 2/4/20 5:03 PM, Adam Wolf wrote:
> Hi folks!
> 
> Good news.
> 
> On my dev machine, I've got the DMG, the apps, all the frameworks,
> everything, all notarized.  The apps are all signed even!
> 
> We don't need to change the symlinks! (I'm a little bummed that the
> relayed question->answer from WWDC wasn't accurate, but that was 3
> years ago, and there have been changes to how notarization is enforced
> as recently as 2020/02/03. :) )
> 
> What was it?  A combination of two things:
> 
> * Moving some Python and ngspice things around in the bundle so that
> only certain types of executables were in certain directories of the
> bundle
> * Apple says to submit a zip to their notarization service.  If you
> create a zip with "zip", it won't work. You need to use ditto with a
> few different arguments.  I suspect that this was messing with the
> symlinks.  *sigh*
> 
> Alright, so what's next?
> 
> 1) I want to remove all the KiCad patches from kicad-mac-builder,
> long-term.  As part of that, there's a few changes from this effort
> that I want to get into the KiCad cmake files.  I think they're
> innocent and gentle but we can discuss them on the MRs I'll make. :)
> However, I have an old patch to create a distributable Python
> Framework that I don't really want to merge into our tree--and I am
> personally OK with leaving it as a patch in kicad-mac-builder, since
> a) it has been that way since I created it years ago and 2) my next
> effort after this notarization/signing is 100% done is getting Python
> 3 working on the macOS builds, and as part of that I'll be getting rid
> of this patch.  At that point kicad-mac-builder won't have any KiCad
> patches at all.
> 
> 2) It is certainly possible that I broke things or made minor mistakes
> with signing/notarization, so I will generate some of these builds on
> my dev machine and get them available as testing builds for people to
> test.
> 
> 3) It is possible there are ways that users use the apps now that will
> break.  For instance, it will no longer be OK for users to put their
> own files inside the bundle.  This is a good thing, but we may need to
> prepare some instructions or something to help break it to users--if
> anyone has strong opinions here please let me know.  I am terrified
> that users are doing this, downloading a new version of KiCad,
> overwriting their old "executables" and then losing their data files.
> I have read of at least one report of this happening on kicad.info and
> it breaks my heart.   I know there has been some confusion about this
> point technically but see
> https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG304
> for details.
> 
> 4) I have some kicad-mac-builder changes to make to get all of this
> signing and notarization stuff working on CI.  I expect this will take
> at least a few days as the part I need to modify the most is a part
> that's been a pain lately and needs to be gutted anyway...
> 
> 5) When all of this is done, and this is stable, Python 3 on macOS is
> next on my plate.
> 
> Thanks folks!
> 
> If anyone has any questions or comments or opinions on this stuff, let
> me know, otherwise I'll keep at it :)
> 
> Adam Wolf
> 
> On Mon, Feb 3, 2020 at 10:05 AM Bernhard Stegmaier
>  wrote:
>>
>> Adam,
>>
>> One last thing, just to be sure… you are notarizing the final kicad.app 
>> after the “make install”?
>> If you use the (intermediate) one of the build directory, the sub-bundles 
>> might not yet be in place as they should…
>>
>>
>> Bernhard
>>
>>> On 3. Feb 2020, at 16:59, Bernhard Stegmaier  
>>> wrote:
>>>
>>> OK, I see… this is weird.
>>> My understanding from what I read in the documentation was, that it should 
>>> sign everything in the top-level bundle (kicad.app) including sub-apps you 
>>> might have in kicad.app/Contents/Applications.
>>>
>>>
>>> Regards,
>>> Bernhard
>>>
 On 3. Feb 2020, at 16:47, Adam Wolf  wrote:

 I am not notarizing the DMGs.  While this is possible, it has not been
 necessary so far.

 When I tried notarizing kicad.app but not the others, when I move to a
 new computer, it complains that eeschema.app is not notarized.

 The problem is not putting the signed kicad.app into an unsigned dmg.

 On Mon, Feb 3, 2020 at 8:11 AM Bernhard Stegmaier
  wrote:
>
> Hi Adam,
>
> I am also no fan of the symlinks, but having a different approach will
> be probably some work.
>
>> I had someone ask if what we do would work during WWDC and I was told
>> it would not work.  I consistently get "the signature is invalid" when
>> signing while we have symlinks, and when I remove the symlinks and
>> just sign KiCad.app this error goes away.
>
> I don't doubt that the symlinks in the DMG don't work.
> What you explained is exactly what I had in mind:
> (1) Sign *only* kicad.app as is. No complete DMG with 

Re: [Kicad-developers] macos notarization status

[Adam Wolf]

My first email to the list about my signing efforts are from early 2017!

On Tue, Feb 4, 2020 at 4:12 PM Jeff Young  wrote:
>
> Awesome!  Great job, Adam.
>
>
> > On 4 Feb 2020, at 22:03, Adam Wolf  wrote:
> >
> > Hi folks!
> >
> > Good news.
> >
> > On my dev machine, I've got the DMG, the apps, all the frameworks,
> > everything, all notarized.  The apps are all signed even!
> >
> > We don't need to change the symlinks! (I'm a little bummed that the
> > relayed question->answer from WWDC wasn't accurate, but that was 3
> > years ago, and there have been changes to how notarization is enforced
> > as recently as 2020/02/03. :) )
> >
> > What was it?  A combination of two things:
> >
> > * Moving some Python and ngspice things around in the bundle so that
> > only certain types of executables were in certain directories of the
> > bundle
> > * Apple says to submit a zip to their notarization service.  If you
> > create a zip with "zip", it won't work. You need to use ditto with a
> > few different arguments.  I suspect that this was messing with the
> > symlinks.  *sigh*
> >
> > Alright, so what's next?
> >
> > 1) I want to remove all the KiCad patches from kicad-mac-builder,
> > long-term.  As part of that, there's a few changes from this effort
> > that I want to get into the KiCad cmake files.  I think they're
> > innocent and gentle but we can discuss them on the MRs I'll make. :)
> > However, I have an old patch to create a distributable Python
> > Framework that I don't really want to merge into our tree--and I am
> > personally OK with leaving it as a patch in kicad-mac-builder, since
> > a) it has been that way since I created it years ago and 2) my next
> > effort after this notarization/signing is 100% done is getting Python
> > 3 working on the macOS builds, and as part of that I'll be getting rid
> > of this patch.  At that point kicad-mac-builder won't have any KiCad
> > patches at all.
> >
> > 2) It is certainly possible that I broke things or made minor mistakes
> > with signing/notarization, so I will generate some of these builds on
> > my dev machine and get them available as testing builds for people to
> > test.
> >
> > 3) It is possible there are ways that users use the apps now that will
> > break.  For instance, it will no longer be OK for users to put their
> > own files inside the bundle.  This is a good thing, but we may need to
> > prepare some instructions or something to help break it to users--if
> > anyone has strong opinions here please let me know.  I am terrified
> > that users are doing this, downloading a new version of KiCad,
> > overwriting their old "executables" and then losing their data files.
> > I have read of at least one report of this happening on kicad.info and
> > it breaks my heart.   I know there has been some confusion about this
> > point technically but see
> > https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG304
> > for details.
> >
> > 4) I have some kicad-mac-builder changes to make to get all of this
> > signing and notarization stuff working on CI.  I expect this will take
> > at least a few days as the part I need to modify the most is a part
> > that's been a pain lately and needs to be gutted anyway...
> >
> > 5) When all of this is done, and this is stable, Python 3 on macOS is
> > next on my plate.
> >
> > Thanks folks!
> >
> > If anyone has any questions or comments or opinions on this stuff, let
> > me know, otherwise I'll keep at it :)
> >
> > Adam Wolf
> >
> > On Mon, Feb 3, 2020 at 10:05 AM Bernhard Stegmaier
> >  wrote:
> >>
> >> Adam,
> >>
> >> One last thing, just to be sure… you are notarizing the final kicad.app 
> >> after the “make install”?
> >> If you use the (intermediate) one of the build directory, the sub-bundles 
> >> might not yet be in place as they should…
> >>
> >>
> >> Bernhard
> >>
> >>> On 3. Feb 2020, at 16:59, Bernhard Stegmaier  
> >>> wrote:
> >>>
> >>> OK, I see… this is weird.
> >>> My understanding from what I read in the documentation was, that it 
> >>> should sign everything in the top-level bundle (kicad.app) including 
> >>> sub-apps you might have in kicad.app/Contents/Applications.
> >>>
> >>>
> >>> Regards,
> >>> Bernhard
> >>>
>  On 3. Feb 2020, at 16:47, Adam Wolf  
>  wrote:
> 
>  I am not notarizing the DMGs.  While this is possible, it has not been
>  necessary so far.
> 
>  When I tried notarizing kicad.app but not the others, when I move to a
>  new computer, it complains that eeschema.app is not notarized.
> 
>  The problem is not putting the signed kicad.app into an unsigned dmg.
> 
>  On Mon, Feb 3, 2020 at 8:11 AM Bernhard Stegmaier
>   wrote:
> >
> > Hi Adam,
> >
> > I am also no fan of the symlinks, but having a different approach will
> > be probably some work.
> >
> >> I had someone ask if what we do would work during WWDC and I was told
> 

Re: [Kicad-developers] macos notarization status

[Jeff Young]

Awesome!  Great job, Adam.


> On 4 Feb 2020, at 22:03, Adam Wolf  wrote:
> 
> Hi folks!
> 
> Good news.
> 
> On my dev machine, I've got the DMG, the apps, all the frameworks,
> everything, all notarized.  The apps are all signed even!
> 
> We don't need to change the symlinks! (I'm a little bummed that the
> relayed question->answer from WWDC wasn't accurate, but that was 3
> years ago, and there have been changes to how notarization is enforced
> as recently as 2020/02/03. :) )
> 
> What was it?  A combination of two things:
> 
> * Moving some Python and ngspice things around in the bundle so that
> only certain types of executables were in certain directories of the
> bundle
> * Apple says to submit a zip to their notarization service.  If you
> create a zip with "zip", it won't work. You need to use ditto with a
> few different arguments.  I suspect that this was messing with the
> symlinks.  *sigh*
> 
> Alright, so what's next?
> 
> 1) I want to remove all the KiCad patches from kicad-mac-builder,
> long-term.  As part of that, there's a few changes from this effort
> that I want to get into the KiCad cmake files.  I think they're
> innocent and gentle but we can discuss them on the MRs I'll make. :)
> However, I have an old patch to create a distributable Python
> Framework that I don't really want to merge into our tree--and I am
> personally OK with leaving it as a patch in kicad-mac-builder, since
> a) it has been that way since I created it years ago and 2) my next
> effort after this notarization/signing is 100% done is getting Python
> 3 working on the macOS builds, and as part of that I'll be getting rid
> of this patch.  At that point kicad-mac-builder won't have any KiCad
> patches at all.
> 
> 2) It is certainly possible that I broke things or made minor mistakes
> with signing/notarization, so I will generate some of these builds on
> my dev machine and get them available as testing builds for people to
> test.
> 
> 3) It is possible there are ways that users use the apps now that will
> break.  For instance, it will no longer be OK for users to put their
> own files inside the bundle.  This is a good thing, but we may need to
> prepare some instructions or something to help break it to users--if
> anyone has strong opinions here please let me know.  I am terrified
> that users are doing this, downloading a new version of KiCad,
> overwriting their old "executables" and then losing their data files.
> I have read of at least one report of this happening on kicad.info and
> it breaks my heart.   I know there has been some confusion about this
> point technically but see
> https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG304
> for details.
> 
> 4) I have some kicad-mac-builder changes to make to get all of this
> signing and notarization stuff working on CI.  I expect this will take
> at least a few days as the part I need to modify the most is a part
> that's been a pain lately and needs to be gutted anyway...
> 
> 5) When all of this is done, and this is stable, Python 3 on macOS is
> next on my plate.
> 
> Thanks folks!
> 
> If anyone has any questions or comments or opinions on this stuff, let
> me know, otherwise I'll keep at it :)
> 
> Adam Wolf
> 
> On Mon, Feb 3, 2020 at 10:05 AM Bernhard Stegmaier
>  wrote:
>> 
>> Adam,
>> 
>> One last thing, just to be sure… you are notarizing the final kicad.app 
>> after the “make install”?
>> If you use the (intermediate) one of the build directory, the sub-bundles 
>> might not yet be in place as they should…
>> 
>> 
>> Bernhard
>> 
>>> On 3. Feb 2020, at 16:59, Bernhard Stegmaier  
>>> wrote:
>>> 
>>> OK, I see… this is weird.
>>> My understanding from what I read in the documentation was, that it should 
>>> sign everything in the top-level bundle (kicad.app) including sub-apps you 
>>> might have in kicad.app/Contents/Applications.
>>> 
>>> 
>>> Regards,
>>> Bernhard
>>> 
 On 3. Feb 2020, at 16:47, Adam Wolf  wrote:
 
 I am not notarizing the DMGs.  While this is possible, it has not been
 necessary so far.
 
 When I tried notarizing kicad.app but not the others, when I move to a
 new computer, it complains that eeschema.app is not notarized.
 
 The problem is not putting the signed kicad.app into an unsigned dmg.
 
 On Mon, Feb 3, 2020 at 8:11 AM Bernhard Stegmaier
  wrote:
> 
> Hi Adam,
> 
> I am also no fan of the symlinks, but having a different approach will
> be probably some work.
> 
>> I had someone ask if what we do would work during WWDC and I was told
>> it would not work.  I consistently get "the signature is invalid" when
>> signing while we have symlinks, and when I remove the symlinks and
>> just sign KiCad.app this error goes away.
> 
> I don't doubt that the symlinks in the DMG don't work.
> What you explained is exactly what I had in mind:
> (1) Sign 

Re: [Kicad-developers] macos notarization status

[Adam Wolf]

Hi folks!

Good news.

On my dev machine, I've got the DMG, the apps, all the frameworks,
everything, all notarized.  The apps are all signed even!

We don't need to change the symlinks! (I'm a little bummed that the
relayed question->answer from WWDC wasn't accurate, but that was 3
years ago, and there have been changes to how notarization is enforced
as recently as 2020/02/03. :) )

What was it?  A combination of two things:

* Moving some Python and ngspice things around in the bundle so that
only certain types of executables were in certain directories of the
bundle
* Apple says to submit a zip to their notarization service.  If you
create a zip with "zip", it won't work. You need to use ditto with a
few different arguments.  I suspect that this was messing with the
symlinks.  *sigh*

Alright, so what's next?

1) I want to remove all the KiCad patches from kicad-mac-builder,
long-term.  As part of that, there's a few changes from this effort
that I want to get into the KiCad cmake files.  I think they're
innocent and gentle but we can discuss them on the MRs I'll make. :)
However, I have an old patch to create a distributable Python
Framework that I don't really want to merge into our tree--and I am
personally OK with leaving it as a patch in kicad-mac-builder, since
a) it has been that way since I created it years ago and 2) my next
effort after this notarization/signing is 100% done is getting Python
3 working on the macOS builds, and as part of that I'll be getting rid
of this patch.  At that point kicad-mac-builder won't have any KiCad
patches at all.

2) It is certainly possible that I broke things or made minor mistakes
with signing/notarization, so I will generate some of these builds on
my dev machine and get them available as testing builds for people to
test.

3) It is possible there are ways that users use the apps now that will
break.  For instance, it will no longer be OK for users to put their
own files inside the bundle.  This is a good thing, but we may need to
prepare some instructions or something to help break it to users--if
anyone has strong opinions here please let me know.  I am terrified
that users are doing this, downloading a new version of KiCad,
overwriting their old "executables" and then losing their data files.
I have read of at least one report of this happening on kicad.info and
it breaks my heart.   I know there has been some confusion about this
point technically but see
https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG304
for details.

4) I have some kicad-mac-builder changes to make to get all of this
signing and notarization stuff working on CI.  I expect this will take
at least a few days as the part I need to modify the most is a part
that's been a pain lately and needs to be gutted anyway...

5) When all of this is done, and this is stable, Python 3 on macOS is
next on my plate.

Thanks folks!

If anyone has any questions or comments or opinions on this stuff, let
me know, otherwise I'll keep at it :)

Adam Wolf

On Mon, Feb 3, 2020 at 10:05 AM Bernhard Stegmaier
 wrote:
>
> Adam,
>
> One last thing, just to be sure… you are notarizing the final kicad.app after 
> the “make install”?
> If you use the (intermediate) one of the build directory, the sub-bundles 
> might not yet be in place as they should…
>
>
> Bernhard
>
> > On 3. Feb 2020, at 16:59, Bernhard Stegmaier  
> > wrote:
> >
> > OK, I see… this is weird.
> > My understanding from what I read in the documentation was, that it should 
> > sign everything in the top-level bundle (kicad.app) including sub-apps you 
> > might have in kicad.app/Contents/Applications.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 3. Feb 2020, at 16:47, Adam Wolf  wrote:
> >>
> >> I am not notarizing the DMGs.  While this is possible, it has not been
> >> necessary so far.
> >>
> >> When I tried notarizing kicad.app but not the others, when I move to a
> >> new computer, it complains that eeschema.app is not notarized.
> >>
> >> The problem is not putting the signed kicad.app into an unsigned dmg.
> >>
> >> On Mon, Feb 3, 2020 at 8:11 AM Bernhard Stegmaier
> >>  wrote:
> >>>
> >>> Hi Adam,
> >>>
> >>> I am also no fan of the symlinks, but having a different approach will
> >>> be probably some work.
> >>>
>  I had someone ask if what we do would work during WWDC and I was told
>  it would not work.  I consistently get "the signature is invalid" when
>  signing while we have symlinks, and when I remove the symlinks and
>  just sign KiCad.app this error goes away.
> >>>
> >>> I don't doubt that the symlinks in the DMG don't work.
> >>> What you explained is exactly what I had in mind:
> >>> (1) Sign *only* kicad.app as is. No complete DMG with symlinks or
> >>> whatever.
> >>> (2) Create DMG with previously signed kicad.app and symlinks, libraries
> >>> and whatever you put into. Don't try to notarize this DMG, DMG is just
> >>> a container.
> >>>
> 

Re: [Kicad-developers] File format specification

[Wayne Stambaugh]

https://bazaar.launchpad.net/~stambaughw/kicad/doc-read-only/view/head:/doc/help/file_formats/file_formats.pdf

On 2/4/20 2:16 PM, Johannes Pfister wrote:
> Hello
> 
> Where can i get the file format specifications for kicad_pdb?
> 
> I tried it here https://kicad-pcb.org/help/file-formats/ which leads
> to 
> http://bazaar.launchpad.net/~stambaughw/kicad/doc-read-only/download/head:/1115%4016bec504-3128-0410-b3e8-8e38c2123bca:trunk%252Fkicad-doc%252Fdoc%252Fhelp%252Ffile_formats%252Ffile_formats.pdf/file_formats.pdf
> but this link is broken.
> As far as I remember, i was able to download it from there in the
> past. Did this document move?
> 

___
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] File format specification

[Johannes Pfister]

Hello

Where can i get the file format specifications for kicad_pdb?

I tried it here https://kicad-pcb.org/help/file-formats/ which leads
to 
http://bazaar.launchpad.net/~stambaughw/kicad/doc-read-only/download/head:/1115%4016bec504-3128-0410-b3e8-8e38c2123bca:trunk%252Fkicad-doc%252Fdoc%252Fhelp%252Ffile_formats%252Ffile_formats.pdf/file_formats.pdf
but this link is broken.
As far as I remember, i was able to download it from there in the
past. Did this document move?

-- 
Johannes Pfister
Electronic Engineering
johannes.pfis...@josttech.ch
+41 55 460 22 25

josTTech GmbH
Haemmerli 6
8855 Wangen - Switzerland
+41 55 460 22 25
www.josTTech.ch - i...@josttech.ch
Vending - Engineering - Trading

___
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] How to access the fbp sources

[Simon Richter]

Hi,

On Tue, Feb 04, 2020 at 07:40:02PM +0100, ja...@veith.net wrote:

> To access the fbp sources I tried to install the wxFormbuilder for
> Ubuntu 18.04LTS. As there seems neither distro version nor Debian
> packages I used the github repo with v3.9.0:

I've made a set of unofficial Debian packages that live at
http://simonrichter.eu/debian/ . The 3.9.0 packages have a known bug that
the generated output claims to be built with 3.8.0, as that is hardcoded,
but other than that the packages seem to work alright.

   Simon

___
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] How to access the fbp sources

[ja...@veith.net]

To access the fbp sources I tried to install the wxFormbuilder for 
Ubuntu 18.04LTS. As there seems neither distro version nor Debian 
packages I used the github repo with v3.9.0:


>sudo apt install libwxgtk3.0-dev libwxgtk-media3.0-dev meson
>sudo apt install libcanberra-gtk-module libcanberra-gtk3-module
>git clone --recursive --depth=1 
https://github.com/wxFormBuilder/wxFormBuilder

>cd wxFormBuilder
>meson _build --prefix $PWD/_install
>ninja -C _build install

went through without errors. After this, invoking
./_install/bin/wxformbuilder generates numerous errors:

19:08:05: Error: Could not set current working directory (error 2: No 
such file or directory)
19:08:05: Error: 
/home/jv/wxFormBuilder/_install/lib/wxformbuilder/libforms.so: cannot 
open shared object file: No such fil
19:08:05: Error: Error loading library 
/home/jv/wxFormBuilder/_install/lib/wxformbuilder/libforms 

19:08:05: Error: Could not set current working directory (error 2: No 
such file or directory)


libforms.so is available in path 
_install/lib/x86_64-linux.gnu/wxformbuilder while wxFormBuilder searches 
path without x86_64-linux.gnu. Any help on how to go on appreciated.


Thanks,
Jürgen




___
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] Repeat request for help from icon maintainer.

[Brian Piccioni]

JP

Thank you so much for your help!

Removing the Msys2 versions of inkscape and then installing the windows 
package and adjusting my path to


    export PATH=$PATH:"/c/Program Files/Inkscape"

and then commenting out line 33 in zutil.h, recompiling and replacing 
pngcrush seemed to work.


I am providing details in case others have this challenge.

I am now waiting for the compile to run but it seems happy.

Thanks again!

Brian

On 2020-02-04 12:27 p.m., jp charras wrote:

Le 04/02/2020 à 17:32, Brian Piccioni a écrit :

JP

Thanks for this.

Unfortunately, inkscape and pngcrush seem to be a work in process on Msys.

If I install the package

     $ pacman -S mingw-w64-x86_64-inkscape

and run inkscape I get the error

     $ inkscape
     C:/msys64/mingw64/bin/inkscape.exe: error while loading shared
libraries: libpoppler-89.dll: cannot open shared object file: No such
file or directory

If I build inkscape in MSYS and run make install I get

     [  0%] Built target potrace
     make[2]: Entering directory '/home/bjpic/debug'
     [  0%] Creating 48 pixel tall
C:/msys64/home/bjpic/debug/bitmaps_png/tmp/wizard_add_fplib_icon.png
     Unknown option --without-gui
     [  0%] Creating 16 pixel tall
C:/msys64/home/bjpic/debug/bitmaps_png/tmp/folder.png
     Unknown option --without-gui
     [  0%] Creating cleaned file
C:/msys64/home/bjpic/kicad/bitmaps_png/png_16/folder.png

running inkscape --without-gui causes the same error.

Similarly, installing the pngcrush package in msys2 pacman -S
mingw-w64-x86_64-pngcrush results in the warning

$ pngcrush
Warning: versions are different between png.h and png.c
   png.h version: 1.6.34
   png.c version: 1.6.37

Making pngcrush under msys2 fails with a forced error.

In general it seems that many related utilities under Msys2 are a dogs
breakfasts.

Perhaps for the moment it would be best if I simply made my bitmaps
manually.

Brian


I have no issues with inkscape and pngcrush.
However:
- Inkscape is installed from binaries coming from Inkscape site.
- pngcrush was built on msys2 by me from pngcrush sources.
This is a very small program and it is easy to build on msys2.
However, to build it, remove (or comment) the line 33 in zutil.h
"typedef long ptrdiff_t;  /* guess -- will be caught if guess is wrong */"
to avoid a conflict with a mingw included file.

the first useful line of my script running cmake is:
export PATH=$WXMSW:$PATH:/d/inkscape:/d/pngcrush

You will have to remove inkscape from msys2.

Attached, my msys2 script to run cmake.

Good luck...


On 2020-02-04 9:34 a.m., jp charras wrote:

Le 04/02/2020 à 15:06, Brian Piccioni a écrit :

Hello

I emailed earlier because when I follow the directions to create a new
icon under MSYS2 it fails.

This means that either

1) the directions are wrong or
2) I am following them incorrectly.

Perhaps an icon maintainer can get in contact with me and work through
this?

I basically need to clone the icons annotate_right_down and
annotate_down_right rotated 90, 180, and 270 degrees. Not complicated.

thanks


Brian

Hi Brian,

To build the .cpp files the option MAINTAIN_PNGS must be set to ON in
makefiles.

So:
1 - To avoid cache issues, delete your current CMakeCache.txt file in
your build directory.
2 - Run cmake as before, with option -DMAINTAIN_PNGS=ON to recreated the
makefiles

After that you should be able to rebuild/create the .cpp bitmap files.


___
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] Repeat request for help from icon maintainer.

[jp charras]

Le 04/02/2020 à 17:32, Brian Piccioni a écrit :
> JP
> 
> Thanks for this.
> 
> Unfortunately, inkscape and pngcrush seem to be a work in process on Msys.
> 
> If I install the package
> 
>     $ pacman -S mingw-w64-x86_64-inkscape
> 
> and run inkscape I get the error
> 
>     $ inkscape
>     C:/msys64/mingw64/bin/inkscape.exe: error while loading shared
> libraries: libpoppler-89.dll: cannot open shared object file: No such
> file or directory
> 
> If I build inkscape in MSYS and run make install I get
> 
>     [  0%] Built target potrace
>     make[2]: Entering directory '/home/bjpic/debug'
>     [  0%] Creating 48 pixel tall
> C:/msys64/home/bjpic/debug/bitmaps_png/tmp/wizard_add_fplib_icon.png
>     Unknown option --without-gui
>     [  0%] Creating 16 pixel tall
> C:/msys64/home/bjpic/debug/bitmaps_png/tmp/folder.png
>     Unknown option --without-gui
>     [  0%] Creating cleaned file
> C:/msys64/home/bjpic/kicad/bitmaps_png/png_16/folder.png
> 
> running inkscape --without-gui causes the same error.
> 
> Similarly, installing the pngcrush package in msys2 pacman -S
> mingw-w64-x86_64-pngcrush results in the warning
> 
> $ pngcrush
> Warning: versions are different between png.h and png.c
>   png.h version: 1.6.34
>   png.c version: 1.6.37
> 
> Making pngcrush under msys2 fails with a forced error.
> 
> In general it seems that many related utilities under Msys2 are a dogs
> breakfasts.
> 
> Perhaps for the moment it would be best if I simply made my bitmaps
> manually.
> 
> Brian
> 

I have no issues with inkscape and pngcrush.
However:
- Inkscape is installed from binaries coming from Inkscape site.
- pngcrush was built on msys2 by me from pngcrush sources.
This is a very small program and it is easy to build on msys2.
However, to build it, remove (or comment) the line 33 in zutil.h
"typedef long ptrdiff_t;  /* guess -- will be caught if guess is wrong */"
to avoid a conflict with a mingw included file.

the first useful line of my script running cmake is:
export PATH=$WXMSW:$PATH:/d/inkscape:/d/pngcrush

You will have to remove inkscape from msys2.

Attached, my msys2 script to run cmake.

Good luck...

> 
> On 2020-02-04 9:34 a.m., jp charras wrote:
>> Le 04/02/2020 à 15:06, Brian Piccioni a écrit :
>>> Hello
>>>
>>> I emailed earlier because when I follow the directions to create a new
>>> icon under MSYS2 it fails.
>>>
>>> This means that either
>>>
>>> 1) the directions are wrong or
>>> 2) I am following them incorrectly.
>>>
>>> Perhaps an icon maintainer can get in contact with me and work through
>>> this?
>>>
>>> I basically need to clone the icons annotate_right_down and
>>> annotate_down_right rotated 90, 180, and 270 degrees. Not complicated.
>>>
>>> thanks
>>>
>>>
>>> Brian
>> Hi Brian,
>>
>> To build the .cpp files the option MAINTAIN_PNGS must be set to ON in
>> makefiles.
>>
>> So:
>> 1 - To avoid cache issues, delete your current CMakeCache.txt file in
>> your build directory.
>> 2 - Run cmake as before, with option -DMAINTAIN_PNGS=ON to recreated the
>> makefiles
>>
>> After that you should be able to rebuild/create the .cpp bitmap files.
>>
> 
> ___
> 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


-- 
Jean-Pierre CHARRAS
#! /bin/sh

rm -f CMakeCache.txt
WXMSW=/d/wxWidgets-3.1.3/Release_dll
export PATH=$WXMSW:$PATH:/d/inkscape:/d/pngcrush

KICAD_DIR=/e/kicad

OPT0=-DKICAD_SCRIPTING_ACTION_MENU=OFF
OPT1=-DKICAD_SCRIPTING=OFF
OPT2=-DKICAD_SCRIPTING_MODULES=OFF
OPT3=-DKICAD_SCRIPTING_WXPYTHON=OFF
OPT4=-DOPENSSL_ROOT_DIR=/mingw32
OPT5=-DBUILD_GITHUB_PLUGIN=ON
OPT6=-DMAINTAIN_PNGS=ON
OPT7=-DBUILD_SMALL_DEBUG_FILES=ON
OPT8=-DKICAD_SPICE=ON
OPT9=-DNGSPICE_ROOT_DIR=/c/Spice
OPT10=-DKICAD_USE_OCE=ON
OPT11=-DOCE_DIR=/g/opencascade/lib_oce/cmake
OPT12=-DKICAD_BUILD_QA_TESTS=OFF
#OPT13=-DKICAD_STDLIB_DEBUG=ON
OPT13=-DKICAD_STDLIB_LIGHT_DEBUG=ON
OPT14=-DKICAD_SANITIZE=OFF


INSTALL_DIR=-DCMAKE_INSTALL_PREFIX=$KICAD_DIR
PYTH_INST_DIR=-DPYTHON_SITE_PACKAGE_PATH=$KICAD_DIR/lib/python2.7/site-packages

#Debug Release Relwithdebinfo Minsizerel
#BUILD_TYPE=Debug
BUILD_TYPE=Release

cmake -G "MSYS Makefiles" -DCMAKE_BUILD_TYPE=$BUILD_TYPE\
$OPT0 $OPT1 $OPT2 $OPT3 $OPT4 $OPT5 $OPT6 $OPT7 $OPT8 $OPT9 $OPT10 $OPT11 
$OPT12 $OPT13 $OPT14\
$INSTALL_DIR $PYTH_INST_DIR ../../
___
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] Repeat request for help from icon maintainer.

[Brian Piccioni]

JP

Thanks for this.

Unfortunately, inkscape and pngcrush seem to be a work in process on Msys.

If I install the package

    $ pacman -S mingw-w64-x86_64-inkscape

and run inkscape I get the error

    $ inkscape
    C:/msys64/mingw64/bin/inkscape.exe: error while loading shared 
libraries: libpoppler-89.dll: cannot open shared object file: No such 
file or directory


If I build inkscape in MSYS and run make install I get

    [  0%] Built target potrace
    make[2]: Entering directory '/home/bjpic/debug'
    [  0%] Creating 48 pixel tall 
C:/msys64/home/bjpic/debug/bitmaps_png/tmp/wizard_add_fplib_icon.png

    Unknown option --without-gui
    [  0%] Creating 16 pixel tall 
C:/msys64/home/bjpic/debug/bitmaps_png/tmp/folder.png

    Unknown option --without-gui
    [  0%] Creating cleaned file 
C:/msys64/home/bjpic/kicad/bitmaps_png/png_16/folder.png


running inkscape --without-gui causes the same error.

Similarly, installing the pngcrush package in msys2 pacman -S 
mingw-w64-x86_64-pngcrush results in the warning


$ pngcrush
Warning: versions are different between png.h and png.c
  png.h version: 1.6.34
  png.c version: 1.6.37

Making pngcrush under msys2 fails with a forced error.

In general it seems that many related utilities under Msys2 are a dogs 
breakfasts.


Perhaps for the moment it would be best if I simply made my bitmaps 
manually.


Brian


On 2020-02-04 9:34 a.m., jp charras wrote:

Le 04/02/2020 à 15:06, Brian Piccioni a écrit :

Hello

I emailed earlier because when I follow the directions to create a new
icon under MSYS2 it fails.

This means that either

1) the directions are wrong or
2) I am following them incorrectly.

Perhaps an icon maintainer can get in contact with me and work through
this?

I basically need to clone the icons annotate_right_down and
annotate_down_right rotated 90, 180, and 270 degrees. Not complicated.

thanks


Brian

Hi Brian,

To build the .cpp files the option MAINTAIN_PNGS must be set to ON in
makefiles.

So:
1 - To avoid cache issues, delete your current CMakeCache.txt file in
your build directory.
2 - Run cmake as before, with option -DMAINTAIN_PNGS=ON to recreated the
makefiles

After that you should be able to rebuild/create the .cpp bitmap files.



___
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] Welcome New Bug Squad members

[Jeff Young]

Welcome, guys!

> On 4 Feb 2020, at 14:15, Dino Ghilardi  wrote:
> 
> Congratulations Eeli and Simon!
> 
> Dino.
> 
> On 04/02/20 10:40, Seth Hillbrand wrote:
>> Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon Richter.  
>> As members of the Bug Squad, they help to verify, triage and classify our 
>> bug reports, serving a critical role in ensuring KiCad continues to improve.
>> Thanks to you both along with long-time squad member Michael Kavanaugh for 
>> all that you do to push KiCad forward.  We look forward to building great 
>> things together.
>> Best-
>> Seth
>> Seth Hillbrand
>> KiCad Services Corporation
>> https://www.kipro-pcb.com
>> +1 530 302 5483 | +1 212 603 9372
>> ___
>> 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] Repeat request for help from icon maintainer.

[jp charras]

Le 04/02/2020 à 15:06, Brian Piccioni a écrit :
> Hello
> 
> I emailed earlier because when I follow the directions to create a new
> icon under MSYS2 it fails.
> 
> This means that either
> 
> 1) the directions are wrong or
> 2) I am following them incorrectly.
> 
> Perhaps an icon maintainer can get in contact with me and work through
> this?
> 
> I basically need to clone the icons annotate_right_down and
> annotate_down_right rotated 90, 180, and 270 degrees. Not complicated.
> 
> thanks
> 
> 
> Brian
Hi Brian,

To build the .cpp files the option MAINTAIN_PNGS must be set to ON in
makefiles.

So:
1 - To avoid cache issues, delete your current CMakeCache.txt file in
your build directory.
2 - Run cmake as before, with option -DMAINTAIN_PNGS=ON to recreated the
makefiles

After that you should be able to rebuild/create the .cpp bitmap files.

-- 
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] Welcome New Bug Squad members

[Dino Ghilardi]

Congratulations Eeli and Simon!

Dino.

On 04/02/20 10:40, Seth Hillbrand wrote:
Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon 
Richter.  As members of the Bug Squad, they help to verify, triage and 
classify our bug reports, serving a critical role in ensuring KiCad 
continues to improve.


Thanks to you both along with long-time squad member Michael Kavanaugh 
for all that you do to push KiCad forward.  We look forward to building 
great things together.


Best-
Seth

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

___
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] Repeat request for help from icon maintainer.

[Brian Piccioni]

Hello

I emailed earlier because when I follow the directions to create a new 
icon under MSYS2 it fails.


This means that either

1) the directions are wrong or
2) I am following them incorrectly.

Perhaps an icon maintainer can get in contact with me and work through this?

I basically need to clone the icons annotate_right_down and 
annotate_down_right rotated 90, 180, and 270 degrees. Not complicated.


thanks


Brian



___
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 | WIP: Geographical re-annotation (!56)

[Brian Piccioni]

Eeli

I wasn't aware the merge. Gitlab is a nightmare for me and I may have 
closed it accidentally. Ever since I opened my brianadtdocumenteddesigns 
account it would not let me clone kicad master. Eventually I found a 
workaround to let me clone alex's fork but then when I tried to fix my 
geographical annotation it resolutely would not let me do that no matter 
what I tried. So I opened a new gitlab account bjpiccioni and have been 
using that.


I would very much like thoughts/help on the UI in general. I am very bad 
with UIs and was hoping that someone would comment. While I appreciate 
good UIs I don't seem to be able to create them myself.


I like your idea and will work on it.

I will also send out another plea for help specifically for the missing 
icons. I think I can manually create them for debugging purposes but it 
baffles me nobody seems to know how to make them using the recommended 
procedure.


Any additional comments/suggestions are welcomed.


Brian

On 2020-02-04 3:55 a.m., Eeli Kaikkonen wrote:

GitLab

Eeli Kaikkonen  commented:

I'm curious, do all the parties who have been involved in this 
discussion receive notifications even though this merge request has 
been closed?


I use this discussion because the actual comment is on topic, I hope 
Brian doesn't mind reviving this.


You asked about the icons in the mailing list. I can't help with that, 
but I have another thought about the UI WRT the direction.


Here's a screenshot from your old UI: image 



I don't know what kind of changes you have planned, but if you are 
going to use all 8 direction options, it would be better to break up 
into two options: "Start from" and "Direction". Then there would be 4 
options + 2 options:


|Start From: Top left Top right Bottom left Bottom right Direction: 
Horizontal first Vertical first|


And there could be one place for the icon which would show the final 
combination.


This would be IMO much more easy to comprehend than putting all 8 into 
one list.


—
Reply to this email directly or view it on GitLab 
.
You're receiving this email because of your account on gitlab.com. If 
you'd like to receive fewer emails, you can unsubscribe 
 
from this thread or adjust your notification settings.


___
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] Welcome New Bug Squad members

[Adam Wolf]

Congratulations, thanks and good luck! :)

On Tue, Feb 4, 2020 at 3:44 AM Seth Hillbrand  wrote:
>
> On 2020-02-04 03:40, Seth Hillbrand wrote:
> > Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon
> > Richter.  As members of the Bug Squad, they help to verify, triage and
> > classify our bug reports, serving a critical role in ensuring KiCad
> > continues to improve.
> >
> > Thanks to you both along with long-time squad member Michael Kavanaugh
> > for all that you do to push KiCad forward.  We look forward to
> > building great things together.
>
>
> Whoops.  *Kavanagh*  Sorry for the typo, Michael.
>
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372
>
> ___
> 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] Welcome New Bug Squad members

[Seth Hillbrand]

On 2020-02-04 03:40, Seth Hillbrand wrote:

Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon
Richter.  As members of the Bug Squad, they help to verify, triage and
classify our bug reports, serving a critical role in ensuring KiCad
continues to improve.

Thanks to you both along with long-time squad member Michael Kavanaugh
for all that you do to push KiCad forward.  We look forward to
building great things together.



Whoops.  *Kavanagh*  Sorry for the typo, Michael.

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

___
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] Welcome New Bug Squad members

[Seth Hillbrand]

Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon 
Richter.  As members of the Bug Squad, they help to verify, triage and 
classify our bug reports, serving a critical role in ensuring KiCad 
continues to improve.


Thanks to you both along with long-time squad member Michael Kavanaugh 
for all that you do to push KiCad forward.  We look forward to building 
great things together.


Best-
Seth

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

___
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