kicad-developers team mailing list archive

[Maciej Sumiński <maciej.suminski@xxxxxxx>]

On 10/25/18 2:23 AM, Seth Hillbrand wrote:
> Am 2018-10-24 17:20, schrieb Maciej Suminski:
>> Actually I was pretty sure that my approach is bullet-proof, but perhaps
>> I do not get where the trap is hidden. As far as I understand, Seth
>> experienced problems when pcbnew (wxWidgets/gtk2) loaded wxPython shared
>> libraries (wxWidgets/gtk3), which end up in symbol conflicts.
>>
>> This issue is eliminated in my branch by ensuring KiCad requests the
>> same wxWidgets flavor as is used by wxPython. I might be lacking
>> explanation skills, but code is unambiguous - have a look at [1], lines
>> 746 and 775.
> 
> Hi Orson-
> 
> It looks like this overwrites the user's preference for GTK toolkit. 
> I'd like to keep the ability to specify which toolkit I compile against
> if possible.
> 
> Best-
> Seth

I will add such option, but keep in mind that pcbnew will be broken if
wxWidgets and wxPython use different toolkits. Note that the toolkit
version is enforced only on Linux and when KICAD_SCRIPTING_WXPYTHON is
enabled.

Cheers,
Orson

Attachment: signature.asc
Description: OpenPGP digital signature