[wxPython-dev] wxPython for windows 64-bit

[Brandon Pedersen]

Ok, so I am very new to compiling with msvc...actually C in general...never
really programmed using C...anywho, so I read some of those posts and it
talked about when linking the files you need to use an extra command line
parameter of bufferoverflowU.lib to overcome the missing __security_cookie
thing....so instead of like "link file.cpp", it should be "link file.cpp
bufferoverflowU.lib"....now I am wondering how I can do that since I am just
using nmake to do all the work...is there some file I need to change so that
that parameter is added to all the linking steps? Sorry for my
ignorance...thanks for your help

Brandon

-----Original Message-----
From: Robin Dunn [mailto:robin at alldunn.com] 
Sent: Monday, November 12, 2007 4:04 PM
To: wxPython-dev at lists.wxwidgets.org
Subject: Re: [wxPython-dev] wxPython for windows 64-bit

Brandon Pedersen wrote:
> Hello all,
> 
>  
> 
> I tried this on the users list but no response yet so I thought I would 
> try here.
> 
>  
> 
> I have been trying to get wxPython to work with 64-bit windows. First of 
> all does anyone know of a build out there that is 64-bit? I cannot seem 
> to find any. I would gladly use the 32-bit version but there are some 
> other libraries that I need for python that if I use 32-bit python on a 
> 64-bit machine it will not work, so I am stuck using 64-bit python and 
> therefore need 64-bit wxPython..


I have no experience with 64-bit Windows.  If somebody could provide a 
copy of 64-bit XP I'll give it a whirl and see if I can start providing 
binaries.

> 
>  
> 
> I have tried compiling using the build instructions using both VS 2005 
> and VS.NET <http://VS.NET> 2003. With VS 2005 I am able to compile the 
> wxWidgets ok, although for some reason I could not get it to compile 
> with the Unicode flags, said something about not being able to open 
> unicows.lib.after I compiled the widgets I went to use the setup.py and 
> got errors about the compiler I was using.can't remember what it was 
> exactly but found on the web that I should use VS 2003 or 7.1 which is I 
> believe 2003.

Unicows would only be applicable to 32-bit anyway, so you can try 
leaving the MSLU settings in the build instructions at zero instead of 
one.  Afterall, you can's run a 64-bit binary on win98!  ;-)


> So I tried compiling with VS 2003 and I can't even compile wxWidgets.I 
> used the following command:
> 
>  
> 
> nmake -f makefile.vc <http://makefile.vc> OFFICIAL_BUILD=1 SHARED=1 
> MONOLITHIC=0 USE_OPENGL=1 USE_GDIPLUS=1 DEBUG_FLAG=1 
> CXXFLAGS=/D__NO_VC_CRTDBG__ WXDEBUGFLAG=h BUILD=release UNICODE=0 MSLU=0
> 
>  
> 
> I would love to be able to use the Unicode flags.I am not too worried 
> about supporting win9x so I may not need the mslu but I would like to 
> support Unicode for other windows platforms but I always get the error 
> about opening unicows.lib or whatever its called.
> 
>  
> 
> This is the last part of the output I get.
> 
>  
> 
>    Creating library ..\..\lib\vc_dll\wxbase28h.lib and object 
> ..\..\lib\vc_dll\w
> 
> xbase28h.exp
> 
> wxzlibh.lib(wxzlib_trees.obj) : error LNK2001: unresolved external 
> symbol __secu
> 
> rity_cookie
> 

Did you read any of these? 
http://www.google.com/search?hl=en&q=__security_cookie


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!


---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help at lists.wxwidgets.org