Instead of taking FreeAsic's problems seriously, they prefer to kill the messenger...
The thread "Using a static library: linker problems" was deleted - no problem, every new user of FB will run into the same problems over and over. It's a shame, because FreeBasic is perhaps (next to PowerBasic) the last good BASIC compiler around. But the
FB Forum is so crammed full of desperate users asking for help because their simple proggies won't compile with the xyz "toolchain". Many problems are caused by fanatic type checking that simply does not work in a Windows environment, others because, well, for the benefit of serving the 1% Linux fans, one has to sacrifice lots of good features.
So, Hutch, please keep up the good work with PowerBasic - the World of BASIC needs you

P.S.: The text below was supposed to be my last post

...which helps no one.
First, I have not enough time into indulging into the secrets of compiling fbc.exe, so bear with me if I can't help you with code. Quoting one friendly member whose name I want to keep out of this thread:
The warnings can be suppressed by doing things like
wc.hbrBackground = cast(HBRUSH__ PTR,(COLOR_BTNFACE+1))
and
wc.hIcon = LoadIcon(hIconLib, cptr(any ptr,239)) ' get the butterfly icon
Yes, that will suppress the warnings, but you really
cannot expect such stuff from a newbie, especially not in a language that has a "B" in its name.
What the compiler could do, instead, is to check what the wc.hbrBackground member expects, and to provide the friendly Gcc compiler automagically with the necessary cast if,
and only if, the naked parameter passed by the newbie
can be casted to what the compiler expects. Another example: SendMessage. Numerous absurd warnings and errors. Each Message is documented, and can tell the compiler the kind of parameters that are
expected. Now if the user passes a FB string where a zstring ptr is expected, cast it, for heaven's sake, but don't ask the "B" user fumble this.
IMHO that would be sufficient to make all nonsense warnings disappear.