On Mon, 18 May 2009, Mark Burton wrote:
How about this:
1 - with no option specified, the default number of jobs (aka threads) is 1.
2 - specifying --max-jobs without a value will maximise the number of jobs (i.e. create one thread per core).
3 - specifying --max-jobs=N will create N threads.
Would that suit you?
This would be the best approach (and it's just like 'make -j'). Not everybody wants to clog their computer with a mkgmap run. If map generation really is time consuming it could also be done on one core in the background while the computer is responsive for other tasks. In addition, parallel mkgmap requires more memory which is not available on all computers. For instance the laptop I am writing this mail on has a dual core but only 1GB memory, that's scarce even for one mkgmap thread. -Wolfgang