subject:"Re\: \[Kicad\-developers\] Building with visual studio\? looking for a tutorial."

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


Just need to resolve some link errors now

On Mon, Mar 12, 2018 at 7:02 PM, Nick Østergaard  wrote:

> 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,
>>
>> Long term there is good news, VCPKG exists. https://github.com/Mic
>> rosoft/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 depedencies are there, I
>> actually started to work on seeing if Kicad would compile with it but
>> didn't get far before being distracted.
>>
>>
>> On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh 
>> wrote:
>>
>>> 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 v4 was specifically for this reason.  The amount of time
>>> we were spending supporting this was significant.  I would prefer that
>>> the projects provide their own binary installers or we do a better job
>>> of choosing dependencies.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
>>> > 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 (as
>>> > well as binaries of every other dependency for Kicad), say, once a
>>> year,
>>> > and with a very high probability they will work on every Windows box
>>> out
>>> > there. I wouldn't worry much about libcontext, I'm more worried about
>>> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
>>> > newer MSVC versions have fixed such interoperability issues, so I hope
>>> > things will go smoothly. Simon has been running MSVC builds for a
>>> while,
>>> > so he's likely more up-to-date than me in MSVC compatibility.
>>> >
>>> > Tom
>>> >
>>>
>>> ___
>>> 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
>>>
>>
>>
>>
>> --
>> Mark
>>
>> ___
>> 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
>>
>>
>


-- 
Mark


0001-Add-exception-for-vcpkg-search-of-package.patch
Description: Binary data


CMakeSettings.json
Description: Binary data
___
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] Building with visual studio? looking for a tutorial.

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 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,
>>
>> Long term there is good news, VCPKG exists. https://github.com/Mic
>> rosoft/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 depedencies are there, I
>> actually started to work on seeing if Kicad would compile with it but
>> didn't get far before being distracted.
>>
>>
>> On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh 
>> wrote:
>>
>>> 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 v4 was specifically for this reason.  The amount of time
>>> we were spending supporting this was significant.  I would prefer that
>>> the projects provide their own binary installers or we do a better job
>>> of choosing dependencies.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
>>> > 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 (as
>>> > well as binaries of every other dependency for Kicad), say, once a
>>> year,
>>> > and with a very high probability they will work on every Windows box
>>> out
>>> > there. I wouldn't worry much about libcontext, I'm more worried about
>>> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
>>> > newer MSVC versions have fixed such interoperability issues, so I hope
>>> > things will go smoothly. Simon has been running MSVC builds for a
>>> while,
>>> > so he's likely more up-to-date than me in MSVC compatibility.
>>> >
>>> > Tom
>>> >
>>>
>>> ___
>>> 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
>>>
>>
>>
>>
>> --
>> Mark
>>
>> ___
>> 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
>>
>>
>


-- 
Mark
___
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] Building with visual studio? looking for a tutorial.

2018-03-12 Thread Nick Østergaard

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,
>
> Long term there is good news, VCPKG exists. https://github.com/Mic
> rosoft/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 depedencies are there, I
> actually started to work on seeing if Kicad would compile with it but
> didn't get far before being distracted.
>
>
> On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh 
> wrote:
>
>> 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 v4 was specifically for this reason.  The amount of time
>> we were spending supporting this was significant.  I would prefer that
>> the projects provide their own binary installers or we do a better job
>> of choosing dependencies.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
>> > 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 (as
>> > well as binaries of every other dependency for Kicad), say, once a year,
>> > and with a very high probability they will work on every Windows box out
>> > there. I wouldn't worry much about libcontext, I'm more worried about
>> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
>> > newer MSVC versions have fixed such interoperability issues, so I hope
>> > things will go smoothly. Simon has been running MSVC builds for a while,
>> > so he's likely more up-to-date than me in MSVC compatibility.
>> >
>> > Tom
>> >
>>
>> ___
>> 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
>>
>
>
>
> --
> Mark
>
> ___
> 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] Building with visual studio? looking for a tutorial.

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 depedencies are there, I
actually started to work on seeing if Kicad would compile with it but
didn't get far before being distracted.


On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh 
wrote:

