[M3devel] bootstrap and Compiler.i3 change?

[Olaf Wagner]

Quoting Jay <jayk123 at hotmail.com>:

> What is the deal with building and the Compiler.i3 change?
> I had difficulty here, despite using upgrade.py and upgrade.sh that   
> have gotten things correct before (and I understand what they are   
> doing).
>
> I ended up doing something that didn't make sense to me and I got   
> past it, but then I had another problem.
>
> I ran ugprade until it failed -- it built/shipped compiler and   
> m3core; then libm3 fails.
> Then I think I ran either do-cm3-front.py, or I rolled back tools   
> and then ran do-cm3-front.py.
>
> I understand the change to Compiler.i3. It should be ok. It is in   
> m3core, build/ship that and then build libm3 should work, right?
>
> The code that is actually using Compiler.i3 is for fairly unused   
> targets, however it actually sets a good example I intend to follow.
> Rather than probing for what Pathname.Join returns a\b or a/b, you   
> can check Compiler.Platform or whatnot directly.
> But if there are more uses of this, outside m3core, this build   
> problem needs to be understood.
> Probably I'm just missing something?

Are you sure you didn't just forget to clean everything after
building the first cm3? upgrade.sh should do it right though...

My own regression tests at home seem to have recoverd from the
target extension without further help (except for the new required
libraries), too, so I'm quite sure that upgrade.sh does the right
things.

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