Re: [Kicad-developers] Windows builds broken

2019-05-07 Thread Wayne Stambaugh
Nick, Thanks, that did the trick. I guess I need to update the build documentation. Wayne On 5/1/2019 5:05 PM, Nick Østergaard wrote: > Maybe it will be fixed in the next release of cmake > https://gitlab.kitware.com/cmake/cmake/merge_requests/2747 > Found via

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Nick Østergaard
Maybe it will be fixed in the next release of cmake https://gitlab.kitware.com/cmake/cmake/merge_requests/2747 Found via https://gitlab.kitware.com/cmake/cmake/issues/18865 On Wed, 1 May 2019 at 22:34, Nick Østergaard wrote: > > @Wayne, please note that I think there is a workaround. I have not

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Nick Østergaard
@Wayne, please note that I think there is a workaround. I have not tested it myself, but I guess you can configure kicad with Boost_NO_BOOST_CMAKE=ON as mention in the github issue. On Wed, 1 May 2019 at 20:33, Wayne Stambaugh wrote: > > Jeff, > > I think that was a different issue. My issue

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
Jeff, I think that was a different issue. My issue was link problem due to msys2 upgrading boost to 1.70 which apparently now uses CMake instead of the old b2 build system. It looks like the new cmake stuff is not getting the boost link libraries correct. I may take another look at it when I

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
This is odd. You are correct about PKGBUILD. Here is the contents of my /mingw32/lib/cmake folder: boost_atomic-1.70.0/ boost_chrono-1.70.0/ boost_container-1.70.0/ boost_context-1.70.0/ boost_contract-1.70.0/ boost_coroutine-1.70.0/ boost_date_time-1.70.0/ boost_exception-1.70.0/

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Nick Østergaard
I don't think so, at least when I look at the PKGBUILD it is still using bootstrap.sh and b2 to build. See: https://github.com/msys2/MINGW-packages/blob/fd550b8d48e6bc831b1e36202eaf495cba5062f8/mingw-w64-boost/PKGBUILD I don't see anything immediately alarming. Maybe the builds scripts in boost

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
On 5/1/2019 8:53 AM, John Beard wrote: > On 01/05/2019 13:36, Wayne Stambaugh wrote: >> On 5/1/2019 8:27 AM, John Beard wrote: >>> On 01/05/2019 12:53, Jeff Young wrote: Someone on the forums had to turn off the qa tests on Linux to get it to build: >> It fails during linking not

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread John Beard
On 01/05/2019 13:36, Wayne Stambaugh wrote: On 5/1/2019 8:27 AM, John Beard wrote: On 01/05/2019 12:53, Jeff Young wrote: Someone on the forums had to turn off the qa tests on Linux to get it to build: It fails during linking not compiling. I also tried clang but I get the same error. Here

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
On 5/1/2019 8:27 AM, John Beard wrote: > On 01/05/2019 12:53, Jeff Young wrote: >> Someone on the forums had to turn off the qa tests on Linux to get it >> to build: >> >> https://forum.kicad.info/t/call-for-testers-eemodern/16663/8 > This bit, right? > >

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
On 5/1/2019 8:27 AM, John Beard wrote: > On 01/05/2019 12:53, Jeff Young wrote: >> Someone on the forums had to turn off the qa tests on Linux to get it >> to build: >> >> https://forum.kicad.info/t/call-for-testers-eemodern/16663/8 > This bit, right? > >

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
On 5/1/2019 8:27 AM, John Beard wrote: > On 01/05/2019 12:53, Jeff Young wrote: >> Someone on the forums had to turn off the qa tests on Linux to get it >> to build: >> >> https://forum.kicad.info/t/call-for-testers-eemodern/16663/8 > This bit, right? > >

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread John Beard
On 01/05/2019 12:53, Jeff Young wrote: Someone on the forums had to turn off the qa tests on Linux to get it to build: https://forum.kicad.info/t/call-for-testers-eemodern/16663/8 This bit, right? .../qa/utils/kicad2step/pcb/test_base.cpp: In member function ‘void

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
Clean build fails as well. I did upgrade msys2 yesterday so maybe something is borked with msys2. On 5/1/2019 7:53 AM, Wayne Stambaugh wrote: > Hey John, > > I'll try a clean build to see if that fixes it. I rarely have to do > that. I haven't done a windows build in a while so I was a bit >

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread John Beard
On 01/05/2019 12:53, Wayne Stambaugh wrote: I'll try a clean build to see if that fixes it. I rarely have to do that. I haven't done a windows build in a while so I was a bit surprised. I've attached the build error. Hmm, have you upgraded Boost or something? IIRC, Boost 1.70 was just

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
Hey John, I'll try a clean build to see if that fixes it. I rarely have to do that. I haven't done a windows build in a while so I was a bit surprised. I've attached the build error. Wayne On 5/1/2019 7:47 AM, John Beard wrote: > Hi Wayne, > > I don't see any issues on the Jenkins Msys2

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread Jeff Young
Someone on the forums had to turn off the qa tests on Linux to get it to build: https://forum.kicad.info/t/call-for-testers-eemodern/16663/8 > On 1 May 2019, at 12:47, John Beard wrote: > > Hi Wayne, > > I don't see any issues on the Jenkins Msys2 and MSVC builds. In fact, it's > green