> 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 v4 was specifically for this reason.  The amount of time
> we were spending supporting this was significant.  I would prefer that
> the projects provide their own binary installers or we do a better job
> of choosing dependencies.
>
> Cheers,
>
> Wayne
>
> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
> > 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 (as
> > well as binaries of every other dependency for Kicad), say, once a year,
> > and with a very high probability they will work on every Windows box out
> > there. I wouldn't worry much about libcontext, I'm more worried about
> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
> > newer MSVC versions have fixed such interoperability issues, so I hope
> > things will go smoothly. Simon has been running MSVC builds for a while,
> > so he's likely more up-to-date than me in MSVC compatibility.
> >
> > Tom
> >
>
> ___
> 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
>



-- 
Mark
___
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] Building with visual studio? looking for a tutorial.

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 the download server[2].
> 
> The only thing that is missing is Python support.

This would be a non-starter for nightly release builds.  Users expect
python scripting to be available.  For developer builds, you can do
whatever you fancy but this would have to be addressed if we wanted to
use this for nightly and release builds.

Wayne

> 
>Simon
> 
> [1] http://darine.hogyros.de:8080/view/MSVC/
> [2] http://downloads.kicad-pcb.org/windows/testing/msvc/
> 
> 
> 
> ___
> 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] Building with visual studio? looking for a tutorial.

2018-03-12 Thread Simon Richter

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 to
windows/testing/msvc later, and also add a script.

   Simon



signature.asc
Description: OpenPGP digital signature
___
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] Building with visual studio? looking for a tutorial.

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 v4 was specifically for this reason.  The amount of time
we were spending supporting this was significant.  I would prefer that
the projects provide their own binary installers or we do a better job
of choosing dependencies.

Cheers,

Wayne

On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
> 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 (as
> well as binaries of every other dependency for Kicad), say, once a year,
> and with a very high probability they will work on every Windows box out
> there. I wouldn't worry much about libcontext, I'm more worried about
> code that MSVC might not like in Kicad - but as Mark & Jon reported,
> newer MSVC versions have fixed such interoperability issues, so I hope
> things will go smoothly. Simon has been running MSVC builds for a while,
> so he's likely more up-to-date than me in MSVC compatibility.
> 
> Tom
> 

___
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] Building with visual studio? looking for a tutorial.

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.
> 
> There is one major issue for building with Visual Studio: static
> libraries are not linked elementwise, but rather, their entire symbol
> table is imported in one go, and sections pulled in as required.
> 
> This means that symbols need to be unique for the entire project, and
> overwriting symbols from static libraries (as the qa programs do) does
> not work.
> 
> I've avoided the issue by simply removing the "qa" subfolder from the
> main CMakeLists.txt, but obviously that is not a solution.
> 
>> The context switching build
>> issue will most likely have to be fixed yet again if we choose to go
>> down this path.  I do not believe current context assembly files will
>> build with msvc so we will either have to provide both sets of assembly
>> files or go back to using them from the boost which has it's own set of
>> well known build issues.
> 
> FWIW, I've backed out the relevant commits, and it builds fine with
> Boost 1.60 and 1.62. The only problematic version seems to be 1.61. If
> we wanted to go back to Boost, we could perhaps special-case 1.61 if
> there is significant demand.
> 
> The only other MSVC specific change is a workaround for a VS2015
> internal compiler error. The code in question is nonsensical anyway,
> I've replaced it with equally nonsensical code that is a bit more
> legible so it is more obvious that it is nonsensical. For those who
> care: it's the initializers for the BOX2 template, which use
> std::numeric_limits to default-initialize boxes to span the largest
> possible area. Except this doesn't work, because
> 
> using namespace std;
> cout << numeric_limits::min() << ' '
> << numeric_limits::max() << endl;
> cout << numeric_limits::min() << ' '
> << numeric_limits::max() << endl;
> 
> gives
> 
> -2147483648 2147483647
> 1.17549e-38 3.40282e+38
> 
> so the default initialization for BOX2 covers (0,0) while
> BOX2 does not. My suspicion is that this is either responsible
> for some very subtle bugs, or simply does not matter because all
> default-initialized boxes are later overwritten anyway.
> 
> Current MSVC patch stack:
> 
> Remove qa code for MSVC
> Remove own copy of FindOpenSSL.cmake
> Revert "Switched coroutine library from Boost libcotext to custom
> libcontext."
> Revert "Made libcontext compile on FreeBSD. Code formatting too."
> Revert "Preserve FPU registers on context switch"
> Revert "libcontext FreeBSD compatibility fix"
> Revert "Some coverity fixes"
> Revert "Fix an initialization order warning in coroutine.h"
> Work around VC++ 2015 bug.
> Define compiler flags for MSVC
> 
> IMO:
> 
>  - the compiler flags patch can be applied as is, it just adds a
> conditional block to CMakeLists.txt
>  - the workaround can be applied as is, or someone can look at that code
> and throw it out
>  - the context stuff needs to be decided
>  - the OpenSSL CMake script can probably be removed and the shipped
> version used, but we need to check why we had this file in the first place
>  - the QA code needs refactoring if we want to compile it with MSVC, so
> the best we can do now is disable it on MSVC.

