User forums > Help

wxWidgets 2.6 (MSW, GCC) installation instructions

<< < (23/29) > >>

wittend:
In reply to Tdragon:

"1. You have the wrong wxWidgets installation. Make sure it's wxMSW-2.6.2.zip, or wxWidgets-2.6.3-rc1.zip (I have successfully built and used both)."

-- I used 'wxMSW-2.6.2-Setup.exe'.  Last time I used wxWidgets-2.6.3-rc1.zip.  I will try removing the current installer-based package and try the 2.4.2 zip.

"2. The make executable included with MSys is somehow interfering with the original mingw32-make, or mingw32-make or related files have been overwritten somehow."

-- I completely uninstalled MSys before beginning the latest build.  I tested the versions of the tools from the command line, and made certain that the mingw tools I needed were ahead of everything else that could interfere in my path.

-- The command using 'make' instead of 'mingw32-make' was not actually what I used.  In composing the msg, I scrolled my cmd window back - just not far enough.  I tried plain 'make' after 'mingw32-make'  did not produce reasonable results.  Both produced identical output - since the shell commands used are not going to work at a Win32 command line.

Morten:

The location D:\bin\CodeBlocks\wx is just where things have ended up after many unsuccessful attempts.  I agree that it doesn't make good sense, and I have in the past and will in future use another location.  But I think that aesthetics aside, it is not impacting my build attempts.  The problem may lie in the fact that I used  'wxMSW-2.6.2-Setup.exe'.  I'm not even certain where I got it. I was accumulating so many versions that I did a bit of cleanup on my DL directory and now I don't have a zip copy, and I know that I did have it.  A fast connection just turns me into a download pig!

Michael:

I did build 2.6.3-rc1, and some paths seemed odd at the end.  I was unsure if it was something I did or something about the package.  I have nuked it now so I can't be sure what the problems were.  But some of the critical includes seemed to be buried in odd locations like wx/lib/wx/include/msw - an include directory under a lib directory?  or maybe it was just my carpal tunnel kicking in, causing unintended drag/drops in explorer.

thanks for all the input

-- dave



MortenMacFly:

--- Quote from: wittend on February 24, 2006, 02:24:51 pm ---[...]that I did a bit of cleanup on my DL directory and now I don't have a zip copy, and I know that I did have it.

--- End quote ---
Sounds good to me, because I have used a ZIP file for wxWidgets, too. Did you try my bacth file then?

wittend:
I'm just about to try the batch file now.  I'll let you know how it goes.

thatnks,

-- dave

wittend:
It seems that SourceForge doesn't have a copy of wxWidgets-2.6.2.zip - it bounces me into a very large FTP directory.  There is a wxMSW-2.6.2.zip, and wxWidgets-2.6.3.zip and wxWidgets-2.6.2.bz2, etc.  I'll try the wxMSW-2.6.2.zip version, but something seems a bit screwed up on SF.

dave   

TDragon:

--- Quote from: TDragon on February 24, 2006, 06:24:29 am ---Make sure it's wxMSW-2.6.2.zip, or wxWidgets-2.6.3-rc1.zip (I have successfully built and used both).

--- End quote ---
:)

Michael: Yep, I had layout problems too. In fact, I lost the debug toolbar entirely until I reverted to 2.6.2 and reset my layout settings to the default.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version