I try to build wxPython from CVS HEAD on Windows ME using MS VC.
wxWindows build ok (UNICODE=1, MSLU=1, FINAL=1)
But wxPython fail on link.
See log file on http://ikar.t17.ds.pwr.wroc.pl/~wiget/m/tt.log
Regards
--
Artur Frysiak
http://www.pld-linux.org/
Artur Frysiak wrote:
I try to build wxPython from CVS HEAD on Windows ME using MS VC.
wxWindows build ok (UNICODE=1, MSLU=1, FINAL=1)
But wxPython fail on link.
See log file on http://ikar.t17.ds.pwr.wroc.pl/~wiget/m/tt.log
What version of MSVC? (7.0 is known to be too agressive when optimizing and tosses out code that shoudl not be.)
You may want to verify that the wx libs and dlls were actually updated with your build and that you are not actually using old versions. I think that with the flags you mention above the libs and dlls may end up getting named differently, with a "custom" in their name.
I'll attach the scripts I use to build the wx and contrib dlls. They are for 4DOS/4NT so probably will not work with the standard command.com or cmd.exe, but they should still help you see how I build things. (Although I reccommend using 4DOS.) Just drop them in your wx2.5/build/msw dir and to build a release mode unicode version you would just run ".make release-uni" with 4DOS.
.make.btm (2.37 KB)
.mymake.btm (1.3 KB)
.makesetup.mk (1.48 KB)
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!