Building Wine with multiple jobs

[Vinska]

Hello!

As far as I know, the correct procedure to build Wine goes:

Code: Select all

./configure [options]
make depend
make

When using a multicore CPU, to speed up the build, one can tell make to run more jobs, thus use all the cores. Now, the thing is: I have read [don't remember where exactly, it was quite long ago], that it is only OK to use it with the last step (make), but is an inherently bad idea to use with "make dep".
Out of curiosity, I did try to run "make -j9 depend" (I am using an 8-core CPU). It did not complain at all, built without any problems, and Wine itself ran as well as always.
I am wondering: was what I read before false, I got lucky this one time, or it just looks like it built and runs well while there is some problem "hiding in the shadows"?
In short: is it OK to run "make depend" with multiple jobs (i.e. "make -j[some_number] depend")?

[vitamin]

I am wondering: was what I read before false, I got lucky this one time, or it just looks like it built and runs well while there is some problem "hiding in the shadows"?

It always depends on a project. Make system is a complicated beast and not everyone gets it right.

As far as Wine goes - you can do both (dependency and build) with multiple jobs. If it doesn't work - file a bug and it should be fixed. The only thing that's known not to work in parallel are the tests (make test).

[André H.]

I want to mention that make depend shouldn't be needed anymore (maybe if you patch some things)

[vitamin]

I want to mention that make depend shouldn't be needed anymore (maybe if you patch some things)

"Not needed" does not mean "doesn't exist". "All" target includes it by default. But it still very much alive and is a required step for proper compiling.

[André H.]

i mean there's no need to explicitly run it, because of the inclusion in make all. AJ once changed the buildsystem so that it's integrated.