Simon,

Would you be able to provide all dependencies for Kicad MSVC builds in
form of a zip archive (+CMake.exe)?

The goal would be to:

- unzip the dependency file
- git clone Kicad
- cd kicad
- configure.bat
- open kicad.sln with VS

Tom

___
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] Building with visual studio? looking for a tutorial.

2018-03-12 Thread Simon Richter

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 Python support.

   Simon

[1] http://darine.hogyros.de:8080/view/MSVC/
[2] http://downloads.kicad-pcb.org/windows/testing/msvc/



signature.asc
Description: OpenPGP digital signature
___
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] Building with visual studio? looking for a tutorial.

2018-03-12 Thread Simon Richter

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: static
libraries are not linked elementwise, but rather, their entire symbol
table is imported in one go, and sections pulled in as required.

This means that symbols need to be unique for the entire project, and
overwriting symbols from static libraries (as the qa programs do) does
not work.

I've avoided the issue by simply removing the "qa" subfolder from the
main CMakeLists.txt, but obviously that is not a solution.

> The context switching build
> issue will most likely have to be fixed yet again if we choose to go
> down this path.  I do not believe current context assembly files will
> build with msvc so we will either have to provide both sets of assembly
> files or go back to using them from the boost which has it's own set of
> well known build issues.

FWIW, I've backed out the relevant commits, and it builds fine with
Boost 1.60 and 1.62. The only problematic version seems to be 1.61. If
we wanted to go back to Boost, we could perhaps special-case 1.61 if
there is significant demand.

The only other MSVC specific change is a workaround for a VS2015
internal compiler error. The code in question is nonsensical anyway,
I've replaced it with equally nonsensical code that is a bit more
legible so it is more obvious that it is nonsensical. For those who
care: it's the initializers for the BOX2 template, which use
std::numeric_limits to default-initialize boxes to span the largest
possible area. Except this doesn't work, because

using namespace std;
cout << numeric_limits::min() << ' '
<< numeric_limits::max() << endl;
cout << numeric_limits::min() << ' '
<< numeric_limits::max() << endl;

gives

-2147483648 2147483647
1.17549e-38 3.40282e+38

so the default initialization for BOX2 covers (0,0) while
BOX2 does not. My suspicion is that this is either responsible
for some very subtle bugs, or simply does not matter because all
default-initialized boxes are later overwritten anyway.

Current MSVC patch stack:

Remove qa code for MSVC
Remove own copy of FindOpenSSL.cmake
Revert "Switched coroutine library from Boost libcotext to custom
libcontext."
Revert "Made libcontext compile on FreeBSD. Code formatting too."
Revert "Preserve FPU registers on context switch"
Revert "libcontext FreeBSD compatibility fix"
Revert "Some coverity fixes"
Revert "Fix an initialization order warning in coroutine.h"
Work around VC++ 2015 bug.
Define compiler flags for MSVC

IMO:

 - the compiler flags patch can be applied as is, it just adds a
conditional block to CMakeLists.txt
 - the workaround can be applied as is, or someone can look at that code
and throw it out
 - the context stuff needs to be decided
 - the OpenSSL CMake script can probably be removed and the shipped
version used, but we need to check why we had this file in the first place
 - the QA code needs refactoring if we want to compile it with MSVC, so
