No, the delay is almost constant with this stack and after the delay of (most times) 1:40 min the, message „checking directory exists“ pops up again, as if there was a "time out" at the first try and then it takes only the standard 2-3 seconds, before the process continous. Tiemo
-----Ursprüngliche Nachricht----- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Mike Bonner via use-livecode Gesendet: Mittwoch, 5. April 2017 14:07 An: How to use LiveCode <use-livecode@lists.runrev.com> Cc: Mike Bonner <bonnm...@gmail.com> Betreff: Re: standalone build: "checking directory exists" takes up to 2 min If you build a standalone for your app, and immediately build again, is the second build faster? If so, it would make me think that the server spins some of its drives down and it takes a second or two to spin them back up. Even if the drive you are accessing doesn't spin down, if others on the server DO, I think there can be a short delay while it spins other drives back up to speed. On Wed, Apr 5, 2017 at 2:01 AM, Tiemo Hollmann TB via use-livecode < use-livecode@lists.runrev.com> wrote: > Hello, > > LC 8.1 – 8.1.4 and 9.0. I am on Win 10. The stack file source as well > as the standalone build directory is located on a windows server. > > When building a standalone für my (complex) main application on the > server dir the standalone builder progress stopps at the stage > „checking directory exists“ for 1-2 minutes. > > Building a standalone for the same stack in a local dir, it just takes > seconds. Now I could say, ok, LiveCode has to handle some network > security permissions or such for 2 mins. (btw. It is the same using a > UNC path or mapped drive) > > But building any other (smaller) stack or a new test stack on the > server dir takes only seconds. > > What stack parameters have an impact on “checking the build > directory”? OK, since this affects me only when building a standalone > and doesn’t seem to have any impact on the finished standalone, I > probably have to put into my trash of weired issues. > > Or any idea I can check for? > > Tiemo > > > > > > > > > > _______________________________________________ > 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 > _______________________________________________ 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 _______________________________________________ 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
