On 04/13/2012 02:07 AM, Magnus Ihse Bursie wrote:
As for the --with-num-cores, yes, it is a configure time option. The underlying assumption is that your hardware doesn't really change, and if your build system is too weak, it will be too weak at configure time and at all make times. With that said, it is always possible (and not very hard) to re-run configure if you need to tweak such a parameter.
As a developer, my machoine may not change, but my expectations may. Sometimes I want a build to run in the background while I pursue other activities, whether tetris, browsing, or working on the next bug fix. Other times, I need the build ASAP. So while your underlying assumption is good for batch build systems, it may not always be true on developer machines.
The output build directory is named differently, yes. If you have local scripts that depend on the name of output directories, you will have to modify those. The exact format of the automatically named output directories is still not cut in stone, though, so the actual names might change. One of the reasons for the new names is to allow multiple configurations in parallel, with different options such as debug level or target platform.
It would be nice (and would make sense in this side-by-side world) to have a configure option to use the "traditional" build directories. We have yet to see how much developers will want to build multiple configurations side-by-side.
/Magnus
