It uses -G "Visual Studio 15 2017" as the generator.
On Sun, 1 Dec 2019 at 23:45, Jon Evans wrote:
>
> What environment does that build use? My patches were necessary for VS2019
> using default compiler settings
>
> On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote:
>>
>> Oh, ok. Then I wonder w
What environment does that build use? My patches were necessary for VS2019
using default compiler settings
On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote:
> Oh, ok. Then I wonder why Jon needed to patch it.
>
> On Sun, 1 Dec 2019 at 20:14, Simon Richter
> wrote:
> >
> > Hi Nick,
> >
> > On 01
Oh, ok. Then I wonder why Jon needed to patch it.
On Sun, 1 Dec 2019 at 20:14, Simon Richter wrote:
>
> Hi Nick,
>
> On 01.12.19 20:07, Nick Østergaard wrote:
>
> > OK, cool, it looks like the msvc builds on jenkins are back in green again
> > :)
>
> > https://jenkins.simonrichter.eu/job/windows
Hi Nick,
On 01.12.19 20:07, Nick Østergaard wrote:
> OK, cool, it looks like the msvc builds on jenkins are back in green again :)
> https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
They were broken at the same time as the Linux builds :)
Simon
signature.asc
Description: Open
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
>> Sent: November 24,
Jon Thanks so much! I am busy working with Alexander on renumbering so it may take me a few days to see if I can get it to work. Brian From: Jon EvansSent: November 29, 2019 9:19 PMTo: Brian PiccioniCc: KiCad DevelopersSubject: Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build
py to experiment with whatever you’ve got,
> especially if you can provide some guidance.
>
>
>
> Brian
>
>
>
> *From: *Jon Evans
> *Sent: *November 24, 2019 12:41 PM
> *To: *KiCad Developers
> *Subject: *[Kicad-developers] [PATCH] Fixes for Visual S
-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
I have not tried to get those working yet, I have them disabled by flags.
I can try to see what was involved in adding new packages.
-Jon
On Sun, Nov 24, 2019 at 5:17 PM Wayne Stambaugh
wrote:
> Hey Jon,
>
> I was playing around with vcpkg a couple of weeks ago and it's works
> surprisingly wel
Once all of the dependencies for vcpkg are in place, I could see
actually using VS for development (I can't beleive I'm actually typing
this) on windows. Who knew?
On 11/24/19 5:23 PM, Ian McInerney wrote:
> I think it is still missing the OCC/OCE package as well:
> https://github.com/microsoft/v
I think it is still missing the OCC/OCE package as well:
https://github.com/microsoft/vcpkg/issues/4968
-Ian
On Sun, 24 Nov 2019, 22:17 Wayne Stambaugh, wrote:
> Hey Jon,
>
> I was playing around with vcpkg a couple of weeks ago and it's works
> surprisingly well. There is finally a sane way t
Hey Jon,
I was playing around with vcpkg a couple of weeks ago and it's works
surprisingly well. There is finally a sane way to build dependencies
and compile and link against them on windows. The dependencies I could
not find in vcpkg are ngspice and wxPhoenix/wxWidgets which means that
we coul
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
From 87674cb5a87b4d77683248b65994ef625f8a7c47 Mon Sep 17 00:00:00 2001
F
13 matches
Mail list logo
