[wxPython] Building contrib/stc with wxWindows 2.2

[David Bolen]

I'm trying to locally rebuild wxWindows and wxPython using the latest files
from CVS on the 2.2 branch, and just about everything is working properly
except for the contrib/stc directory.

I can rebuild the Scintilla tree for wxWindows itself without problems, but
running the "build -b" in the contrib/stc tree beneath wxPython generates a
ton of warnings and/or errors about duplicate definitions when trying to
compile the actual files from the wxWindows contrib/stc tree.

The collisions all appear to be between definitions that are in Scintilla's
"windefs.h" file (subset of windows items) and the actual Windows headers.
Since I don't get the duplications when building Scintilla directly beneath
wxWindows, I'm assuming there's just some simple environment difference
causing the problem, and was wondering if its something that someone else
had run into and might point me in the right direction.

Oh, and as an aside - was the official 2.2.0 release of wxPython built
against the final commits on the 2.2 wxWindows branch, or against the actual
WX_2_2_0 label? It seems some commits were done after that label but before
2.2 was merged back into the main branch (and I know that whole "mess" was
under some discussion on the wx-devel list).

Thanks.

-- David

[Robin Dunn]

> The collisions all appear to be between definitions that are in
Scintilla's
> "windefs.h" file (subset of windows items) and the actual Windows headers.
> Since I don't get the duplications when building Scintilla directly
beneath
> wxWindows, I'm assuming there's just some simple environment difference
> causing the problem, and was wondering if its something that someone else
> had run into and might point me in the right direction.
>

In .../include/wx/app.h at about line 383, comment out the lines that
include windows.h and winundef.h

> Oh, and as an aside - was the official 2.2.0 release of wxPython built
> against the final commits on the 2.2 wxWindows branch, or against the
actual
> WX_2_2_0 label? It seems some commits were done after that label but
before
> 2.2 was merged back into the main branch (and I know that whole "mess" was
> under some discussion on the wx-devel list).
>

I didn't sync to the tag but it was real close as I stopped updating at the
same time...

--
Robin Dunn
Software Craftsman
ro...@AllDunn.com
http://wxpython.org Java give you jitters?
http://wxpros.com Relax with wxPython!

[Neil Hodgson]

> > The collisions all appear to be between definitions that are in
> Scintilla's
> > "windefs.h" file (subset of windows items) and the actual Windows
headers.
> > Since I don't get the duplications when building Scintilla directly
> beneath
> > wxWindows, I'm assuming there's just some simple environment difference
> > causing the problem, and was wondering if its something that someone
else
> > had run into and might point me in the right direction.

The redefinition of Windows constants inside Scintilla is a known problem
and is on the list of things to fix. However, fixing it properly involves
declaring platform independent IDs for a lot of things such as keyboard key
symbols and converting to and from these in the correct places. I'll try to
get to this in the next couple of weeks.

This will also require changes to client code. That is, to the wxSTC
code, not to clients of wxSTC.

Neil