BorlandTalk.com

Roddy Pratt · Guest

I feel strangely compelled to raise the issue of BCB compile speed (or lack
of it) once more.

I'm aware of the stock answers, namely

* C++ is awseomely difficult to compile
* Pre-compiled headers don't work the way you think
* Your computer needs more memory
* You need a faster computer/more disks/faster disks/more computers
* You need a slooooower brain

And, it's always nagged me, because I came to BCB from Delphi, and Delphi
has always just blazed along when compiling,

But, today I saw something that that makes me feel that there's more to it
than that: ProjectMaker
(http://helene-lange-weg.mine.nu/Rutsch/cppcorner.html)

It's not perfect: it doesn't work for all projects, and it doesn't play
nicely with the IDE, but it DOES speed up builds by a factor of between 5
and 10.

That is, a two minute BCB5 build of my project takes well under 20 seconds
with Projectmaker.

As far as I can tell, it achieves this magic just by running the Borland
command line make and compile tools. What *possible* sane reason is there
for this to give a five or ten times speedup???

I don't know if I can use ProjectMaker for real yet, but I now believe that
BCB compiles slowly because there's the equivalent of a brick wedged under
the gas pedal. Will DeXter remove the brick? I hope so!

- Roddy

David Charron · Guest

"Roddy Pratt" <roddy at spam fritter dot com> wrote in <42b30cc2$1
@newsgroups.borland.com>:

Dave · Guest

I've been using it and it works good (MUCH faster) but I have to exit the
IDE before I build. I would be VERY disapointed if the new C++ Borland is
working on built any slower in the IDE than this can do. Now that we know
this is possible anything less is unacceptable, build speed is just too
important.

Dave

Roddy Pratt · Guest

"Dave" <drbsname_ (AT) _aol (DOT) com> wrote

Siegfried Rohdewald · Guest

You may want to test the SuperSpeed RAMDisk utility. I use it with just
512 MBytes of RAM under Windows XP SP2, and it speeds up build times of
BCB5 by about 40% (30 to 40 seconds instead of about 1 minute). Code
size is about 100,000 lines.

Be sure to specify file system NTFS for the RAMDisk virtual drive.
Right click the virtual drive in Windows Explorer and check option
"Compress drive to save disk space" so all intermediate and final
output files fit into RAM.

HTH,

Siegfried.

Roddy Pratt wrote:

Al Acker · Guest

Hendrik Schober · Guest

Al Acker <al (AT) thexbasefiles (DOT) com> wrote: