kicad-developers team mailing list archive

[Jon Evans <jon@xxxxxxxxxxxxx>]

Hi Brian,

I will try to write a better guide, especially if I can get a full (all
options) KiCad build going rather than a minimal one.

In the meantime, I'm attaching my CMakeSettings.json from VS2019 in case
it's helpful.
It has a hard-coded toolchain path that you'll have to check/update.

I installed all the dependencies that were available in vcpkg, and then
disabled whatever was left (ngspice, OCE, and python stuff)
Then I set up that CMakeSettings and basically things work :)

By the way, I pushed my patches from my earlier email, let me know if
anyone has an issue with the change to the CMake script.

Best,
Jon

On Sun, Nov 24, 2019 at 6:56 PM Brian Piccioni <brian@xxxxxxxxxxxxxxxxxxxxx>
wrote:

> Jon
>
>
>
> Despite MSVC Community being from MS, I see some advantages in using it,
> namely that it is basically a one-package solution: no msys2, no loads of
> other tools that have to be updated, etc..
>
>
>
> My lack of cmake-foo meant I hit a roadblock when trying to build an MSVC
> recipe. One time I got so far as to have it crap out on SSL or something
> like that but now I’m stuck much earlier.
>
>
>
> In any event I’m more than happy to experiment with whatever you’ve got,
> especially if you can provide some guidance.
>
>
>
> Brian
>
>
>
> *From: *Jon Evans <jon@xxxxxxxxxxxxx>
> *Sent: *November 24, 2019 12:41 PM
> *To: *KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
> *Subject: *[Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg
> build
>
>
>
> Hi all,
>
>
>
> I got a build working using Visual Studio 2019 and vcpkg.
>
> Attached are three patches I needed to make so far.
>
> I'd appreciate some double-checking on these since cmake and wxwidgets can
> be a bit perilous.
>
>
>
> Thanks,
>
> -Jon
>
>
>

Attachment: CMakeSettings.json
Description: application/json