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
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
@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
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
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/
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
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
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
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?
>
>
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?
>
>
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?
>
>
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
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
>
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
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
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
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
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 :
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:
>
>
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
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.
>
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
22 matches
Mail list logo
