That is exactly what I was complaining about. Apparently when the SB creates the duplicate stack, it uses that path and modifies the original mainstack if you try to build again. Now I only build for one platform, and then I quit and relaunch for each build operation. That keeps my original stackfile paths from becoming corrupted.
Bob S > On Feb 5, 2018, at 22:35 , Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I'll spare you the step by step of all the weirdness I'm seeing (the > duplicate stack warning about stacks in a "Windows" directory that doesn't > exist, or the error dialog at the end that just displays raw error data, and > everything in between), and just get to what I think is the point: _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
