The changes I just pushed to the Nevada X gate for CR 6933880 make
some changes to the way the builds are done in the X gate that you
may need to know about.

When you build the tree, instead of unpacking the sources into
build_32 and build_64 directories for the 32-bit and 64-bit builds,
platform-specific names are now used: build-sparc, build-sparcv9,
build-i386, build-amd64.   The contents of each directory should be
the same as before.

This should allow you to keep a tree built for both architectures
and do incremental builds on either one.

You cannot do full builds in parallel in the same tree - since there
is no coordination between builds running on different machines (as
they must be since we don't have cross-compilers), there will likely
be race conditions when both machines end up in the platform-independent
parts of the build, like the font directories.   (Builds break if one
is running make clean in the same directory another is running make install.)

Once you've done the buildit on each platform in turn though, you should
be able to rebuild individual platform-specific modules in parallel - though
I haven't fully verified or tested this.

For instance, if you're updating an X server patch, you should be able
to run "xmake clean ; xmake install" in open-src/xserver/xorg on both
the SPARC & x86 machines at the same time.   You should certainly be able
to do one after the other and then be able to test.

There is still only one proto-packages, so each time you run
make_release_packages or buildit -p, the proto-packages directory
will be removed and rebuilt with the current platform package set.

This should be improved when we transition to IPS (which merges binaries
from both platforms into a single package set), so I haven't spent the
time to change this for the few builds between now and then.

"make clean" will remove the old build_32 & build_64 directories as well
as the new names, to help clean up as we make this transition, so there
should be nothing you need to manually do, other than be aware that
the build directories have changed when you look for them.   It will only
remove the directories for the current platform, so if you've built on
both, and need to save maximum disk space, you will need to run make clean
on both as well.

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Oracle Solaris Platform Engineering: X Window System

Reply via email to