Hi Lorenzo,
Do you know if MinGW's linker has support for
incremental linking in recent versions?
One of the things that put me off using MinGW,
is that linking my .exe (which is 20megs using -gc3)
takes so much more time than with BCC32, which
has the incremental linking feature (albeit
it sometimes gets confused about it, so a full
build is needed before release), so that it
takes only seconds.
Brgds,
Viktor
On 2008.08.06., at 15:48, Lorenzo Fiorini wrote:
On Wed, Aug 6, 2008 at 2:59 PM, Szakáts Viktor <harbour.
[EMAIL PROTECTED]> wrote:
Okay, I've checked all my m* dirs and there turned out
to be some leftovers from the past, so I'm currently
testing the cleaned environment. There are a few
strangenesses still, like missing make.exe from mingw,
even if I select this option. (The .exe is named mingw-make.exe),
but anyway, I have a mingw based make.exe in the path
anyway, so this is still hacky, but fine. I dropped msys
from the path for Windows shell builds.
This is correct, mingw make is a windows exe while msys/make is a
msys one.
( see Przemyslaw's previous message ).
I use msys/mingw since years like all my developers and I don't see
any major problem.
What I ask to my devs is:
- download and install stable mingw c/c++
- download and install stable msys
- never ever use batch files
that's all.
best regards,
Lorenzo
_______________________________________________
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