Hi Przemek,
Okay, I see now. What I still don't see is how to
assemble a properly usable MinGW environment without
manual hacks.
I know have two pre-build manual instructions for
MinGW, and it doesn't help to make the process
automatic or easy to port or replicate.
Currently I have to rename msys sh.exe to sh-.exe
to make MinGW builds possible using the Windows
shell. I have to do the opposite if I want to build
using bash shell, plus now I have to copy over
sed.exe from msys to mingw, if I want to make it work.
With for different MinGW version installed (and
sometimes updated separately), this becomes quite
error prone and ugly. As a mere user, just wanting
to use MinGW, I'd expect a somewhat more user-friendly
or straightforward approach. Not to mention if we
want to give someone instructions, how to replicate
the process locally.
I'm not sure if we can do anything more to make
the above easier, or this is the job of the MinGW
team, but it's very sad that MinGW (and GNU on
Windows in general) was and still - after 10 years -
is such a PITA to work with.
And to rumble a bit more: GNU make is probably the
far weakest piece of the GNU toolchain, I can't even
understand how it didn't get a replacement in all
these years.
Anyhow, anyone who managed to tame MinGW in a
proper way, is welcome to share his experiences,
and best practices.
Brgds,
Viktor
On 2008.08.06., at 12:58, Przemyslaw Czerpak wrote:
On Tue, 05 Aug 2008, Szakáts Viktor wrote:
Hi Viktor,
Finally I simply copied over sed.exe from msys to mingw dir,
and this way it worked without the error. Thanks for the tip.
[ I wonder however how these tools are meant to be used properly,
if even a 'sed' cannot work consistently along different builds,
not to mention the rest of the mess. I also wonder if there is
any clean method achieve the above effect. ]
The answer is very simple. MS-Windows pass parameters to application
as single ASCIIZ string not as arrays of ASCIIZ strings like in
*nixes.
It means that in Windows is not possible that SHELL divide parameters
using given shell rulles and pass them correctly to application which
only have to scan each of them. In MS-Win each program has to parse
and
divide parameters using it's own rules. Because program does not know
anything about the SHELL from which he was executed then he cannot
make
it well for all environments. The main differens in GNU tools ported
for MS-Windows is the method of parameters extracting. Never try
to use tools compiled for MSYS/SHELL environment in cmd.exe/
command.com
and tools compiled for MS-Win command interpreter in *nix like shells
because some more advanced parameters (using spaces or special
characters)
will be wrongly recognized.
This is not GNU tools problem but MS-Windows limitation inherited
from DOS.
best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
