[M3devel] strange code in scripts

[Olaf Wagner]

I assume you're talking about make-bin-dist-min.sh.

Quoting Jay K <jay.krell at cornell.edu>:

> This sequence is odd:
>
> [ ${TARGET} != NT386 ] && "${ROOT}/scripts/do-pkg.sh" buildship

> echo "${ROOT}/scripts/do-cm3-${DIST}.sh" buildlocal
> "${ROOT}/scripts/do-cm3-${DIST}.sh" buildlocal || exit 1
>
> header "stage 4: installing libraries using new cm3 compiler"
> echo "${ROOT}/scripts/do-cm3-${DIST}.sh" buildglobal
> "${ROOT}/scripts/do-cm3-${DIST}.sh" buildglobal || exit 1
>
> The first line doesn't do anything.
> In the logs you can see it just says "no packages".

Have a look at
    
http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/scripts/make-bin-dist-min.sh?annotate=1.42.2.5

This line is from Tony with the following comment:

    
http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/scripts/make-bin-dist-min.sh#rev1.24

It should be completely removed.

> I don't understand why buildlocal + buildglobal.

This is (a) a reasonable precaution, as building local will test
everything before shipping it, and (b) it will show us if both
building against the workspace and against the global package pool
succeeds. Missing/wrong overrides have often enough broken the
released packages.

> Is that, um, to delete the .M3OVERRIDES files, so that "On the other side",
> ship won't refuse?
Of course, if we'd only build with overrides we couldn't ship
anything. The second run will mostly just change the .M3SHIP files
(and relink some programs, because M3 is usually not smart enough
to avoid that -- but the discussion about dynamic linking has shown
that that can be viewed as a feature :-).

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194