OT: Multi-core optimized compilation?

Hi,

I have a, somewhat large, amount of data to compile (drivers). A
single driver is compiled fast enough, but current project (which has a
base code set, and several subsets) could make use of multiple
cores/CPUs, especially since sometimes I do several compilations in a
row.
Anything I can do for the WDK compilers to take advantage of
multiple cores?
I’ve been considering doing a batch file to do this, with
multithreaded “start” command, waiting until all compilations finish to
do the next phase. I might resort to this, since the “next phase” isn’t
a driver compilation and it can be made multicore aware, too. But
thought I’d at least use what’s available for some part.


Kind regards, Dejan
http://www.alfasp.com
File system audit, security and encryption kits.

I think BUILD will do the multi-CPU build by default, if your code is in
several directories, is it not so?


Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

“Dejan Maksimovic” wrote in message news:xxxxx@ntfsd…
>
> Hi,
>
> I have a, somewhat large, amount of data to compile (drivers). A
> single driver is compiled fast enough, but current project (which has a
> base code set, and several subsets) could make use of multiple
> cores/CPUs, especially since sometimes I do several compilations in a
> row.
> Anything I can do for the WDK compilers to take advantage of
> multiple cores?
> I’ve been considering doing a batch file to do this, with
> multithreaded “start” command, waiting until all compilations finish to
> do the next phase. I might resort to this, since the “next phase” isn’t
> a driver compilation and it can be made multicore aware, too. But
> thought I’d at least use what’s available for some part.
>
> –
> Kind regards, Dejan
> http://www.alfasp.com
> File system audit, security and encryption kits.
>
>
>

Hmm, it does… I used nmake all this time, but I see this will work. Thanks!

“Maxim S. Shatskih” wrote:

I think BUILD will do the multi-CPU build by default, if your code is in
several directories, is it not so?


Kind regards, Dejan
http://www.alfasp.com
File system audit, security and encryption kits.

My current project (~200KB user-mode EXE, built by 2003 DDK with the plans
to upgrade the build env) has lots of subdirs, and LIB is built from each
subdir, then the LIBs are linked together.

In this mode, BUILD on SMP machine runs in several threads automatically,
no setup needed.


Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

“Dejan Maksimovic” wrote in message news:xxxxx@ntfsd…
>
> Hmm, it does… I used nmake all this time, but I see this will work.
Thanks!
>
> “Maxim S. Shatskih” wrote:
>
> > I think BUILD will do the multi-CPU build by default, if your code is
in
> > several directories, is it not so?
>
> –
> Kind regards, Dejan
> http://www.alfasp.com
> File system audit, security and encryption kits.
>
>
>

Yep, I noticed that now. I knew build.exe had UP/MP commands, but I wasn’t
aware that requires separate dirs, I thought it would compile a single directory
in MP mode. Thanks!

“Maxim S. Shatskih” wrote:

My current project (~200KB user-mode EXE, built by 2003 DDK with the plans
to upgrade the build env) has lots of subdirs, and LIB is built from each
subdir, then the LIBs are linked together.

In this mode, BUILD on SMP machine runs in several threads automatically,
no setup needed.


Kind regards, Dejan
http://www.alfasp.com
File system audit, security and encryption kits.