Paul,

FWIW, I'm using MSVC too (VS 2005) and while I didn't make any speed  
comparisons, the new make system appears faster. Additionaly the  
older system was forcing me to manually delete files to force a  
rebuild - f.e. every time I made any modification to ppcore.c I'd  
have to delete ppcore.obj, and harbour.exe to force a rebuild.  
Similar issues every time I touched harbour.sly, and/or harbour.slx.  
You might remebber I reported this long ago and you promised to take  
a look.

IMO, even if the new make system would be slower, between the  
resolution of long standing problems as above, to the centralization  
and unification of all make files, it's a minor cost to pay.

FWIW, I suppose the speed issue must be related to using a NW drive,  
which I don't use.

Ron

On May 31, 2008, at 7:18 PM, Paul Tucker wrote:

>
>  RP> Do you have any specifics on why would compile time be slower? My
>  RP> experience has been the opposite - I think this new make  
> system is a
>  RP> great improvement.
>
> I'm using MSVC.
>
> I'll not argue the fact that the original system left something to be
> desired, but I can't see how your experience can be possible.
>
> Generally speaking, with the previous system, all c files for a lib  
> were
> compiled with the same invocation of cl (sure there are exeptions  
> to that) -
> with this system, it's all done 1 file at a time.
>
> I have a 750gig raid 0 drive which gives decent throughput and I  
> can set up
> an e:drive by either using subst e: c:\drives\edrive or share that  
> location
> as 'edrive' and net use e: \\paul\edrive.  (my development drive is  
> e:)
>
> When set up as a network share, speed drops because (I guess), the  
> cacheing
> no longer works the same as it does for a 'real' drive.
>
>                                             subst        network
> old makallvc clean/makallvc:    8min       45min
> new make_vc clean:               13min      75min
>
> The 'old' system is from may 26 2007 and certainly could be  
> improved upon by
> at least correcting the way the dll is built.
>
> Paul
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers

Reply via email to