News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

[Windows] precompiled wxWidgets in next release

Started by inventore123, July 07, 2008, 01:16:58 PM

Previous topic - Next topic

inventore123

Thanks!
The 8.3 trick worked, I changed "C:\Program files\CodeBlocks\wxWidgets-2.8.8" in "C:\PROGRA~1\CodeBlocks\wxWidgets-2.8.8", and now I can compile everything.
I'll also try with new MinGW releases, to see if new windres.exe no longer have this bug.

Last thing, can you confirm me that the path for #wx global variable MUST be an absolute path, and that relative path don't work (I mean relative with respect to codeblocks folder, like saying "./wxWidgets-2.8.8" instead of "C:\Program files\CodeBlocks\wxWidgets-2.8.8"), because when I do so I get errors not only related to windres.exe, but also gcc.exe

MortenMacFly

Quote from: inventore123 on July 11, 2008, 05:17:51 PM
Last thing, can you confirm me that the path for #wx global variable MUST be an absolute path
That's true. Hence for the "childs" (like include etc...) you can use relative path's again - just like a recursion. This way you need to change only one path if you are on another platform.

For example, imagine a global variable, named "GV":
base path: C:\Whatever\MyLib
include path: $(#GV.base)\the_includes
lib path: $(#GV.base)\the_libs
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

JGM

I should hurry up and finish codepacks plugin  :D