kicad-developers team mailing list archive

[Simon Wells <swel024@xxxxxxxxx>]

well the patch is not designed to be default at all, just to be made
Optional for those that don't want/need it, aka its designed such that
packagers would still include it by default, but for those building
from source or they could choose not to include it if they so wished.

The number of REQUIRED packages just seems to be excessive

On Tue, Mar 29, 2016 at 8:46 PM, jp charras <jp.charras@xxxxxxxxxx> wrote:
> Le 29/03/2016 08:26, Lorenzo Marcantonio a écrit :
>> On Mon, Mar 28, 2016 at 08:07:39PM +0200, jp charras wrote:
>>> * Cairo is not always very slow and is an alternative to OpenGL canvas,
>>> which has sometimes issues.
>>
>> Cairo is *absurdly* slow without a gallium driver i.e. on all intel GPUs
>> :P I think that a better alternative to the opengl canvas is the legacy
>> one, anyway...
>
> Do not dream.
> The current wxDC canvas does not exist on wxWidgets built against GTK3.
>
> the wxDC canvas on GTK3 looks like it uses Cairo.
> (Unless something has changed in wxWidgets 3.1)
>
>
>>
>>> * It could be a good canvas for Eeschema (better than Opengl).
>>
>> Uh? please elaborate on this... why should be better than opengl for
>> eeschema? for line width consistency? (still hating opengl for that)
>
> Better antialiasing.
> But the main reason is the fact on Opengl I am easily out of memory with large boards, with 4Go of
> RAM (W7 32 bits).
> I am thinking this is due to memory fragmentation.
>
> I am afraid we have more easily this issue if Eeschema + Pcbnew + other frames use OpenGL.
>
> Cairo do not have this issue.
> It is not fast, but not especially slow on my computer.
> Eeschema does not create drawings as complex as Pcbnew. So Cairo can be a candidate.
> Especially if OpenGL creates out of memory issues.
>
>>
>>> * It could be needed for printing as an alternative to the current wxDC
>>> canvas (wxDC has always issues for printing)
>>
>> Excellent reason. I don't see any good reason for not using cairo to print
>>
>>> * I do not see any good reason to add a lot of #ifdef in code.
>>
>> Fully agree with this, too... you don't like cairo, just don't use it.
>> Also IIRC is not an additional dependency since gtk (and wx by
>> extension) needs it. Could be different on mac/win obviously...
>>
>> So I vote to keep cairo in (it isn't invasive, either)
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> --
> Jean-Pierre CHARRAS
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp