OpenEuphoria

Re: Building from Euphoria repository

• Posted by mattlewis (admin) Jan 16, 2012
• 1118 views

Which branch are you working from? When I get unexpected stuff like that, it's usually from reusing a build directory from another branch or something, and running "make cleann" usually clears that up. Also, if you switch branches, you need to run the configure script again.

I keep different build directories for various branches and configurations. Recently, I've been using these:

32/ 
4.0/ 
64/ 
mingw32/ 
mingw64/ 
struct/sixtyfour 
struct/thirtytwo 
struct/win/sixtyfour 
struct/win/thirtytwo 

I have shell scripts that optionally update to a particular branch and run configure for me so that I get a consistent setup. Here's what my configstruct script looks like:

#!/bin/sh 
 
BUILDBASE=../struct 
BUILDBITS=/sixtyfour 
ARCH=x86.64 
while [ "$1" != "" ]; do 
        case $1 in 
                up*) 
                        hg up -C struct 
                        ;; 
 
                32*) 
                        ARCH=x86 
                        BUILDBITS=/thirtytwo 
                        ;; 
                win*) 
                        BUILDOS=/win 
        esac 
 
        shift 
done 
 
if [ "$BUILDOS" = "/win" ]; then 
        if [ "$ARCH" = "x86" ]; then 
                HOST="--cc-prefix i686-w64-mingw32-" 
        else 
                HOST="--cc-prefix x86_64-w64-mingw32-" 
        fi 
        PLAT="--plat=WINDOWS" 
fi 
 
./configure --build $BUILDBASE$BUILDOS$BUILDBITS --arch $ARCH $HOST $PLAT 
 

I have similar scripts for the 4.0 branch and the default (i.e., trunk, 4.1) branch.

Matt