Author Topic: [Windows] precompiled wxWidgets in next release  (Read 32051 times)

Offline inventore123

  • Multiple posting newcomer
  • *
  • Posts: 11
Re: [Windows] precompiled wxWidgets in next release
« Reply #30 on: July 11, 2008, 05:17:51 pm »
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

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: [Windows] precompiled wxWidgets in next release
« Reply #31 on: July 11, 2008, 05:28:37 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: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline JGM

  • Lives here!
  • ****
  • Posts: 518
  • Got to practice :)
Re: [Windows] precompiled wxWidgets in next release
« Reply #32 on: July 11, 2008, 07:03:07 pm »
I should hurry up and finish codepacks plugin  :D