It turns out mingw has a few bugs which makes it a bit
difficult to fix it for filenames / paths containing space.
Problem #1/#2:
- windres tries to pass the input file to gcc for preprocessing,
but it has a bug forming gcc's name if windres was invoked
with an explicit path containing space. And another when
the input file is wrongly passed. The latter could theoretically
by fixed by using std input, but in this case there is a warning
telling: "cc1.exe: warning: is shorter than expected" (plus
hbmk2 needs to resort calling the shell to invode the command,
but that's okay)
Problem #3:
- 'gcc -l"lib with space"' won't work. ('gcc "-llib with space"' also won't)
If anyone has solutions for these I'd appreciate them.
It would be nice to have equal support for this for all
Windows compilers. It would also allow to install the
Harbour binary package to standard place, like "C:\Program Files".
Brgds,
Viktor
On Sat, Jun 20, 2009 at 1:11 PM, Viktor Szakáts<harbour...@syenar.hu> wrote:
> Hi Przemek,
>
> I'd like to add support for spaces in input/output filenames
> to mingw targets, but I'd also like not to break it for
> Linux cross-compile situations.
>
> Any hints regarding space handling in 'i386-mingw' and
> 'arm-wince-mingw32ce' modes?
>
> Most importantly is it Windows compatible, or does it
> need some other logic? If yes, what is this logic?
>
> Brgds,
> Viktor
>
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