the best we can do now is disable it on MSVC.

   Simon

signature.asc
Description: OpenPGP digital signature
___
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] Building with visual studio? looking for a tutorial.

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 (as
well as binaries of every other dependency for Kicad), say, once a year,
and with a very high probability they will work on every Windows box out
there. I wouldn't worry much about libcontext, I'm more worried about
code that MSVC might not like in Kicad - but as Mark & Jon reported,
newer MSVC versions have fixed such interoperability issues, so I hope
things will go smoothly. Simon has been running MSVC builds for a while,
so he's likely more up-to-date than me in MSVC compatibility.

Tom

___
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] Building with visual studio? looking for a tutorial.

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 a while until a few months ago where I had to
> develop a small program for Windows. It was quite a positive change
> since the previous time (also ~10 years ago). I appreciate the nice dark
> coloured theme and greatly improved autocompletion/class browser.
> 
> Honestly, I don't care if MSVS supports Mingw or other non-MS toolchain
> or debugger. What I care about is a compiler that doesn't take ages to
> compile Kicad (for some reason MSYS's gcc is ~3 times slower than gcc
> under Linux). Same applies to CMake and a debugger that works under Windows:
> - In my case GDB and LLDB require some strange hacks (a separate
> program) to send a ctrl-c to interrupt the application being debugged.
> This hasn't been fixed since 2009 (see [1]) - so apparently nobody cares
> to make GDB a working thing under Windows.
> - Qt Creator crashes when I try to attach to running kicad process.
> - Converting DWARF-2 symbols to MS PDB format (in order to use MSVS
> debugger) using cv2pdb tool fails. Maybe due to debug symbols taking ~1
> GB in _pcbnew.kiface alone. I also can't understand why the debug info
> takes more than 100 times the size of the source code ;-).
> - IDA Pro in free version doesn't support debugging...
> 
> Since we often do favors for our Linux users (e.g. by adding workarounds
> for poor quality Linux graphics drivers), we should also be more
> welcoming to the Windows users (and programmers) - it's only 70-80% of
> our user base IIRC. Vast majority of Windows developers use MSVS. If we
> want them onboard, we must support MSVS. I'm pretty sure there are
> people willing to help with this on the mailing list.
> 
> Tom
> 
> [1]
> https://stackoverflow.com/questions/711086/in-gdb-on-mingw-how-to-make-ctrl-c-stop-the-program
> 

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.  The context switching build
issue will most likely have to be fixed yet again if we choose to go
down this path.  I do not believe current context assembly files will
build with msvc so we will either have to provide both sets of assembly
files or go back to using them from the boost which has it's own set of
well known build issues.

___
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] Building with visual studio? looking for a tutorial.

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/
> 
> 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 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?
> 
> On 3/12/2018 11:36 AM, 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.
> >
> >
> > I haven't tried this yet though, but in theory it should be possible to
> > run MSYS2/MINGW and debug via this new feature from last year that lets
> > you configure toolchains and even use gdb:
> >
> > 
> https://blogs.msdn.microsoft.com/vcblog/2017/07/19/using-mingw-and-cygwin-with-visual-cpp-and-open-folder/
> 
> 
> > 
>  
> >
> >
> > In this example it is using MSYS2.
> >
> >
> >
> > On Fri, Mar 9, 2018 at 9:54 AM, Wayne Stambaugh  
> > >> wrote:
> >
> >     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 dependencies.  You will also need a msvc
> build of boost
> >     as well for the unit test library.  I'm pretty sure Simon Richter
> >     creates msvs builds so he may have some more up to date
> information than
> >     I do.
> >
> >     Wayne
> >
> >     On 3/9/2018 9:48 AM, Tomasz Wlostowski wrote:
> >     > 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 a VS2015 project for building and
> debugging
> >     > Kicad? Is there some tutorial?
> >     >
> >     > Cheers,
> >     > Tom
> >     >
> >     >
> >     >
> >     > ___
> >     > 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
> 
> >      >
>

Re: [Kicad-developers] Building with visual studio? looking for a tutorial.

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 small program for Windows. It was quite a positive change
since the previous time (also ~10 years ago). I appreciate the nice dark
coloured theme and greatly improved autocompletion/class browser.

