kicad-developers team mailing list archive

[Dick Hollenbeck <dick@...>]

Milan Horák wrote:
> Hallo Dick,
>
> I understand what you mean. And what you are trying to tell me.
>
> For now, problem was in '--enable-monolitic' directive in compiling 
> wxWidgets. When I disabled it, it created all that needed libraries.
> Had to create symlinks to them, cause they're created with _gcc_custom 
> suffix.
>
> Compilation succesfull.

Milan,

Congratulations, on your perseverance, and fortitude!

I expect that this capability will be used by some of the other 
developers to generate Windows binaries from Linux. While it is still 
fresh in your mind, I would like to gather all the data that we can, and 
standardize and document the solution.


Here is a summary of what you've told us. You:

1) Had to use CMake 2.6.4, not 2.6.2. You did not mention any edits to 
the CMake supplied FindwxWidgets.cmake for 2.6.4.


2) Had to build wxWidgets for windows without the '--enable-monolitic' 
flag, so that the names of the generated libraries matched those looked 
for in the stock FindwxWidgets.cmake


3) Had add a file UsewxWidgets.cmake to <kicad>/CMakeModules 
directory. WE NEED THIS FILE COMMITTED?


4) Had to change windres.exe to i586-mingw32msvc-windres in 
MinGWResourceCompiler.cmake according to Mateusz. I would like to 
find a way to isolate this change to your toolkit file. Can a proper 
variable be injected in your toolkit file so that the standard winres 
variable name can be used in MinGWResourceCompiler.cmake?


5) We need a copy of your toolkit file committed into the tree, although 
developers should know that this one is considered very "host machine 
dependent" and will need to be edited before use.



Last is a question:

Were you able to build wxWidgets for Windows on Linux?

Thanks,

Dick