kicad-developers team mailing list archive

[Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx>]

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 non-Intel platforms? IIRC there are a number
> of people running KiCad on ARM based systems, and Debian will
> certainly complain if ten architectures are dropped.

Hi,

My intentions are very far from killing any platform (maybe except the
8051 ;-)

I don't mind including the rest of boost::context code in the new
library (ARM included) if somebody tests it on these platforms. It's
just a script-driven conversion, but the compiler/ABI detection code
must be written and tested. I'll try to build it for ARM and test on a
raspi as soon as I'll find some time.

Currently Kicad supports only Intel-based platforms and the patch is
intended to make them build reliably. What happens if Boost devs
decide to change the ABI of the context library once again, like they
did between 1.55 and 1.56? Should we #ifdef all our code to support
every Boost configuration on the planet?

We can't be responsible for every single build on every single
architecture and OS.

Regards,
Tom