[CUWiN-Dev] heads up: building cuwin for other architectures

[David Young]

The CUWiN build system will change soon to allow cross-builds for non-i386
architectures.  The build changes will affect people who already
build CUWiN in important ways that they need to be aware of.

Say that you set your BUILDDIR to $HOME/scratch-cuw/ with mkstaboot's
-b option.  The content of your BUILDDIR will change from something
like this:

        $HOME/scratch-cuw
        $HOME/scratch-cuw/T
        $HOME/scratch-cuw/O
        $HOME/scratch-cuw/D
        $HOME/scratch-cuw/Z
        $HOME/scratch-cuw/I

to this:

        $HOME/scratch-cuw
        $HOME/scratch-cuw/T
        $HOME/scratch-cuw/i386
        $HOME/scratch-cuw/i386/O
        $HOME/scratch-cuw/i386/D
        $HOME/scratch-cuw/i386/Z
        $HOME/scratch-cuw/i386/I

If you use the new build features to build for big-endian ARM
architecture---using, e.g., './mkstaboot -m evbarm -a armeb'---then an
evbarm/ directory will appear:

        $HOME/scratch-cuw/evbarm
        $HOME/scratch-cuw/evbarm/O
        $HOME/scratch-cuw/evbarm/D
        $HOME/scratch-cuw/evbarm/Z
        $HOME/scratch-cuw/evbarm/I

Cross-builds can share many tools.  That is why there is just one T/
directory.  If you look inside T/, however, you will find that some
subdirectories are architecture-specific:

        $HOME/scratch-cuw/T
        $HOME/scratch-cuw/T/bin
        $HOME/scratch-cuw/T/lib
        $HOME/scratch-cuw/T/share
        $HOME/scratch-cuw/T/info
        $HOME/scratch-cuw/T/man
        $HOME/scratch-cuw/T/i386--netbsdelf
        $HOME/scratch-cuw/T/include
        $HOME/scratch-cuw/T/libexec
        $HOME/scratch-cuw/T/armeb--netbsdelf

Dave

-- 
David Young             OJC Technologies
dyoung at ojctech.com      Urbana, IL * (217) 278-3933