Thanks to all who responded and please excuse that i answer so late. I´ve checked all you suggestions. But nothing solved my problem.
I then opened the stack in LC 9.0.1 and was able to built a standalone without a problem. After that i was also able to create a standalone again in LC 9.0.2 w/o a problem. Whatever this has caused it, it´s not there anymore and all is fine again. Very strange. Matthias > Am 15.02.2019 um 16:55 schrieb Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>>: > > I just had an, "AHA!" moment. > > Bob S > > >> On Feb 14, 2019, at 10:15 , Richard Gaskin via use-livecode >> <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> wrote: >> >> The example there is uses two paths that differ based on the Unix shortcut >> of "~" for the user's home folder, e.g.: >> >> /home/matthias/workfolder/somestack.livecode >> >> ...vs: >> >> ~/workfolder/somestack.livecode >> >> Both paths refer to the same file system object, but apparently the engine >> maintains its handle to the file based on the given path rather than the >> fully resolved path, so it believes those are two different files in which >> the stack objects happen to have the same name. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com <mailto: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 _______________________________________________ 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
