Approach 2: Use different views

Perform builds for different platforms in different views ( sun5_bld_vu, sles15_bld_vu, and so on).

A team of developers working on the same variant can share a view or each can work in an architecture-specific view.

In most cases, the build script that creates a derived object differs for each variant, as described in Handling build procedure differences. If so, clearmake prevents winkin of derived objects built for another architecture. You can force the build script to be architecture specific by including a well-chosen message or comment. For example, if BLD_ARCH is used as described in Handling build procedure differences, you can include this message:

@echo "Building $@ for $(BLD_ARCH)"

The disadvantage of this approach is that when an element is checked-out, you can build only one variant of the application. Because the checked-out version is visible only in one view, builds of other variants (which take place in other views) do not select the checked-out version. You must check in the element before building other variants.

Another disadvantage is the number of views that might be required. For example, if seven developers want to maintain their own views in which to build four variants, 28 views are required.