nick, use the attached patched on kicad :3
Under vcpkg, wxwidgets is put into a unix like dependency tree meanwhile
the wxwidgets script assumes crazy prefixed distributed by wx scheme.
With this it'll at least find the right path.
If you are using VS2017, here's a sample CMakeSettings.Json
Ju
The findwxwidgets script in kicad is screwy, it can't even find wxwidgets
in msys2 if I invoke Msys2 via a secondary terminal/application (i.e. using
msys2 as a toolchain rather than shell directly).
On Mon, Mar 12, 2018 at 7:02 PM, Nick Østergaard wrote:
> I can't make cmake find wxwidgets from
I can't make cmake find wxwidgets from vcpkg. I think Thomas Figueroa also
uses vcpkg, but he built wxwidgets himself to overcome this. So I think
something is missing for wxwidgets in vcpkg, or something else is not quite
right in that corner.
2018-03-12 23:36 GMT+01:00 Mark Roszko :
> Wayne,
>
Wayne,
Long term there is good news, VCPKG exists. https://github.com/
Microsoft/vcpkg right now its separate but eventually it'll be part of VS.
(But it works now).
It's like msysbut for MSVC and it builds packages locally and puts them
in a central store. I think most of Kicad's depedenci
On 03/12/2018 04:45 PM, Simon Richter wrote:
> Hi,
>
> On 12.03.2018 16:39, Tomasz Wlostowski wrote:
>
>> Would someone be so kind to upload all build dependencies for Kicad
>> compiled for VS in a binary form?
>
> I have them as artifacts in Jenkins[1], and the runtime is also
> available on th
Hi,
On 12.03.2018 21:50, Tomasz Wlostowski wrote:
> Would you be able to provide all dependencies for Kicad MSVC builds in
> form of a zip archive (+CMake.exe)?
I've told Jenkins to pack all the artifacts together, for some reason
they ended up in the root of the download server. I'll move them
Tom,
I would prefer KiCad not be in the business of providing dependency
binaries. I can't stop anyone from providing them but I would rather
developers focus on kicad development rather than our dependencies as
much as possible. The whole point of removing all of the dependency
build code from
On 12/03/18 21:41, Simon Richter wrote:
> Hi,
>
> On 12.03.2018 19:10, Wayne Stambaugh wrote:
>
>> As long as we don't have to add msvs specific fixes to the kicad source
>> then I don't have any issues with this but I think this falls under the
>> category be careful what you wish for.
>
> Ther
Hi,
On 12.03.2018 16:39, Tomasz Wlostowski wrote:
> Would someone be so kind to upload all build dependencies for Kicad
> compiled for VS in a binary form?
I have them as artifacts in Jenkins[1], and the runtime is also
available on the download server[2].
The only thing that is missing is Pyth
Hi,
On 12.03.2018 19:10, Wayne Stambaugh wrote:
> As long as we don't have to add msvs specific fixes to the kicad source
> then I don't have any issues with this but I think this falls under the
> category be careful what you wish for.
There is one major issue for building with Visual Studio: s
On 12/03/18 19:10, Wayne Stambaugh wrote:
> The context switching build
> issue will most likely have to be fixed yet again if we choose to go
> down this path.
Wayne,
One of the things that Windows does remarkably well is binary
compatibility. We can just provide pre-built libcontext binaries (
On 3/12/2018 1:24 PM, Tomasz Wlostowski wrote:
> On 12/03/18 17:36, Wayne Stambaugh wrote:
>> No doubt I'm out of touch. :) It's been at least 10 years since I used
>> msvs. It's great that they have decided to support open source
>> development tools.
>
> Hi Wayne,
>
> I hadn't used MSVC for
Thanks for the information everyone. Maybe some day when I have a few
spare seconds and am feeling motivated, I will take a look at it.
Wayne
On 3/12/2018 12:46 PM, Jon Evans wrote:
> The free version is actually very complete for many use
> cases: https://www.visualstudio.com/vs/compare/
>
> O
On 12/03/18 17:36, Wayne Stambaugh wrote:
> No doubt I'm out of touch. :) It's been at least 10 years since I used
> msvs. It's great that they have decided to support open source
> development tools.
Hi Wayne,
I hadn't used MSVC for a while until a few months ago where I had to
develop a smal
The free version is actually very complete for many use cases:
https://www.visualstudio.com/vs/compare/
On Mon, Mar 12, 2018 at 12:36 PM, Wayne Stambaugh
wrote:
> No doubt I'm out of touch. :) It's been at least 10 years since I used
> msvs. It's great that they have decided to support open so
No doubt I'm out of touch. :) It's been at least 10 years since I used
msvs. It's great that they have decided to support open source
development tools. I'm may to to check it out when I get a chance. I'm
guessing they have a minimal free version available or have they stopped
offering that?
O
On 12/03/18 16:36, Mark Roszko wrote:
> Way out of touch now Wayne ;)
>
> VS can open CMake projects directly without generator. Also supports
> GDB.MINGWand even ships with Clang. MS even patched all their
> VC++ headers to be compatible with Clang.
Would someone be so kind to upload all
Way out of touch now Wayne ;)
VS can open CMake projects directly without generator. Also supports
GDB.MINGWand even ships with Clang. MS even patched all their VC++
headers to be compatible with Clang.
I haven't tried this yet though, but in theory it should be possible to run
MSYS2/MIN
Hi,
On 09.03.2018 15:48, Tomasz Wlostowski wrote:
> Could you help me set up a VS2015 project for building and debugging
> Kicad? Is there some tutorial?
Not really, but we have a somewhat working setup in Jenkins.
http://darine.hogyros.de:8080/view/MSVC/
has all the projects. Some of them
https://git.launchpad.net/~sjr/kicad/log/?h=msvc
2018-03-09 16:41 GMT+01:00 Nick Østergaard :
> You need to base it on Simon Richters branch.
>
> 2018-03-09 16:05 GMT+01:00 Tomasz Wlostowski :
>
>> On 09/03/18 15:55, Jon Evans wrote:
>> > One other thing that might be worth trying is to use Qt Cr
You need to base it on Simon Richters branch.
2018-03-09 16:05 GMT+01:00 Tomasz Wlostowski :
> On 09/03/18 15:55, Jon Evans wrote:
> > One other thing that might be worth trying is to use Qt Creator to
> > build/debug. It can be used as a frontend for GCC/GDB and might get
> > around your Ctrl-C
On 09/03/18 15:55, Jon Evans wrote:
> One other thing that might be worth trying is to use Qt Creator to
> build/debug. It can be used as a frontend for GCC/GDB and might get
> around your Ctrl-C issue.
Looks like a good idea, will give it a try!
Tom
It's been a really long time since I've done this but you should be able
to tell cmake to create a VS project (`cmake -G "Visual Studio 14
2015 [arch]`") and then use msvs to build. You might want to disable
python scripting, oce, and ngspice unless you feel like building msvc
variant of those
I'm going to try this just to see where I get, but I'm not an expert.
One other thing that might be worth trying is to use Qt Creator to
build/debug. It can be used as a frontend for GCC/GDB and might get around
your Ctrl-C issue.
On Fri, Mar 9, 2018 at 9:48 AM, Tomasz Wlostowski wrote:
> Dear
Dear Windows experts,
I'm desperately trying to debug a segfault in a Windows build of Kicad.
So far I've been unable to pause the program in gdb, because gdb exits
when I press Ctrl-C instead of pausing the application.
I'm fed up with this 'unix style of doing things'.
Could you help me set up
25 matches
Mail list logo