Tomasz, you’re awesome!! :)
and good catch :)
> On 28 Jan 2016, at 17:42, Tomasz Wlostowski wrote:
>
> On 23.01.2016 23:53, Wayne Stambaugh wrote:
>>> I found the issue in Boost causing crashes on x86_64 windows builds.
Now I have no doubt why Windows
FYI, the updated msys2 boost packages have been released. I tested the
64-bit build of KiCad using the boost package version 1.60.0-2 and it
works fine. You can now safely remove the ignore boost package
statement from your pacman.conf file. I'll update the compiling kicad
doc when I get a
On 23.01.2016 23:53, Wayne Stambaugh wrote:
>> I found the issue in Boost causing crashes on x86_64 windows builds.
>> >
>> > Now I have no doubt why Windows Boost developers may have a very good
>> > reason to hate the x86 GNU assembler (well, not the tool itself but its
>> > infamous AT
On 23.01.2016 18:51, "Torsten Hüter" wrote:
> Hi Wayne,
>
> for a short term solution also an older Boost version can be used for Windows
> - or Tom's patch - it's at least not a blocker.
> I'm guessing Tom could do more productive stuff :)
>
> For the long term solution it's of course
Hi Wayne,
for a short term solution also an older Boost version can be used for Windows -
or Tom's patch - it's at least not a blocker.
I'm guessing Tom could do more productive stuff :)
For the long term solution it's of course possible to drop the coroutines
completely and use the well
On 1/23/2016 2:56 PM, Tomasz Wlostowski wrote:
> On 23.01.2016 18:51, "Torsten Hüter" wrote:
>> Hi Wayne,
>>
>> for a short term solution also an older Boost version can be used for
>> Windows - or Tom's patch - it's at least not a blocker.
>> I'm guessing Tom could do more productive stuff :)
Hi Tom,
On 21.01.2016 20:00, Tomasz Wlostowski wrote:
> Currently Kicad supports only Intel-based platforms and the patch is
> intended to make them build reliably.
Well, in Debian we ship a few more[1].
> What happens if Boost devs
> decide to change the ABI of the context library once again,
Hi,
Chris:
>> I really think that if we're going to have to support this, it should be
>> something conceptually simpler, like an emulation of coroutines using a
>> set of threads and locks.
I've tried that, but there are side effects with 3rd party libraries
(wxWidgets, OpenGL),
so that is
I've been following this thread for a few days and honestly I'm not
excited about anything proposed thus far. Tom's latest patch solves the
immediate problem of the MinGW64 build issues but creates build on other
platforms that Boost supports (although I don't know how well they are
supported).
Hm, is this really something we want to get into? Nice to remove the
dependency, but when something breaks in the future, do we have any/many
developers who can support x86 assembly code?
I really think that if we're going to have to support this, it should be
something conceptually simpler,
Hi,
This patch replaces boost::context with a small library called
libcontext (derived from boost::context sources). It drops the
dependency on boost for the cost of one additional header file and cpp
file (taking inspiration from ClipperLib).
I've tested the new context switching code on Linux,
On 21.01.2016 15:03, Chris Pavlina wrote:
> Hm, is this really something we want to get into? Nice to remove the
> dependency, but when something breaks in the future, do we have any/many
> developers who can support x86 assembly code?
>
Concerning the support: I can do that, but there is
On 21.01.2016 15:20, Lorenzo Marcantonio wrote:
> On Thu, Jan 21, 2016 at 09:03:59AM -0500, Chris Pavlina wrote:
>> Hm, is this really something we want to get into? Nice to remove
>> the dependency, but when something breaks in the future, do we
>> have any/many developers who can support x86
On Thu, Jan 21, 2016 at 09:03:59AM -0500, Chris Pavlina wrote:
> Hm, is this really something we want to get into? Nice to remove the
> dependency, but when something breaks in the future, do we have any/many
> developers who can support x86 assembly code?
boost::context is broken anyway so
On 21 January 2016 at 13:42, Tomasz Wlostowski
wrote:
> Hi,
>
> This patch replaces boost::context with a small library called
> libcontext (derived from boost::context sources). It drops the
> dependency on boost for the cost of one additional header file and cpp
>
Fair enough, and it's nice to fix the boost issue. I suppose if support
ever becomes an issue we can consider replacing it _then_.
On Thu, Jan 21, 2016 at 03:21:41PM +0100, Tomasz Wlostowski wrote:
> On 21.01.2016 15:03, Chris Pavlina wrote:
> > Hm, is this really something we want to get into?
On Thu, Jan 21, 2016 at 03:21:41PM +0100, Tomasz Wlostowski wrote:
> Have a look at the discussion between Lorenzo, Kristian and Torsten.
> Emulating coroutines with threads can only bring more problems.
Fully agree. The boost::context is more or less an ad-hoc setjmp/longjmp
so it should work as
Hi,
Am 21.01.2016 um 14:42 schrieb Tomasz Wlostowski:
> I've tested the new context switching code on Linux, OSX (El Capitan) &
> Windows (all OS 32-bit and 64-bit Intel). Supported compilers are GCC
> and Clang.
Wouldn't that kill all non-Intel platforms? IIRC there are a number of
people
On 21.01.2016 17:34, Simon Richter wrote:
> Hi,
>
> Am 21.01.2016 um 14:42 schrieb Tomasz Wlostowski:
>
>> I've tested the new context switching code on Linux, OSX (El
>> Capitan) & Windows (all OS 32-bit and 64-bit Intel). Supported
>> compilers are GCC and Clang.
>
> Wouldn't that kill all
On 21.01.2016 17:34, Simon Richter wrote:
> Hi,
>
> IIRC there are a number of
> people running KiCad on ARM based systems,
Patch for 32-bit ARM (tested on a raspberry pi) attached.
Tom
>
>Simon
>
>
>
> ___
> Mailing list:
20 matches
Mail list logo