Thanks Xavi. Parallel compiling? Well, good idea actually :) It could be done, but I'm not familiar with MT programming (just concepts about coding *for* MT). The way to do it is most probably to split filelists into N chunks and launch these commands in separate threads and wait for them to complete before going to next make stage. A bit more gymnastics is needed for command which we are executing in a loop, where the whole loops has to be moved to thread.
If someone has working code for this, it'd be welcome. [ one minor: I cannot interpret 'infinite' number of jobs. ] Brgds, Viktor On Wed, Apr 15, 2009 at 3:41 AM, Xavi <jara...@gmail.com> wrote: > Great job Viktor, > > Thanks. > When compiling parallel multithreaded ? ;) > New option: -j [N], --jobs[=N] Allow N jobs at once; infinite jobs with no > arg. > > Xavi > > vszak...@users.sourceforge.net escribió: > > Revision: 10860 >> >> http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10860&view=rev >> Author: vszakats >> Date: 2009-04-14 22:26:26 +0000 (Tue, 14 Apr 2009) >> >> Log Message: >> ----------- >> 2009-04-15 00:22 UTC+0200 Viktor Szakats (harbour.01 syenar hu) >> * utils/hbmk2/hbmk2.prg >> + libpaths= can now have relative paths specified, and in this >> case the path will be adjusted by absolute path of host .hbp. >> This makes it possible to point hbmk2 to a .hbp file in a >> foreign dir, and let it pick up local lib dirs automatically. >> + .hbp files passed without absolute paths will now inherit >> the .hbm path if applicable. >> + Will now echo all explicitly specified .hbp filenames on >> screen in -info mode. >> + Added echo= support in .hbp files. The parameter will be echoed >> to stdout as is. >> + Added macro support for following .hbp lines: >> libpaths=, prgflags=, cflags=, ldflags=, echo=. >> Supported macros are: >> ${hb_root}: hbmk2 base dir >> ${hb_parent}: .hbp file dir >> ${hb_arch}: architecture >> ${hb_comp}: compiler >> ${<envvar>}: any envvar >> + .hbp files are now searched in libpaths, too. >> ; NOTE: With above changes it's possible to refer to a 3rd >> party lib solely by pointing to its .hbp file, from >> that point all lib/include paths can be automatically >> picked up. Here's an example for hwgui, the file >> needs to be places in hwgui root dir: >> --- >> {win}prgflags=-i${hb_parent}include >> {win}cflags=-I${hb_parent}include >> {win}libpaths=${hb_parent}lib >> {win}libs=hwgui hwg_qhtm procmisc hbxml >> {win}gt=gtgui >> --- >> Any hwgui apps can be compiled with this command: >> hbmk2 appname.prg C:\hwgui\hwgui.hbp >> >> * contrib/hbtip/tests/dnldftp.prg >> % Minor opt. >> >> Modified Paths: >> -------------- >> trunk/harbour/ChangeLog >> trunk/harbour/contrib/hbtip/tests/dnldftp.prg >> trunk/harbour/utils/hbmk2/hbmk2.prg >> >> >> This was sent by the SourceForge.net collaborative development platform, >> the world's largest Open Source development site. >> _______________________________________________ >> 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 >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
