Oops, forgot to include the list.
Hi Seth,
Thanks for replying so quickly. I hate to ask such a hand-holding
question, but I'm also very reluctant to break my brand-new Debian
installation (I'm rebuilding because my prior installation just became
extremely broken over some time of hacking packages together to satisfy
various build environments).
So, the glm headers certainly exist at the following path: /usr/include/glm
...but if I enable tracing on the FindGLM.cmake script included with the
KiCad source, it appears it's trying to find it in /usr/local/include.
I know this is a stupid question that I should already know the answer to,
but why is cmake looking in /usr/local/include and apparently not in
/usr/include? How do I fix that?
Humble thanks,
-Brian
On Mon, Jun 1, 2020 at 11:24 AM Seth Hillbrand wrote:
> Hello Brian
>
> GLM is only a header, so it is missing in the paths that your build is
> looking for it.
>
> This is not a KiCad issue (I build using Debian stable). You can
> re-install GLM and check that there is not another header on your system
> that is named the same.
>
> -S
>
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603 9372
>
> On 2020-06-01 07:44, Brian Henning wrote:
>
> > Comrades,
> >
> > I am in the process of rebuilding my main desktop system, and trying to
> > get my KiCAD build environment back together. I've run into a very
> > early snag, in the form of CMake being unable to find the GLM package:
> >
> > $ cmake -DCMAKE_BUILD_TYPE=Release ../..
> > -- KICAD_SCRIPTING is OFF: Disabling all python scripting support
> > -- KiCad install dir:
> > -- Check for installed GLEW -- found
> > CMake Error at
> > /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137
> > (message):
> > Could NOT find GLM (missing: GLM_VERSION) (Required is at least version
> > "0.9.5.1")
> >
> > However, libglm-dev is installed, at version 0.9.9.3:
> >
> > $ apt list libglm-dev
> > Listing... Done
> > libglm-dev/stable,now 0.9.9.3-2 all [installed]
> >
> > I am knowingly not quite right at the bleeding edge of the KiCAD 6
> > source tree, as Wayne has mentioned he is pushing some of the changes
> > involving removing the support for saving legacy schematic symbols, and
> > my ODBC fork still depends on that; I'm not quite ready to take on
> > whatever challenges might be involved in updating my fork to use the
> > new s-expr symbol code.
> >
> > Anyway, all of that as a preface to this question: IS THIS A KNOWN
> > ISSUE WITH A FIX ALREADY?
> >
> > Any advice on how to correct this? What additional information do I
> > need to provide to shed light on the situation?
> >
> > The system is Debian 10 (stable). Missing packages are almost a
> > certainty as I'm rebuilding.
> >
> > Many 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
>
___
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