Re: [Kicad-developers] Windows builds broken

2019-05-01 Thread John Beard
Hi Wayne, I don't see any issues on the Jenkins Msys2 and MSVC builds. In fact, it's green across the board: https://jenkins.simonrichter.eu/view/KiCad%20Status/ What is the error? And when did it go wrong? Cheers, John On 01/05/2019 12:42, Wayne Stambaugh wrote: Anyone else having build

[Kicad-developers] Windows builds broken

2019-05-01 Thread Wayne Stambaugh
Anyone else having build issues on windows? I'm getting link errors for the qa s-expr tests on both 32 and 64 bit builds. Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] Windows Builds

2018-07-26 Thread Wayne Stambaugh
Thank you gentlemen. I appreciate the support. Wayne On 7/25/2018 2:58 PM, Adam Wolf wrote: > Nice work team! > > On Wed, Jul 25, 2018, 1:57 PM Mark Roszko > wrote: > > Appears Simon has handled it, the downloads are updated. > > I installed it and it

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Maciej Suminski
Thank you all! It was the #1 issue with the 5.0 release. Cheers, Orson On 07/25/2018 08:57 PM, Mark Roszko wrote: > Appears Simon has handled it, the downloads are updated. > > I installed it and it no longer asserts. > > On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh wrote: >> >> On

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Adam Wolf
Nice work team! On Wed, Jul 25, 2018, 1:57 PM Mark Roszko wrote: > Appears Simon has handled it, the downloads are updated. > > I installed it and it no longer asserts. > > On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh > wrote: > > > > On 7/25/2018 12:54 PM, Mark Roszko wrote: > > > *

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Mark Roszko
Appears Simon has handled it, the downloads are updated. I installed it and it no longer asserts. On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh wrote: > > On 7/25/2018 12:54 PM, Mark Roszko wrote: > > * Simon's pull request. > > > > https://github.com/KiCad/kicad-winbuilder/pull/74 > > Nick

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Wayne Stambaugh
On 7/25/2018 12:54 PM, Mark Roszko wrote: > * Simon's pull request. > > https://github.com/KiCad/kicad-winbuilder/pull/74 Nick must have given me admin permissions so I merged Simon's pull request. The new release packages should be available shortly. Do I need to do anything to make sure the

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Simon Richter
Hi, On 25.07.2018 18:18, Wayne Stambaugh wrote: > I guess we will have to wait until Nick returns from vacation to get > this resolved. I just pointed Jenkins at my fork, but that's bad style, basically. Simon signature.asc Description: OpenPGP digital signature

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Mark Roszko
* Simon's pull request. https://github.com/KiCad/kicad-winbuilder/pull/74 On Wed, Jul 25, 2018 at 12:33 PM Wayne Stambaugh wrote: > > I believe have github admin permissions at the org level. Please post > the link to Mark's pull request and I will see if I can merge it. > > On 7/25/2018 12:29

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Wayne Stambaugh
I believe have github admin permissions at the org level. Please post the link to Mark's pull request and I will see if I can merge it. On 7/25/2018 12:29 PM, Adam Wolf wrote: > Does anyone else have admin permissions at the org level? > > On Wed, Jul 25, 2018, 11:19 AM Wayne Stambaugh

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Adam Wolf
Does anyone else have admin permissions at the org level? On Wed, Jul 25, 2018, 11:19 AM Wayne Stambaugh wrote: > On 7/25/2018 11:15 AM, Mark Roszko wrote: > > @Wayne, The hold up on Windows was that Nick went on vacation > > basically the day after posting the first 5.0 build. So bad timing.>

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Wayne Stambaugh
On 7/25/2018 11:15 AM, Mark Roszko wrote: > @Wayne, The hold up on Windows was that Nick went on vacation > basically the day after posting the first 5.0 build. So bad timing.> > >> I've changed it to Release for the time being (but someone still needs to >> accept my pull request in GitHub) >

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Mark Roszko
@Wayne, The hold up on Windows was that Nick went on vacation basically the day after posting the first 5.0 build. So bad timing. >I've changed it to Release for the time being (but someone still needs to >accept my pull request in GitHub) Unforunately Nick is the only one with privs on the

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Simon Richter
Hi, On 25.07.2018 14:16, Wayne Stambaugh wrote: > We should have created a release build of the stable version. I'm fine > with nightly builds having debugging information. Stable releases > should not have debug info. These are built as RelWithDebInfo, and the debug information is stripped

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Adam Wolf
(Marek and I did pull the macOS builds, and I regenerated it as Release and got everything all fixed up on the website.) On Wed, Jul 25, 2018 at 7:31 AM Wayne Stambaugh wrote: > > We should have created a release build of the stable version. I'm fine > with nightly builds having debugging

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Wayne Stambaugh
We should have created a release build of the stable version. I'm fine with nightly builds having debugging information. Stable releases should not have debug info. On 7/25/2018 8:10 AM, Jakub Kozdon wrote: > There are probably in http://downloads.kicad-pcb.org/windows/testing/ > instead of

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Jakub Kozdon
There are probably in http://downloads.kicad-pcb.org/windows/testing/ instead of stable. Dne 25.7.2018 v 13:51 Wayne Stambaugh napsal(a): I thought we created a new windows release build to prevent the assertions. Did that not happen? On 7/25/2018 7:01 AM, Andrew Lutsenko wrote: Were the

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Wayne Stambaugh
I thought we created a new windows release build to prevent the assertions. Did that not happen? On 7/25/2018 7:01 AM, Andrew Lutsenko wrote: > Were the windows builds ever fixed?  > I downloaded 5.0 today and get a wxWidgets assert simply from clicking > on tools menu in Pcbnew. >

