Hello Jim Chaney, What version of CMake are you using? I'm using 2.6.2-RC4 here. I often use make -j7 on my company's 8 core Mac Pro. (Leaving the remaining core to manage interprocess communications, run make, manage disk caches, etc.) Using that configuration I can build ParaView in only 7-10 minutes. Occasionally it bombs out but if I repeat the make it picks up where it left off and finishes the build.
--- On Wed, 9/17/08, Jim Chaney <[EMAIL PROTECTED]> wrote: > From: Jim Chaney <[EMAIL PROTECTED]> > Subject: Re: [CMake] make -j and cmake > To: [email protected] > Date: Wednesday, September 17, 2008, 1:47 PM > In case my first post to the list went missing, re-posting. > > (If my post did reach the list, help! :) > > Jim > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jim Chaney > Sent: 12 September 2008 10:54 > To: [email protected] > Subject: [CMake] make -j and cmake > > I have been attempting to switch CMAKE from building using > nmake (via a customised Microsoft Visual Studio 8 generator) > to a cygwin make (using Unix Makefiles generator) in order > to use the -j option. A previous post > (http://www.cmake.org/pipermail/cmake/2008-April/021338.html) > noted that Bill Hoffman had made a special version of make > that fixed/reverted some path/drive letter change in the > main CVS branch. > > Although the version of make available on the cmake website > seems to work OK from the command line, when I then run it > under Incredibuild (to move from parallel to distributed > builds) I get a crash inside make.exe. I have spoken to > Xoreax (the makers of Incredibuild) and they are interested > but unable to assist, as the problem is inside make and not > their product. The logical step then was to make my own > debug version of make from the source, but I cannot get the > same behaviour from a locally compiled make (using latest > CVS as downloaded from Savannah) as I do with the version > from the cmake website. > > So to the questions: > > 1) What modifications were made to > the CVS of make? Is there a certain date I should sync > to? (I notice that it says the -j option only takes effect > for that call to make, and subsequent calls have to have -j > added to them; I dont think the cmake generated makefile > will do this for me, will it?) > > 2) When I get 'valid' source, > what parameters were used in the config.h? Most > importantly, was HAVE_CYGWIN_MAKE or HAVE_MKS_MAKE defined? > > > Apologies of this seems tangential, but unless I am > misunderstanding the CVS repository make hasn't been > released for 2+ years so the change from Bill has never been > released... > > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
