Re: [Kicad-developers] Experience compiling latest HEAD

[Carsten Schoenert]

Hello Ruth,

Am 28.06.21 um 21:34 schrieb Ruth Ivimey-Cook:

> I would *really* appreciate an ubuntu "official" nightly build of 5.99
> that uses wx3.1

there was never and probably will never be any official Ubuntu KiCad
packages.

The "official Ubuntu" packages are taken from Debian by the automatic
pick up from Debian unstable.

wxwidget 3.1 is the development version for the upcoming stable version
3.2 which possible breaks the API/ABI with every new version that is
getting released. That makes this software breaking other software too
often and by this unfit to get introduced into Debian unstable, it
simply make to less sense.

-- 
Regards
Carsten

___
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] Experience compiling latest HEAD

[Wayne Stambaugh]

On 6/28/21 12:34 PM, Ruth Ivimey-Cook wrote:

I have v5.1 from http://ppa.launchpad.net/kicad/kicad-5.1-releases/ubuntu/


In the short term, we will probably continue to package 5.1 with wx 3.0. 
 This is primarily to ensure that our python scripts aren't broken by 
Python 3 which is require when building with wxWidgets 3.1.




And the kicad built nightly v5.99 from 
http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu/


And it's v5.99 I was asking to include wx 3.1.


I though we had changed our nightly Ubuntu builds over to 3.1 but 
apparently not.  Maybe our PPA package dev can comment about what it 
would take to do that.  I've been using 3.1 on Debian testing for quite 
a long time now and it seems to be stable and it also fixes a lot of issues.




Ruth


On 28/06/2021 16:53, Wayne Stambaugh wrote:

Which version of KiCad are you talking about, 5.1 or master?  Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA?  The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.

On 6/28/21 11:38 AM, Ruth Ivimey-Cook wrote:

Folks,

I'm using Kicad on Kubuntu 21.04 with a 4K screen, and experience the
'tiny fonts' problem on it. I got fed up with that a few days ago and
noticed the recommendations that wxWin 3.1 fixes many issues. I first
tried to install the 'flatpak' build, but couldn't do so, so then I
compiled it from scratch. It took a little while but I did get to a
build (re: the recent GLEW posts, that was a problem for me also).

The project screen loaded fine and displays the fonts very nicely...
however, pcbnew fails (either directly or via project window) with a DRI
failed to authenticate message. Having looked around, I think this could
be because I'm using the nVidia driver for my GTX1060 GPU which doesn't
play nice with DRI. However, the officially-compiled kicad versions
(including nightly) work fine in that regard, so I'm not sure what is
happening there.

So, this is a long post to say:

 Please incorporate wx 3.1 into the Linux build, as you have for the
Win and Mac builds, because wx 3.0 is broken.

Also, it would be good to know (if it is known) what happened with 
DRI 2.


Ruth


___
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] Experience compiling latest HEAD

[Ruth Ivimey-Cook]

  
  


On 28/06/2021 20:28, Johannes Maibaum
  wrote:


  
  
Running this with "flatpak run org.kicad.KiCad" runs the
  application, but the fonts problem (very small fonts for
  native wx widgets) is not resolved.
  
  We decided to keep the 5.1 flatpak on wx 3.0, and switch to
wx 3.1 for 6.0 (and 5.99). So again, another reason for you to
skip 5.1, I guess.
  
  
  I read from your messages, that you can already run 5.99
successfully, but if you want to try, I'd be excited to hear how
building the kicad-nightly flatpak works for you.
  

While I can run 5.99 from official kicad-nightly it suffers from
  the 'small fonts' problem which makes it very hard to use.
I tried building kicad from gitlab with wx3,1 latest and built
  something that sort of worked, and didn't suffer from the small
  fonts problem, but also as soon as 3D initialisation started it
  crashed with the DRI 2 authorisation message. (this doesn't happen
  with nightly).

I would *really* appreciate an ubuntu "official" nightly build of
  5.99 that uses wx3.1
Ruth

-- 
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
  


___
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] Experience compiling latest HEAD

[Johannes Maibaum]

Hi Ruth,

Am Montag, dem 28.06.2021 um 19:55 +0100 schrieb Ruth Ivimey-Cook:
> I think the initial problem with flatpak was that I couldn't figure
> out how to install kicad. Things like "flatpak search flathub KiCad"
> don't return useful results.
You can leave out the remote from flatpak search commands. It will
always search all your active remotes.
> However, I then found the problem with flatpak was that I needed
> kicad 5.99, not 5.1, because a key part I had was a 5.99 format
> symbol & footprint and I don't know of any way to downgrade that to
> the earlier format.
There is no "backwards" converter for symbols/footprints in the 5.99
format, AFAIK. So yes, if you depend on certain 5.99
symbols/footprints, there is no point in running 5.1.
> Running this with "flatpak run org.kicad.KiCad" runs the application,
> but the fonts problem (very small fonts for native wx widgets) is not
> resolved.
We decided to keep the 5.1 flatpak on wx 3.0, and switch to wx 3.1 for
6.0 (and 5.99). So again, another reason for you to skip 5.1, I guess.

I read from your messages, that you can already run 5.99 successfully,
but if you want to try, I'd be excited to hear how building the kicad-
nightly flatpak works for you.


Johannes
___
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] Experience compiling latest HEAD

[Ruth Ivimey-Cook]

  
  
Johannes,

Thanks for asking... I think the initial problem with flatpak was
  that I couldn't figure out how to install kicad. Things like
  "flatpak search flathub KiCad" don't return useful results.
  However, I then found the problem with flatpak was that I needed
  kicad 5.99, not 5.1, because a key part I had was a 5.99 format
  symbol & footprint and I don't know of any way to downgrade
  that to the earlier format.

Running the flatpak command does:
> flatpak install
flathub org.kicad.KiCad
  
  Note that the directories 
  
  '/var/lib/flatpak/exports/share'
  '/home/ruth/.local/share/flatpak/exports/share'
  
  are not in the search path set by
the XDG_DATA_DIRS environment variable, so
  applications installed by Flatpak
may not appear on your desktop until the
  session is restarted.
  `
  Looking for matches…
  Required runtime for
org.kicad.KiCad/x86_64/stable
(runtime/org.freedesktop.Platform/x86_64/20.08) found in remote
flathub
... and then I installed version 5.1.10:
$ flatpak list
  Name  
  Application ID
  Version    Branch   Installation
  Name 
  Application ID    Version  Branch
  Installation
  Freedesktop Platform 
  org.freedesktop.Platform  20.08.13 20.08  system
  Mesa 
  org.freedesktop.Platform.GL.default   21.1.1   20.08  system
  nvidia-465-19-01 
  …desktop.Platform.GL.nvidia-465-19-01  1.4    system
  Intel
  org.freedesktop.Platform.VAAPI.Intel   20.08  system
  openh264 
  org.freedesktop.Platform.openh264 2.1.0    2.0    system
  Breeze Gtk theme 
  org.gtk.Gtk3theme.Breeze   3.22   system
  KiCad
  org.kicad.KiCad   5.1.10   stable system
  KiCad Footprint Libraries
  org.kicad.KiCad.Library.Footprints stable system
  KiCad 3D Model Libraries 
  org.kicad.KiCad.Library.Packages3D stable system
  KiCad Schematic Symbol L…
  org.kicad.KiCad.Library.Symbols    stable system
  KiCad Templates  
  org.kicad.KiCad.Library.Templates  stable system
  
  Running this with "flatpak run org.kicad.KiCad" runs the
  application, but the fonts problem (very small fonts for native wx
  widgets) is not resolved.
This is the version info:
Application: KiCad
Version: 5.1.10, release build
Libraries:
    wxWidgets 3.0.5
    libcurl/7.71.1-DEV GnuTLS/3.6.15 (NSS/3.49.2)
(OpenSSL/1.1.1k) zlib/1.2.11 libidn2/2.3.0
Platform: Linux 5.11.0-22-generic x86_64, 64 bit, Little endian,
wxGTK
Build Info:
    wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8)
GTK+ 3.24
    Boost: 1.76.0
    OpenCASCADE Technology: 7.5.1
    Curl: 7.71.1-DEV
    Compiler: GCC 10.2.0 with C++ ABI 1014
Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=OFF
    KICAD_USE_OCC=ON
    KICAD_SPICE=ON


--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
  


___
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] Experiences/feedback with 'nightly'

[Jeff Young]

Hi Ruth,

Are your 3D issues in raytracing or normal (OpenGL) rendering?  Could you 
screenshot your Preferences > 3D Viewer > Display Options panel?  (I’m unable 
to reproduce any of the issues you’re mentioning.)

For unlock all you can do a Select All and then a right-mouse-button Unlock.

You can convert old-format symbols to new format in the Manage Symbol Libraries 
dialog (the Migrate Libraries button).

The project viewer stuff is controversial. ;)  (See: 
https://gitlab.com/kicad/code/kicad/-/issues/7946 
.)

Single sided board (well, odd layer boards actually) is tracked in 
https://gitlab.com/kicad/code/kicad/-/issues/2425 
.

Cheers,
Jeff.


> On 28 Jun 2021, at 17:28, Ruth Ivimey-Cook  wrote:
> 
> I've been using the nightly build for the last couple of weeks on a hobby 
> project, with generally good results. I thought it might be helpful for you 
> some feedback on it. My comparisons are against 5.1.14:
> 
> I love the new cut/paste, click to move etc. Very much easier. I love too the 
> Schematic's 'edit endpoint' on a wire to extend it, but couldn't it support 
> general movement too, as is true for 'd' on the PCB?
> 
> I like the new part Group and part Lock options, and the dialog for lock 
> override. Have I missed finding a general Unlock All, though?
> 
> The router tool to drag whole parts with their tracks (opt 'd') gets very 
> easily confused with conflicts on tracks that shouldn't be there and for any 
> many-pin part it's almost unusable. I didn't notice the same problems in 
> v5.1. By 'shouldn't be there' I think there is a conflict is with THT pads 
> where the hole itself becomes something to avoid. You can also conflict with 
> existing track segments which should and can move and are at least 1 segment 
> distant from the part being moved (e.g. part has pad A, which has a track 
> segment on it B, which then bends at 45deg to a segment C. Moving the part 
> moves A and B, but not C, which could move but is instead counted as a 
> conflict. Where the part movement is in line with tracks, things are 
> generally ok; problems arise when part movement is at an angle to track 
> connections.
> 
> A nice enhancement would be for PCB drag to support dragging of contiguous 
> groups of parts (e.g. when you use an area selection).
> 
> The 3D viewer is great as always. I'm not sure if this is a regression, but 
> when the solder resist layer (green etc) is not clipped at pcb holes, e.g. 
> mounting holes, and should be, so currently you can't see all the way through 
> holes. Switch off display of solder resist and you can. You also can't see 
> through THT part holes when components are not shown.
> 
> The new library format was obviously needed and makes more sense 
> (internals-wise). However, integration with older libraries needs 
> improvement, specifically there needs to be a way to auto import specific 
> symbols to an existing new-format library (e.g. project-specific) from an 
> old-format library (or if present this option is not obvious), and ideally a 
> way to export an new format symbol to an old format (even if that is then 
> marked as potentially broken and needs checking). At present it is not 
> practical for everyone to be on the new format all the time. Migration 
> old->new was good when that was appropriate.
> 
> The new project viewer tool layout is improved, but could the clickable area 
> for each tool encompass the text as well as the image? Perhaps also the icons 
> could be somewhat larger.
> 
> I was slightly confused, when setting up my board, that I wasn't allowed to 
> specify a single sided board... there is no option for just one layer of 
> copper. It so happens that my project grew and I do need 2 layers, but still.
> 
> My project has so far had a major revision, as I reimplemented the core of 
> the circuit, and in the process reset the part numbering. Of course there was 
> a fair bit of movement and redoing of pcb placement but some non-core parts 
> stayed put. I was hoping/expecting the areas that hadn't been changed would 
> either show up with lots of broken connections or be retained as-is, but no. 
> For parts that were renumbered  but not moved on the pcb, the track was left 
> with its original net, while the part's connections were those of the new 
> one. (e.g. old part R1 pad1 = 3V3 and has track 3V3, following change now R1 
> pad1 is GND. After change, R1 still refers to the same footprint so pad1 is 
> now GND but track is still 3V3, and yet the ratsnest showed nothing wrong). 
> NB Rule checker dialog not invoked, just the ratsnest.
> 
> Hope this helps,
> 
> Ruth
> 
> 
> -- 
> Tel: 01223 414180
> Blog: http://www.ivimey.org/blog
> LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : 

Re: [Kicad-developers] Experience compiling latest HEAD

[Johannes Maibaum]

Hi Ruth,

Am Montag, dem 28.06.2021 um 16:38 +0100 schrieb Ruth Ivimey-Cook:
> I first tried to install the 'flatpak' build, but couldn't do so, so
> then I compiled it from scratch.

I maintain the KiCad flatpak manifests.

Did you try to install the flatpak from flathub.org, i.e.

flatpak install flathub org.kicad.KiCad

(assuming you have the flathub remote installed) or did you try to
build the kicad-nightly flatpak from Gitlab yourself, i.e.
https://gitlab.com/kicad/packaging/kicad-flatpak/kicad-nightly-flatpaks/kicad-nightly-flatpak
?

Either should be possible, so if you didn't succeed, I am curious what
exactly has failed when, and where?

Refering to your initial grief about tiny fonts on 4K monitors, the
official "stable" channel on flathub was built on wx 3.0, while the
nightly-flatpak manifest, tracking master, builds on wx 3.1. So, if you
want to keep trying the flatpak build, please try the nightly-flatpak.
The README found via the link above should get you started if you are
new to flatpak.


Cheers,
Johannes


___
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] Experience compiling latest HEAD

[Ruth Ivimey-Cook]

I compiled latest HEAD (master) from the gitlab repo, using dev packages 
as required (e.g. glew) from Kubuntu except for the wx 3.1 build, which 
came from https://repos.codelite.org/wx3.1.5/ubuntu/  (codelite maintain 
a set of builds of it for different distros).


Ruth

On 28/06/2021 16:53, Wayne Stambaugh wrote:

Which version of KiCad are you talking about, 5.1 or master?  Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA?  The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.

On 6/28/21 11:38 AM, Ruth Ivimey-Cook wrote:

Folks,

I'm using Kicad on Kubuntu 21.04 with a 4K screen, and experience the
'tiny fonts' problem on it. I got fed up with that a few days ago and
noticed the recommendations that wxWin 3.1 fixes many issues. I first
tried to install the 'flatpak' build, but couldn't do so, so then I
compiled it from scratch. It took a little while but I did get to a
build (re: the recent GLEW posts, that was a problem for me also).

The project screen loaded fine and displays the fonts very nicely...
however, pcbnew fails (either directly or via project window) with a DRI
failed to authenticate message. Having looked around, I think this could
be because I'm using the nVidia driver for my GTX1060 GPU which doesn't
play nice with DRI. However, the officially-compiled kicad versions
(including nightly) work fine in that regard, so I'm not sure what is
happening there.

So, this is a long post to say:

     Please incorporate wx 3.1 into the Linux build, as you have for the
Win and Mac builds, because wx 3.0 is broken.

Also, it would be good to know (if it is known) what happened with DRI 2.

Ruth


___
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


--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/


___
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] Experience compiling latest HEAD

[Ruth Ivimey-Cook]

I have v5.1 from http://ppa.launchpad.net/kicad/kicad-5.1-releases/ubuntu/

And the kicad built nightly v5.99 from 
http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu/


And it's v5.99 I was asking to include wx 3.1.

Ruth


On 28/06/2021 16:53, Wayne Stambaugh wrote:

Which version of KiCad are you talking about, 5.1 or master?  Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA?  The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.

On 6/28/21 11:38 AM, Ruth Ivimey-Cook wrote:

Folks,

I'm using Kicad on Kubuntu 21.04 with a 4K screen, and experience the
'tiny fonts' problem on it. I got fed up with that a few days ago and
noticed the recommendations that wxWin 3.1 fixes many issues. I first
tried to install the 'flatpak' build, but couldn't do so, so then I
compiled it from scratch. It took a little while but I did get to a
build (re: the recent GLEW posts, that was a problem for me also).

The project screen loaded fine and displays the fonts very nicely...
however, pcbnew fails (either directly or via project window) with a DRI
failed to authenticate message. Having looked around, I think this could
be because I'm using the nVidia driver for my GTX1060 GPU which doesn't
play nice with DRI. However, the officially-compiled kicad versions
(including nightly) work fine in that regard, so I'm not sure what is
happening there.

So, this is a long post to say:

     Please incorporate wx 3.1 into the Linux build, as you have for the
Win and Mac builds, because wx 3.0 is broken.

Also, it would be good to know (if it is known) what happened with DRI 2.

Ruth


___
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


--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/


___
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] Experiences/feedback with 'nightly'

[Ruth Ivimey-Cook]

I've been using the nightly build for the last couple of weeks on a 
hobby project, with generally good results. I thought it might be 
helpful for you some feedback on it. My comparisons are against 5.1.14:


I love the new cut/paste, click to move etc. Very much easier. I love 
too the Schematic's 'edit endpoint' on a wire to extend it, but couldn't 
it support general movement too, as is true for 'd' on the PCB?


I like the new part Group and part Lock options, and the dialog for lock 
override. Have I missed finding a general Unlock All, though?


The router tool to drag whole parts with their tracks (opt 'd') gets 
very easily confused with conflicts on tracks that shouldn't be there 
and for any many-pin part it's almost unusable. I didn't notice the same 
problems in v5.1. By 'shouldn't be there' I think there is a conflict is 
with THT pads where the hole itself becomes something to avoid. You can 
also conflict with existing track segments which should and can move and 
are at least 1 segment distant from the part being moved (e.g. part has 
pad A, which has a track segment on it B, which then bends at 45deg to a 
segment C. Moving the part moves A and B, but not C, which could move 
but is instead counted as a conflict. Where the part movement is in line 
with tracks, things are generally ok; problems arise when part movement 
is at an angle to track connections.


A nice enhancement would be for PCB drag to support dragging of 
contiguous groups of parts (e.g. when you use an area selection).


The 3D viewer is great as always. I'm not sure if this is a regression, 
but when the solder resist layer (green etc) is not clipped at pcb 
holes, e.g. mounting holes, and should be, so currently you can't see 
all the way through holes. Switch off display of solder resist and you 
can. You also can't see through THT part holes when components are not 
shown.


The new library format was obviously needed and makes more sense 
(internals-wise). However, integration with older libraries needs 
improvement, specifically there needs to be a way to auto import 
specific symbols to an existing new-format library (e.g. 
project-specific) from an old-format library (or if present this option 
is not obvious), and ideally a way to export an new format symbol to an 
old format (even if that is then marked as potentially broken and needs 
checking). At present it is not practical for everyone to be on the new 
format all the time. Migration old->new was good when that was appropriate.


The new project viewer tool layout is improved, but could the clickable 
area for each tool encompass the text as well as the image? Perhaps also 
the icons could be somewhat larger.


I was slightly confused, when setting up my board, that I wasn't allowed 
to specify a single sided board... there is no option for just one layer 
of copper. It so happens that my project grew and I do need 2 layers, 
but still.


My project has so far had a major revision, as I reimplemented the core 
of the circuit, and in the process reset the part numbering. Of course 
there was a fair bit of movement and redoing of pcb placement but some 
non-core parts stayed put. I was hoping/expecting the areas that hadn't 
been changed would either show up with lots of broken connections or be 
retained as-is, but no. For parts that were renumbered  but not moved on 
the pcb, the track was left with its original net, while the part's 
connections were those of the new one. (e.g. old part R1 pad1 = 3V3 and 
has track 3V3, following change now R1 pad1 is GND. After change, R1 
still refers to the same footprint so pad1 is now GND but track is still 
3V3, and yet the ratsnest showed nothing wrong). NB Rule checker dialog 
not invoked, just the ratsnest.


Hope this helps,

Ruth


--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/


___
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] Experience compiling latest HEAD

[Wayne Stambaugh]

Which version of KiCad are you talking about, 5.1 or master?  Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA?  The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.

On 6/28/21 11:38 AM, Ruth Ivimey-Cook wrote:
> Folks,
> 
> I'm using Kicad on Kubuntu 21.04 with a 4K screen, and experience the
> 'tiny fonts' problem on it. I got fed up with that a few days ago and
> noticed the recommendations that wxWin 3.1 fixes many issues. I first
> tried to install the 'flatpak' build, but couldn't do so, so then I
> compiled it from scratch. It took a little while but I did get to a
> build (re: the recent GLEW posts, that was a problem for me also).
> 
> The project screen loaded fine and displays the fonts very nicely...
> however, pcbnew fails (either directly or via project window) with a DRI
> failed to authenticate message. Having looked around, I think this could
> be because I'm using the nVidia driver for my GTX1060 GPU which doesn't
> play nice with DRI. However, the officially-compiled kicad versions
> (including nightly) work fine in that regard, so I'm not sure what is
> happening there.
> 
> So, this is a long post to say:
> 
>     Please incorporate wx 3.1 into the Linux build, as you have for the
> Win and Mac builds, because wx 3.0 is broken.
> 
> Also, it would be good to know (if it is known) what happened with DRI 2.
> 
> Ruth
> 

___
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Wayne Stambaugh]

Good catch.  I missed that when I made the change.  I will fix the
message when I get a chance.  I would prefer not to use a dialog.  Maybe
adding a warning to update the schematic to the message panel would be a
less intrusive.  The other option would be an info bar.

On 6/28/21 11:32 AM, Brian Piccioni wrote:
> Ah.
> 
> Perhaps it would be useful to throw up a dialog to the effect that that
> the schematic should be updated?
> 
> It still says
> 
> PCB and schematic successfully reannotated
> 
> In the dialog.
> 
> 
> On 2021-06-28 11:29 a.m., Wayne Stambaugh wrote:
>> The reannotation dialog update schematic option because it was removed
>> because it could leave schematics in an undefined state under certain
>> conditions.  See commit 54e18f6b1f4c2199f8748fff82198f86522bef83 and the
>> related issue for details.
>>
>> Wayne
>>
>> On 6/28/21 9:51 AM, Brian Piccioni wrote:
>>> Hello
>>>
>>> I have observed that Geographical Reannotation (my contribution) no
>>> longer seems to update the schematic. Manual "Update Schematic from PCB"
>>> seems to work so I assume there has been a modification to the Kiway
>>> commands. In order to track this down I need to set up build on msys2.
>>>
>>> I have followed the instructions at
>>> https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to
>>>
>>> pacman -S cmake
>>> pacman -S gcc.
>>>
>>> cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)
>>>
>>> Glew is installed as per the instructions.
>>>
>>> Any suggestions?
>>>
>>> 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
>> ___
>> 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

[Kicad-developers] Experience compiling latest HEAD

[Ruth Ivimey-Cook]

Folks,

I'm using Kicad on Kubuntu 21.04 with a 4K screen, and experience the 
'tiny fonts' problem on it. I got fed up with that a few days ago and 
noticed the recommendations that wxWin 3.1 fixes many issues. I first 
tried to install the 'flatpak' build, but couldn't do so, so then I 
compiled it from scratch. It took a little while but I did get to a 
build (re: the recent GLEW posts, that was a problem for me also).


The project screen loaded fine and displays the fonts very nicely... 
however, pcbnew fails (either directly or via project window) with a DRI 
failed to authenticate message. Having looked around, I think this could 
be because I'm using the nVidia driver for my GTX1060 GPU which doesn't 
play nice with DRI. However, the officially-compiled kicad versions 
(including nightly) work fine in that regard, so I'm not sure what is 
happening there.


So, this is a long post to say:

    Please incorporate wx 3.1 into the Linux build, as you have for the 
Win and Mac builds, because wx 3.0 is broken.


Also, it would be good to know (if it is known) what happened with DRI 2.

Ruth

--
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/


___
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Brian Piccioni]

Ah.

Perhaps it would be useful to throw up a dialog to the effect that that 
the schematic should be updated?


It still says

PCB and schematic successfully reannotated

In the dialog.


On 2021-06-28 11:29 a.m., Wayne Stambaugh wrote:

The reannotation dialog update schematic option because it was removed
because it could leave schematics in an undefined state under certain
conditions.  See commit 54e18f6b1f4c2199f8748fff82198f86522bef83 and the
related issue for details.

Wayne

On 6/28/21 9:51 AM, Brian Piccioni wrote:

Hello

I have observed that Geographical Reannotation (my contribution) no
longer seems to update the schematic. Manual "Update Schematic from PCB"
seems to work so I assume there has been a modification to the Kiway
commands. In order to track this down I need to set up build on msys2.

I have followed the instructions at
https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to

pacman -S cmake
pacman -S gcc.

cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)

Glew is installed as per the instructions.

Any suggestions?

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

___
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Wayne Stambaugh]

The reannotation dialog update schematic option because it was removed
because it could leave schematics in an undefined state under certain
conditions.  See commit 54e18f6b1f4c2199f8748fff82198f86522bef83 and the
related issue for details.

Wayne

On 6/28/21 9:51 AM, Brian Piccioni wrote:
> Hello
> 
> I have observed that Geographical Reannotation (my contribution) no
> longer seems to update the schematic. Manual "Update Schematic from PCB"
> seems to work so I assume there has been a modification to the Kiway
> commands. In order to track this down I need to set up build on msys2.
> 
> I have followed the instructions at
> https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to
> 
> pacman -S cmake
> pacman -S gcc.
> 
> cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)
> 
> Glew is installed as per the instructions.
> 
> Any suggestions?
> 
> 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

___
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Nick Østergaard]

Yeah, it appears they ship wxwidgets as 3.0 and wxmsw as 3.1. The guide
should probably be updsted for that dependency.

And I think the wxpython matches wxmsw 3.1, which should be compatible with
python3. I have not tested that.

man. 28. jun. 2021 17.18 skrev Brian Piccioni :

> That was probably it!
>
> I get much farther now. It stopped at
>
> CMake Error at
> C:/msys64/mingw64/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:230
> (message):
>   Could NOT find wxWidgets: Found unsuitable version "3.0.5", but required
> is
>   at least "3.1.5" (found
>
> -LC:/msys64/mingw64/lib;;;-pipe;-Wl,--dynamicbase,--high-entropy-va,--nxcompat,--default-image-base-high;-Wl,--subsystem,windows;-mwindows;-lwx_mswu_gl-3.0;-lwx_mswu_aui-3.0;-lwx_mswu_adv-3.0;-lwx_mswu_html-3.0;-lwx_mswu_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_mswu_propgrid-3.0;-lwx_baseu_xml-3.0;-lwx_mswu_stc-3.0)
>
> Because it found 3.0.5 (even though 3.1.5 was installed) so I ran
>
>  pacman -R mingw-w64-x86_64-wxWidgets
>
> and it went through.
>
>
> Thanks everybody!
>
>
>
> On 2021-06-28 11:00 a.m., Nick Østergaard wrote:
>
> Brian,  think that is because you started the msys shell instead of one of
> the mingw64 one.
>
> On Mon, 28 Jun 2021 at 16:46, jp charras  wrote:
>
>>
>> Le 28/06/2021 à 16:14, Brian Piccioni a écrit :
>> > JP
>> >
>> > Thanks for the quick reply
>> >
>> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
>> > $ find /mingw64/ -name *glew*
>> > /mingw64/bin/glew32.dll
>> > /mingw64/bin/glewinfo.exe
>> > /mingw64/bin/libvtkglew-8.2.dll
>> > /mingw64/include/GL/glew.h
>> > /mingw64/include/GL/wglew.h
>> > /mingw64/include/OGRE/RenderSystems/GL/GL/glew.h
>> > /mingw64/include/OGRE/RenderSystems/GL/GL/wglew.h
>> > /mingw64/include/vtk-8.2/vtkglew
>> > /mingw64/include/vtk-8.2/vtkglew/include/GL/glew.h
>> > /mingw64/include/vtk-8.2/vtkglew/include/GL/vtk_glew_mangle.h
>> > /mingw64/include/vtk-8.2/vtkglew/include/GL/wglew.h
>> > /mingw64/include/vtk-8.2/vtk_glew.h
>> > /mingw64/lib/cmake/glew
>> > /mingw64/lib/cmake/glew/glew-config.cmake
>> > /mingw64/lib/cmake/glew/glew-targets-release.cmake
>> > /mingw64/lib/cmake/glew/glew-targets.cmake
>> > /mingw64/lib/cmake/vtk-8.2/Modules/vtkglew.cmake
>> > /mingw64/lib/libglew32.a
>> > /mingw64/lib/libglew32.dll.a
>> > /mingw64/lib/libvtkglew-8.2.dll.a
>> > /mingw64/lib/pkgconfig/glew.pc
>> > /mingw64/share/licenses/glew
>> >
>> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
>> > $ pacman -Ss glew
>> > mingw32/mingw-w64-i686-glew 2.2.0-2
>> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
>> > mingw64/mingw-w64-x86_64-glew 2.2.0-2 [installed]
>> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
>> > ucrt64/mingw-w64-ucrt-x86_64-glew 2.2.0-2
>> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
>> > clang64/mingw-w64-clang-x86_64-glew 2.2.0-2
>> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
>> >
>> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
>> >
>> >
>>
>> This is similar to what I see on my computer (but I have less files).
>>
>> GLEW_LIBRARY should be found by cmake.
>>
>> You can try the brute force (that helped me in some cases):
>>
>> invoke cmake with the option:
>>
>> -DGLEW_LIBRARY=/d/mingw/mingw64/lib
>>
>> (expecting your mingw path is /d/mingw) to force the GLEW_LIBRARY path.
>>
>>
>> --
>> Jean-Pierre CHARRAS
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Brian Piccioni]

That was probably it!

I get much farther now. It stopped at

CMake Error at 
C:/msys64/mingw64/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:230 
(message):
  Could NOT find wxWidgets: Found unsuitable version "3.0.5", but 
required is

  at least "3.1.5" (found
-LC:/msys64/mingw64/lib;;;-pipe;-Wl,--dynamicbase,--high-entropy-va,--nxcompat,--default-image-base-high;-Wl,--subsystem,windows;-mwindows;-lwx_mswu_gl-3.0;-lwx_mswu_aui-3.0;-lwx_mswu_adv-3.0;-lwx_mswu_html-3.0;-lwx_mswu_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_mswu_propgrid-3.0;-lwx_baseu_xml-3.0;-lwx_mswu_stc-3.0)

Because it found 3.0.5 (even though 3.1.5 was installed) so I ran

 pacman -R mingw-w64-x86_64-wxWidgets

and it went through.


Thanks everybody!



On 2021-06-28 11:00 a.m., Nick Østergaard wrote:
Brian,  think that is because you started the msys shell instead of 
one of the mingw64 one.


On Mon, 28 Jun 2021 at 16:46, jp charras > wrote:



Le 28/06/2021 à 16:14, Brian Piccioni a écrit :
> JP
>
> Thanks for the quick reply
>
> bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
> $ find /mingw64/ -name *glew*
> /mingw64/bin/glew32.dll
> /mingw64/bin/glewinfo.exe
> /mingw64/bin/libvtkglew-8.2.dll
> /mingw64/include/GL/glew.h
> /mingw64/include/GL/wglew.h
> /mingw64/include/OGRE/RenderSystems/GL/GL/glew.h
> /mingw64/include/OGRE/RenderSystems/GL/GL/wglew.h
> /mingw64/include/vtk-8.2/vtkglew
> /mingw64/include/vtk-8.2/vtkglew/include/GL/glew.h
> /mingw64/include/vtk-8.2/vtkglew/include/GL/vtk_glew_mangle.h
> /mingw64/include/vtk-8.2/vtkglew/include/GL/wglew.h
> /mingw64/include/vtk-8.2/vtk_glew.h
> /mingw64/lib/cmake/glew
> /mingw64/lib/cmake/glew/glew-config.cmake
> /mingw64/lib/cmake/glew/glew-targets-release.cmake
> /mingw64/lib/cmake/glew/glew-targets.cmake
> /mingw64/lib/cmake/vtk-8.2/Modules/vtkglew.cmake
> /mingw64/lib/libglew32.a
> /mingw64/lib/libglew32.dll.a
> /mingw64/lib/libvtkglew-8.2.dll.a
> /mingw64/lib/pkgconfig/glew.pc
> /mingw64/share/licenses/glew
>
> bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
> $ pacman -Ss glew
> mingw32/mingw-w64-i686-glew 2.2.0-2
>     GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> mingw64/mingw-w64-x86_64-glew 2.2.0-2 [installed]
>     GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> ucrt64/mingw-w64-ucrt-x86_64-glew 2.2.0-2
>     GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> clang64/mingw-w64-clang-x86_64-glew 2.2.0-2
>     GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
>
> bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
>
>

This is similar to what I see on my computer (but I have less files).

GLEW_LIBRARY should be found by cmake.

You can try the brute force (that helped me in some cases):

invoke cmake with the option:

-DGLEW_LIBRARY=/d/mingw/mingw64/lib

(expecting your mingw path is /d/mingw) to force the GLEW_LIBRARY
path.


-- 
Jean-Pierre CHARRAS



___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Nick Østergaard]

Brian,  think that is because you started the msys shell instead of one of
the mingw64 one.

On Mon, 28 Jun 2021 at 16:46, jp charras  wrote:

>
> Le 28/06/2021 à 16:14, Brian Piccioni a écrit :
> > JP
> >
> > Thanks for the quick reply
> >
> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
> > $ find /mingw64/ -name *glew*
> > /mingw64/bin/glew32.dll
> > /mingw64/bin/glewinfo.exe
> > /mingw64/bin/libvtkglew-8.2.dll
> > /mingw64/include/GL/glew.h
> > /mingw64/include/GL/wglew.h
> > /mingw64/include/OGRE/RenderSystems/GL/GL/glew.h
> > /mingw64/include/OGRE/RenderSystems/GL/GL/wglew.h
> > /mingw64/include/vtk-8.2/vtkglew
> > /mingw64/include/vtk-8.2/vtkglew/include/GL/glew.h
> > /mingw64/include/vtk-8.2/vtkglew/include/GL/vtk_glew_mangle.h
> > /mingw64/include/vtk-8.2/vtkglew/include/GL/wglew.h
> > /mingw64/include/vtk-8.2/vtk_glew.h
> > /mingw64/lib/cmake/glew
> > /mingw64/lib/cmake/glew/glew-config.cmake
> > /mingw64/lib/cmake/glew/glew-targets-release.cmake
> > /mingw64/lib/cmake/glew/glew-targets.cmake
> > /mingw64/lib/cmake/vtk-8.2/Modules/vtkglew.cmake
> > /mingw64/lib/libglew32.a
> > /mingw64/lib/libglew32.dll.a
> > /mingw64/lib/libvtkglew-8.2.dll.a
> > /mingw64/lib/pkgconfig/glew.pc
> > /mingw64/share/licenses/glew
> >
> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
> > $ pacman -Ss glew
> > mingw32/mingw-w64-i686-glew 2.2.0-2
> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> > mingw64/mingw-w64-x86_64-glew 2.2.0-2 [installed]
> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> > ucrt64/mingw-w64-ucrt-x86_64-glew 2.2.0-2
> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> > clang64/mingw-w64-clang-x86_64-glew 2.2.0-2
> > GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
> >
> > bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
> >
> >
>
> This is similar to what I see on my computer (but I have less files).
>
> GLEW_LIBRARY should be found by cmake.
>
> You can try the brute force (that helped me in some cases):
>
> invoke cmake with the option:
>
> -DGLEW_LIBRARY=/d/mingw/mingw64/lib
>
> (expecting your mingw path is /d/mingw) to force the GLEW_LIBRARY path.
>
>
> --
> 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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[jp charras]

Le 28/06/2021 à 16:14, Brian Piccioni a écrit :

JP

Thanks for the quick reply

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
$ find /mingw64/ -name *glew*
/mingw64/bin/glew32.dll
/mingw64/bin/glewinfo.exe
/mingw64/bin/libvtkglew-8.2.dll
/mingw64/include/GL/glew.h
/mingw64/include/GL/wglew.h
/mingw64/include/OGRE/RenderSystems/GL/GL/glew.h
/mingw64/include/OGRE/RenderSystems/GL/GL/wglew.h
/mingw64/include/vtk-8.2/vtkglew
/mingw64/include/vtk-8.2/vtkglew/include/GL/glew.h
/mingw64/include/vtk-8.2/vtkglew/include/GL/vtk_glew_mangle.h
/mingw64/include/vtk-8.2/vtkglew/include/GL/wglew.h
/mingw64/include/vtk-8.2/vtk_glew.h
/mingw64/lib/cmake/glew
/mingw64/lib/cmake/glew/glew-config.cmake
/mingw64/lib/cmake/glew/glew-targets-release.cmake
/mingw64/lib/cmake/glew/glew-targets.cmake
/mingw64/lib/cmake/vtk-8.2/Modules/vtkglew.cmake
/mingw64/lib/libglew32.a
/mingw64/lib/libglew32.dll.a
/mingw64/lib/libvtkglew-8.2.dll.a
/mingw64/lib/pkgconfig/glew.pc
/mingw64/share/licenses/glew

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
$ pacman -Ss glew
mingw32/mingw-w64-i686-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
mingw64/mingw-w64-x86_64-glew 2.2.0-2 [installed]
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
ucrt64/mingw-w64-ucrt-x86_64-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
clang64/mingw-w64-clang-x86_64-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~




This is similar to what I see on my computer (but I have less files).

GLEW_LIBRARY should be found by cmake.

You can try the brute force (that helped me in some cases):

invoke cmake with the option:

-DGLEW_LIBRARY=/d/mingw/mingw64/lib

(expecting your mingw path is /d/mingw) to force the GLEW_LIBRARY path.


--
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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Brian Piccioni]

JP

Thanks for the quick reply

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
$ find /mingw64/ -name *glew*
/mingw64/bin/glew32.dll
/mingw64/bin/glewinfo.exe
/mingw64/bin/libvtkglew-8.2.dll
/mingw64/include/GL/glew.h
/mingw64/include/GL/wglew.h
/mingw64/include/OGRE/RenderSystems/GL/GL/glew.h
/mingw64/include/OGRE/RenderSystems/GL/GL/wglew.h
/mingw64/include/vtk-8.2/vtkglew
/mingw64/include/vtk-8.2/vtkglew/include/GL/glew.h
/mingw64/include/vtk-8.2/vtkglew/include/GL/vtk_glew_mangle.h
/mingw64/include/vtk-8.2/vtkglew/include/GL/wglew.h
/mingw64/include/vtk-8.2/vtk_glew.h
/mingw64/lib/cmake/glew
/mingw64/lib/cmake/glew/glew-config.cmake
/mingw64/lib/cmake/glew/glew-targets-release.cmake
/mingw64/lib/cmake/glew/glew-targets.cmake
/mingw64/lib/cmake/vtk-8.2/Modules/vtkglew.cmake
/mingw64/lib/libglew32.a
/mingw64/lib/libglew32.dll.a
/mingw64/lib/libvtkglew-8.2.dll.a
/mingw64/lib/pkgconfig/glew.pc
/mingw64/share/licenses/glew

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~
$ pacman -Ss glew
mingw32/mingw-w64-i686-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
mingw64/mingw-w64-x86_64-glew 2.2.0-2 [installed]
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
ucrt64/mingw-w64-ucrt-x86_64-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)
clang64/mingw-w64-clang-x86_64-glew 2.2.0-2
    GLEW, The OpenGL Extension Wrangler Library (mingw-w64)

bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~

On 2021-06-28 10:10 a.m., jp charras wrote:


Le 28/06/2021 à 15:51, Brian Piccioni a écrit :

Hello

I have observed that Geographical Reannotation (my contribution) no 
longer seems to update the schematic. Manual "Update Schematic from 
PCB" seems to work so I assume there has been a modification to the 
Kiway commands. In order to track this down I need to set up build on 
msys2.


I have followed the instructions at 
https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to


pacman -S cmake
pacman -S gcc.

cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)

Glew is installed as per the instructions.

Any suggestions?

Brian


What the command "find /mingw64/ -name *glew*" find?

What the command "pacman -Ss glew" says.



--


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] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[jp charras]

Le 28/06/2021 à 15:51, Brian Piccioni a écrit :

Hello

I have observed that Geographical Reannotation (my contribution) no 
longer seems to update the schematic. Manual "Update Schematic from 
PCB" seems to work so I assume there has been a modification to the 
Kiway commands. In order to track this down I need to set up build on 
msys2.


I have followed the instructions at 
https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to


pacman -S cmake
pacman -S gcc.

cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)

Glew is installed as per the instructions.

Any suggestions?

Brian


What the command "find /mingw64/ -name *glew*" find?

What the command "pacman -Ss glew" says.



--


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

[Kicad-developers] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

[Brian Piccioni]

Hello

I have observed that Geographical Reannotation (my contribution) no 
longer seems to update the schematic. Manual "Update Schematic from PCB" 
seems to work so I assume there has been a modification to the Kiway 
commands. In order to track this down I need to set up build on msys2.


I have followed the instructions at 
https://dev-docs.kicad.org/en/build/windows-msys2/. In addition I had to


pacman -S cmake
pacman -S gcc.

cmake fails with Could NOT find GLEW (missing: GLEW_LIBRARY)

Glew is installed as per the instructions.

Any suggestions?

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