kicad-developers team mailing list archive

[Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>]

On Wed, Aug 01, 2012 at 04:17:00PM +0200, Miguel Angel Ajo Pelayo wrote:
> > Hmm, AFAIK, It's only a shared library installed to Python, some extra .py
> files, and it includes some extra headers
> that will go under wx-xx.xx/wx/wxPython when you install it, but no static
> libraries or anything, just the .h files
> under there are self-contained and unleash the full potential of your
> system installed wx library :-)

http://wxpython.org/builddoc.php says that the package builds *both* wxWidget and wxPython. Maybe it's to avoid dll hell with mismatching release...

> Everything is handled by cmake at this moment, will need to tweak Win32 a
> little bit again, but probably not too much.

I don't mean from the kicad side, is the wx build which worries me

> I'm testing with standard installed wx-2.8 , and wxpython in ubuntu +
> python 2.7, but Edwin was making it work with python-2.6,

OK similar to me then. wx-2.8 and python-2.7 should give troubles then (never used python, I installed it only to run bzr:P)

> Sorry, don't know what do you mean exactly for that part :-)

When you build wxWidget you could enable a 'checked build' which pops up assertion boxes on programming issues (like using an uninitialized dc and stuff). I tracked down a lot of bugs in kicad with these.

Anyway thanks for the suggestion, I'll try to make it work...

-- 
Lorenzo Marcantonio
Logos Srl