Re: [Kicad-developers] Windows Builds

2018-07-25 Thread Andrew Lutsenko
Were the windows builds ever fixed? I downloaded 5.0 today and get a wxWidgets assert simply from clicking on tools menu in Pcbnew. [image: kicadassert.png] ​ On Mon, Jul 23, 2018 at 6:34 AM Wayne Stambaugh wrote: > I'm fine with creating a packaging document. We could add it to the >

Re: [Kicad-developers] Windows Builds

2018-07-23 Thread Wayne Stambaugh
I'm fine with creating a packaging document. We could add it to the developers documentation or it could also be an external document with a link in the compiling doc. Wayne On 7/23/2018 8:40 AM, Adam Wolf wrote: > Agreed, Wayne. The macOS 5.0.0-1 build is uploading right now. It is a > Release

Re: [Kicad-developers] Windows Builds

2018-07-23 Thread Wayne Stambaugh
I would prefer that we create release builds (CMAKE_BUILD_TYPE=Release) for the stable releases. Debug builds are fine for nightly builds. On 7/23/2018 12:07 AM, Mark Roszko wrote: > Done. > > Wouldn't be bad if the wxAsserts were squashed :X > But then again some of them come from wx

Re: [Kicad-developers] Windows Builds

2018-07-23 Thread Rene Pöschl
On 23/07/18 05:27, Mark Roszko wrote: Is it because the installer exe is huge? That's because the footprint libraries are now part of the installers and they are absolutely massive. (4GB uncompressed) The whole repo (including git history) only has ~90MB If any libs are to blame then it will

Re: [Kicad-developers] Windows Builds

2018-07-22 Thread Mark Roszko
Done. Wouldn't be bad if the wxAsserts were squashed :X But then again some of them come from wx internally in annoying ways. On Mon, Jul 23, 2018 at 12:03 AM Adam Wolf wrote: > > Ok, this sounds bad. > > Can someone (Marek?) pull the macOS build and revert the macOS download page, > please?

Re: [Kicad-developers] Windows Builds

2018-07-22 Thread Adam Wolf
Ok, this sounds bad. Can someone (Marek?) pull the macOS build and revert the macOS download page, please? I'm running extremely low on sleep from the last two nights of KiCad hacking and I am literally in bed already. I will regenerate the macOS build with Release instead in approximately 8

Re: [Kicad-developers] Windows Builds

2018-07-22 Thread Mark Roszko
Is it because the installer exe is huge? That's because the footprint libraries are now part of the installers and they are absolutely massive. (4GB uncompressed) the installed files look fine to me though? The kiface files would be hundreds of megs themselves if they had debug symbols but they

Re: [Kicad-developers] Windows Builds

2018-07-22 Thread Seth Hillbrand
No, It's because asserts are being triggered. These are disabled (normally) in Release builds. -S Am So., 22. Juli 2018 um 20:28 Uhr schrieb Mark Roszko < mark.ros...@gmail.com>: > Is it because the installer exe is huge? > > That's because the footprint libraries are now part of the

Re: [Kicad-developers] Windows Builds

2018-07-22 Thread Mark Roszko
Welp, I poked Nick. It looks like the stable-debug build got packaged instead of the stable build config (I can reproduce the asserts). Though the executables are suspiciously not huge like they should be. On Sun, Jul 22, 2018 at 11:30 PM Seth Hillbrand wrote: > > No, It's because asserts are

[Kicad-developers] Windows Builds

2018-07-22 Thread Seth Hillbrand
​Hi Devs- I'm seeing some reports (lp:1783037) that indicate the Windows build may be compiled CMAKE_BUILD_TYPE=RelWithDebInfo instead of Release. Can anyone confirm this? Is there a reason to do this for Windows? -Seth ___ Mailing list:

Re: [Kicad-developers] Windows builds broken?

2018-04-24 Thread Maciej Sumiński
Sincere apologies. As far as I can see, Jean-Pierre has already pushed a fix. Orson On 04/24/2018 03:22 PM, Wayne Stambaugh wrote: > Is anyone else have issues with broken windows builds? I'm getting this > error after pulling the latest changes: > >

[Kicad-developers] Windows builds broken?

2018-04-24 Thread Wayne Stambaugh
Is anyone else have issues with broken windows builds? I'm getting this error after pulling the latest changes: C:/msys64/home/wstambaugh/src/kicad-trunk/common/tool/tool_manager.cpp:838:20: error: prototype for 'KIGFX::VC_SETTINGS TOOL_MANAGER::GetCurrentToolVC() const' does not match any in

Re: [Kicad-developers] Windows builds broken?

2018-04-24 Thread jp charras
Le 24/04/2018 à 15:22, Wayne Stambaugh a écrit : > Is anyone else have issues with broken windows builds? I'm getting this > error after pulling the latest changes: > Yes, me. I just committed a fix, a few minutes ago. >

Re: [Kicad-developers] Windows builds broken?

2018-04-24 Thread Wayne Stambaugh
On 4/24/2018 9:33 AM, jp charras wrote: > Le 24/04/2018 à 15:22, Wayne Stambaugh a écrit : >> Is anyone else have issues with broken windows builds? I'm getting this >> error after pulling the latest changes: >> > > Yes, me. > I just committed a fix, a few minutes ago. Thanks for the quick