Honestly, I don't care if MSVS supports Mingw or other non-MS toolchain
or debugger. What I care about is a compiler that doesn't take ages to
compile Kicad (for some reason MSYS's gcc is ~3 times slower than gcc
under Linux). Same applies to CMake and a debugger that works under Windows:
- In my case GDB and LLDB require some strange hacks (a separate
program) to send a ctrl-c to interrupt the application being debugged.
This hasn't been fixed since 2009 (see [1]) - so apparently nobody cares
to make GDB a working thing under Windows.
- Qt Creator crashes when I try to attach to running kicad process.
- Converting DWARF-2 symbols to MS PDB format (in order to use MSVS
debugger) using cv2pdb tool fails. Maybe due to debug symbols taking ~1
GB in _pcbnew.kiface alone. I also can't understand why the debug info
takes more than 100 times the size of the source code ;-).
- IDA Pro in free version doesn't support debugging...

Since we often do favors for our Linux users (e.g. by adding workarounds
for poor quality Linux graphics drivers), we should also be more
welcoming to the Windows users (and programmers) - it's only 70-80% of
our user base IIRC. Vast majority of Windows developers use MSVS. If we
want them onboard, we must support MSVS. I'm pretty sure there are
people willing to help with this on the mailing list.

Tom

[1]
https://stackoverflow.com/questions/711086/in-gdb-on-mingw-how-to-make-ctrl-c-stop-the-program

___
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] Building with visual studio? looking for a tutorial.

2018-03-12 Thread Jon Evans

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 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?
>
> On 3/12/2018 11:36 AM, 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.
> >
> >
> > I haven't tried this yet though, but in theory it should be possible to
> > run MSYS2/MINGW and debug via this new feature from last year that lets
> > you configure toolchains and even use gdb:
> >
> > https://blogs.msdn.microsoft.com/vcblog/2017/07/19/using-
> mingw-and-cygwin-with-visual-cpp-and-open-folder/
> >  mingw-and-cygwin-with-visual-cpp-and-open-folder/>
> >
> > In this example it is using MSYS2.
> >
> >
> >
> > On Fri, Mar 9, 2018 at 9:54 AM, Wayne Stambaugh  > > wrote:
> >
> > 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 dependencies.  You will also need a msvc build of
> boost
> > as well for the unit test library.  I'm pretty sure Simon Richter
> > creates msvs builds so he may have some more up to date information
> than
> > I do.
> >
> > Wayne
> >
> > On 3/9/2018 9:48 AM, Tomasz Wlostowski wrote:
> > > 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 a VS2015 project for building and
> debugging
> > > Kicad? Is there some tutorial?
> > >
> > > Cheers,
> > > Tom
> > >
> > >
> > >
> > > ___
> > > 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
> > 
> >
> >
> >
> >
> > --
> > Mark
>
> ___
> 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] Building with visual studio? looking for a tutorial.

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?

On 3/12/2018 11:36 AM, 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.
> 
> 
> I haven't tried this yet though, but in theory it should be possible to
> run MSYS2/MINGW and debug via this new feature from last year that lets
> you configure toolchains and even use gdb:
> 
> https://blogs.msdn.microsoft.com/vcblog/2017/07/19/using-mingw-and-cygwin-with-visual-cpp-and-open-folder/
> 
> 
> In this example it is using MSYS2.
> 
> 
> 
> On Fri, Mar 9, 2018 at 9:54 AM, Wayne Stambaugh  > wrote:
> 
> 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 dependencies.  You will also need a msvc build of boost
> as well for the unit test library.  I'm pretty sure Simon Richter
> creates msvs builds so he may have some more up to date information than
> I do.
> 
> Wayne
> 
> On 3/9/2018 9:48 AM, Tomasz Wlostowski wrote:
> > 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 a VS2015 project for building and debugging
> > Kicad? Is there some tutorial?
> >
> > Cheers,
> > Tom
> >
> >
> >
> > ___
> > 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
> 
> 
> 
> 
> 
> -- 
> Mark

___
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] Building with visual studio? looking for a tutorial.

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 build dependencies for Kicad
compiled for VS in a binary form?

Tom


___
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] Building with visual studio? looking for a tutorial.