On Wed, 06 Aug 2008, Szakáts Viktor wrote: Hi Viktor,
> 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. I haven't made any real Windows builds for very long time but AFAIR it was very easy to setup MinGW and MSYS environment. You have to sets of GNU tools one designed for MSYS and 2-nd for Windows command shell. It was enough to keep them in default paths and when you want to use MSYS then simply set MSYS binary directory at the beginning of your PATH. Otherwise do not set it at all or set it at the end. That's all and it was working for me. > 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. I do not agree. What is missing for you in GNU make? For me it's the best make tool and when I have to use some other then I still found some limitations. Maybe I do not know those tools enough but as I can see some things cannot be easy resolved also i our non GNU make files what effectively blocks their simplification. Other thing is _OUR_ GNU make files. It should be seriously changed but because it has to work on all supported platforms then I try to not touch it as long as possible. Somewhere in the future I'll try to change it but without any deadline because all modifications will have to be tested in many different platforms and environments. > Anyhow, anyone who managed to tame MinGW in a > proper way, is welcome to share his experiences, > and best practices. Today I'll try to make some tests with real MS-Windows machine. Maybe I'll find some problems which appeared in last year(s). best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
