Hello David, This warning is thrown only if the stack (or a substack) is password protected. If a stack is password protected, then automatic inclusions are not expected to work.
If the stack is not password-protected, and you still get that error, then this might be a bug. Could you file a report and attach this stack to the report, so as we investigate this further? Kind regards, Panos -- On Tue, 23 Jun 2020 at 14:53, David V Glasgow via use-livecode < use-livecode@lists.runrev.com> wrote: > I never saw mail below reach the list, and received no replies, so I am > trying again. > > Aside from thanks to Panos, I reported a new problem with an error “could > not auto-detect inclusions or security categories because stack is password > protected” when I don’t think it is password protected. I tried setting > the password of the stack to empty, with no change to error. Stack has no > sub stacks. I suppose I could select inclusions manually, but it would be > nice to know what is going on. > > Cheers, > > David G > > > Begin forwarded message: > > > > From: David V Glasgow <dvglas...@gmail.com> > > Subject: Re: Build problems with 9.6 [mostly fixed] > > Date: 20 June 2020 at 3:24:06 pm BST > > To: How to use LiveCode <use-livecode@lists.runrev.com> > > > > Updating to Xcode 10.1 did the trick, so it looks like something had > gone awry with the previous Xcode install. I really hadn’t appreciated > that there is any LC dependency on Xcode with respect to desktop builds. > > > > Thanks for the advice Panos. > > > > I now get a build, but with the warning “could not auto-detect > inclusions or security categories because stack is password protected” > > > > This didn’t happen in 7.x or 8.x, and as far as I know, the stack is not > encrypted. I have seen a discussion of the same message with a script only > stack, but I couldn’t see any real connection with my case. > > > > I tried > > > > set the password of stack "ISOPtex" to empty > > > > in the message box, but still got the same message on build. > > > > Any suggestions anyone? > > > > Thanks David G > > > >> On 16 Jun 2020, at 1:11 pm, panagiotis merakos via use-livecode < > use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> > wrote: > >> > >> Hello David, > >> > >> Sorry about that, I should have mentioned that > "/path/to/your/Xcode.app" is > >> a placeholder for the actual path to your Xcode.app. So for example if > you > >> have installed Xcode into your Applications folder, then the above > command > >> should read: > >> > >> sudo xcode-select -s /Applications/Xcode.app > >> > >> *>>>>>>>Launching X-Code I get an unknown error with a long field of > text > >> in the console. Want to see it? * > >> > >> If the previous command does not make any difference, then yes please :) > >> > >> Which version of Xcode have you installed BTW? > >> > >> Kind regards, > >> Panos > >> -- > >> > >> On Tue, 16 Jun 2020 at 15:04, David V Glasgow via use-livecode < > >> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> > wrote: > >> > >>> > >>> > >>>> On 15 Jun 2020, at 5:04 pm, panagiotis merakos via use-livecode < > >>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> > wrote: > >>>> > >>>> Hello David, > >>>> > >>>> Where have you installed Xcode? > >>>> > >>>> Could you try this in a terminal: > >>>> > >>>> sudo xcode-select -s /path/to/your/Xcode.app > >>> > >>> > >>> In response to this I get > >>> > >>> xcode-select: error: invalid developer directory > '/path/to/your/Xcode.app' > >>> > >>> Launching X-Code I get an unknown error with a long field of text in > the > >>> console. Want to see it? > >>> > >>> Cheers, > >>> > >>> David G > >>> > >>>> > >>>> Also, it might be worth opening Xcode first (in case you have never > >>> opened > >>>> it). > >>>> > >>>> Kind regards, > >>>> Panos > >>>> -- > >>>> > >>>> On Mon, 15 Jun 2020 at 18:12, David V Glasgow via use-livecode < > >>>> use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> > wrote: > >>>> > >>>>> Hi Panos, > >>>>> > >>>>> The tools appeared to install, but the error(s) still appear, and the > >>>>> standalone isn’t saved. > >>>>> > >>>>> Best wishes, > >>>>> > >>>>> David G > >>> > >>> _______________________________________________ > >>> 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 <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 > _______________________________________________ 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