subject:"Unable to build for Mac\: adding ad\-hoc signature failed"

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Mark Smith via use-livecode

Very useful info Matthias. Thanks for posting.

Mark

> On 9 Aug 2023, at 2:41 pm, matthias rebbe via use-livecode 
>  wrote:
> 
> Every version of Xocde come with it own version of command line tools. 
> If you are just creating macOS standalones then you just need the command 
> line tools.
> But if you are also planning to create iOS apps then you'll need the complete 
> Xcode package.
> 
> To install just the command line tools run the following command from terminal
> 
> xcode-select --install
> 
> This should download and install the most current version of command line 
> tools or better said, the most current version that is available for your 
> installed macOS.
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 14:40 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I wonder. I don’t have Xcode installed on this machine. Does installing 
>> Xcode change the command-line tools? Maybe those tools that are the default 
>> work a little differently.
>> 
>> I’m willing to install Xcode, but before that maybe I can provide some 
>> information (such as version) about any particular tools.
>> 
>> Dar
>> 
>>> On Aug 9, 2023, at 6:17 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Whoops, I sent the most recent before I saw that Panos had responded.
>>> 
>>> Panos, yes, a build to the network drive with a minimal stack has the 
>>> error. This minimal stack has a name of Test, no inclusions, no copy files.
>>> 
>>> The drive provides SMB, AFP and NFS services.
>>> 
>>> Dar
>>> 
 On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
  wrote:
 
 I don’t know what I did. Building for Mac Intel works just fine. I’ll add 
 my inclusions and such.
 
 I don’t have Xcode on this system. Perhaps there are some command line 
 tools suitable that come with macOS. 
 
 I still feel defensive that Mac said “detritus”. ;-)
 
> On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
>  wrote:
> 
> Hi Dar,
> 
> just a shot in the dark
> 
> For some time now Livecode does an adhoc code signing when creating a 
> macOS standalone. So therefore the Xcode command line tools have to be 
> installed.
> In case you have installed more than one versions of Xcode on your 
> system, did you select in Xcode preferences the correct Xcode standalone 
> tools that shall be used?
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I have a clue. I changed the build destination to a drive on my Mac. 
>> That seemed to have gotten past that error and I ran into other errors.
>> 
>> I guess building expects a drive on my Mac. And my Mac returns a bogus 
>> error message. 
>> 
>> I suggest one of these as an improvement to the build operation:
>> 
>> *   Complain and advise when the target is on a network drive.
>> *   Build the standalone in a temporary location on the local drive and 
>> then copy to the network drive when the target is on a network drive.
>> 
>> I got past that error, but now I am running into others. They look 
>> familiar. I think the problem is that I’m not remembering the magic 
>> steps related to saving, purging and so on. I’m not sure, since I can 
>> build for Windows. (I can probably stumble through what I did long, long 
>> ago, but might figure it out faster.) 
>> 
>> Suggestion:
>> 
>> *   I should not have to remember.
>> 
>> Thanks, everybody, for your help!
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Oh, and I’m building from a network drive.
>>> 
>>> 
 On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
  wrote:
 
 xcode-select -p
 /Library/Developer/CommandLineTools
 
> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I removed all inclusions. I opted to remove all profiles, probably 
> none. There are no Copy Files. I’m building for Intel only. 
> 
> For PLIST I chose Chose a PLIST and then clicked Use None.
> 
> I set my bundle identifier and have not changed that among my 
> attempts. I left all of the other Version Information as default. 
> 
> I have no Icons added.
> 
> I get the same error.
> 
> Dar
> 
>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> Signing happens after the app is built and is a manual process, so 
>> yours isn't signed /notarized yet. But unsigned apps run on the 
>> development machine anyway, so I'd say you built the app 
>> successfully.
>> 
>> --
>> Jacqueline Landman Gay |

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread matthias rebbe via use-livecode

And like the links says that Mark posted.

For iOS standalones every Livecode version supports a special Xcode version 
according to the installed macOS.
You'll find the information which works for your installed LC version also in 
the release notes of your LC version.
You'll find the release notes under the Help menu in LC.



> Am 09.08.2023 um 15:41 schrieb matthias_livecode_150...@m-r-d.de:
> 
> Every version of Xocde come with it own version of command line tools. 
> If you are just creating macOS standalones then you just need the command 
> line tools.
> But if you are also planning to create iOS apps then you'll need the complete 
> Xcode package.
> 
> To install just the command line tools run the following command from terminal
> 
> xcode-select --install
> 
> This should download and install the most current version of command line 
> tools or better said, the most current version that is available for your 
> installed macOS.
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 14:40 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I wonder. I don’t have Xcode installed on this machine. Does installing 
>> Xcode change the command-line tools? Maybe those tools that are the default 
>> work a little differently.
>> 
>> I’m willing to install Xcode, but before that maybe I can provide some 
>> information (such as version) about any particular tools.
>> 
>> Dar
>> 
>>> On Aug 9, 2023, at 6:17 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Whoops, I sent the most recent before I saw that Panos had responded.
>>> 
>>> Panos, yes, a build to the network drive with a minimal stack has the 
>>> error. This minimal stack has a name of Test, no inclusions, no copy files.
>>> 
>>> The drive provides SMB, AFP and NFS services.
>>> 
>>> Dar
>>> 
 On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
  wrote:
 
 I don’t know what I did. Building for Mac Intel works just fine. I’ll add 
 my inclusions and such.
 
 I don’t have Xcode on this system. Perhaps there are some command line 
 tools suitable that come with macOS. 
 
 I still feel defensive that Mac said “detritus”. ;-)
 
> On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
>  wrote:
> 
> Hi Dar,
> 
> just a shot in the dark
> 
> For some time now Livecode does an adhoc code signing when creating a 
> macOS standalone. So therefore the Xcode command line tools have to be 
> installed.
> In case you have installed more than one versions of Xcode on your 
> system, did you select in Xcode preferences the correct Xcode standalone 
> tools that shall be used?
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I have a clue. I changed the build destination to a drive on my Mac. 
>> That seemed to have gotten past that error and I ran into other errors.
>> 
>> I guess building expects a drive on my Mac. And my Mac returns a bogus 
>> error message. 
>> 
>> I suggest one of these as an improvement to the build operation:
>> 
>> *   Complain and advise when the target is on a network drive.
>> *   Build the standalone in a temporary location on the local drive and 
>> then copy to the network drive when the target is on a network drive.
>> 
>> I got past that error, but now I am running into others. They look 
>> familiar. I think the problem is that I’m not remembering the magic 
>> steps related to saving, purging and so on. I’m not sure, since I can 
>> build for Windows. (I can probably stumble through what I did long, long 
>> ago, but might figure it out faster.) 
>> 
>> Suggestion:
>> 
>> *   I should not have to remember.
>> 
>> Thanks, everybody, for your help!
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Oh, and I’m building from a network drive.
>>> 
>>> 
 On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
  wrote:
 
 xcode-select -p
 /Library/Developer/CommandLineTools
 
> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I removed all inclusions. I opted to remove all profiles, probably 
> none. There are no Copy Files. I’m building for Intel only. 
> 
> For PLIST I chose Chose a PLIST and then clicked Use None.
> 
> I set my bundle identifier and have not changed that among my 
> attempts. I left all of the other Version Information as default. 
> 
> I have no Icons added.
> 
> I get the same error.
> 
> Dar
> 
>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> Signing happens after the app is

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread matthias rebbe via use-livecode

Every version of Xocde come with it own version of command line tools. 
If you are just creating macOS standalones then you just need the command line 
tools.
But if you are also planning to create iOS apps then you'll need the complete 
Xcode package.

To install just the command line tools run the following command from terminal

xcode-select --install

This should download and install the most current version of command line tools 
or better said, the most current version that is available for your installed 
macOS.

Regards,
Matthias


> Am 09.08.2023 um 14:40 schrieb Dar Scott via use-livecode 
> :
> 
> I wonder. I don’t have Xcode installed on this machine. Does installing Xcode 
> change the command-line tools? Maybe those tools that are the default work a 
> little differently.
> 
> I’m willing to install Xcode, but before that maybe I can provide some 
> information (such as version) about any particular tools.
> 
> Dar
> 
>> On Aug 9, 2023, at 6:17 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Whoops, I sent the most recent before I saw that Panos had responded.
>> 
>> Panos, yes, a build to the network drive with a minimal stack has the error. 
>> This minimal stack has a name of Test, no inclusions, no copy files.
>> 
>> The drive provides SMB, AFP and NFS services.
>> 
>> Dar
>> 
>>> On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> I don’t know what I did. Building for Mac Intel works just fine. I’ll add 
>>> my inclusions and such.
>>> 
>>> I don’t have Xcode on this system. Perhaps there are some command line 
>>> tools suitable that come with macOS. 
>>> 
>>> I still feel defensive that Mac said “detritus”. ;-)
>>> 
 On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
  wrote:
 
 Hi Dar,
 
 just a shot in the dark
 
 For some time now Livecode does an adhoc code signing when creating a 
 macOS standalone. So therefore the Xcode command line tools have to be 
 installed.
 In case you have installed more than one versions of Xcode on your system, 
 did you select in Xcode preferences the correct Xcode standalone tools 
 that shall be used?
 
 Regards,
 Matthias
 
 
> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
> :
> 
> I have a clue. I changed the build destination to a drive on my Mac. That 
> seemed to have gotten past that error and I ran into other errors.
> 
> I guess building expects a drive on my Mac. And my Mac returns a bogus 
> error message. 
> 
> I suggest one of these as an improvement to the build operation:
> 
> *   Complain and advise when the target is on a network drive.
> *   Build the standalone in a temporary location on the local drive and 
> then copy to the network drive when the target is on a network drive.
> 
> I got past that error, but now I am running into others. They look 
> familiar. I think the problem is that I’m not remembering the magic steps 
> related to saving, purging and so on. I’m not sure, since I can build for 
> Windows. (I can probably stumble through what I did long, long ago, but 
> might figure it out faster.) 
> 
> Suggestion:
> 
> *   I should not have to remember.
> 
> Thanks, everybody, for your help!
> 
> Dar
> 
>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Oh, and I’m building from a network drive.
>> 
>> 
>>> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> xcode-select -p
>>> /Library/Developer/CommandLineTools
>>> 
 On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
  wrote:
 
 I removed all inclusions. I opted to remove all profiles, probably 
 none. There are no Copy Files. I’m building for Intel only. 
 
 For PLIST I chose Chose a PLIST and then clicked Use None.
 
 I set my bundle identifier and have not changed that among my 
 attempts. I left all of the other Version Information as default. 
 
 I have no Icons added.
 
 I get the same error.
 
 Dar
 
> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Signing happens after the app is built and is a manual process, so 
> yours isn't signed /notarized yet. But unsigned apps run on the 
> development machine anyway, so I'd say you built the app successfully.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> I have, but I don’t do any signing or notarizing. If that happens 
>> transparently, then it’s working

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Mark Smith via use-livecode

Hi Dar,

> Does installing Xcode change the command-line tools? 

I think it should. Others will correct me if I’m wrong. 

> I’m willing to install Xcode, but before that maybe I can provide some 
> information (such as version) about any particular tools.


I don’t know if this is of any help but there is a list of LC versions and 
compatible/required Xcode versions here… (in the first entry on the page)

https://livecode.com/resources/support/ask-a-question/ 


Mark


> On 9 Aug 2023, at 1:40 pm, Dar Scott via use-livecode 
>  wrote:
> 
> I wonder. I don’t have Xcode installed on this machine. Does installing Xcode 
> change the command-line tools? Maybe those tools that are the default work a 
> little differently.
> 
> I’m willing to install Xcode, but before that maybe I can provide some 
> information (such as version) about any particular tools.
> 
> Dar
> 
>> On Aug 9, 2023, at 6:17 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Whoops, I sent the most recent before I saw that Panos had responded.
>> 
>> Panos, yes, a build to the network drive with a minimal stack has the error. 
>> This minimal stack has a name of Test, no inclusions, no copy files.
>> 
>> The drive provides SMB, AFP and NFS services.
>> 
>> Dar
>> 
>>> On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> I don’t know what I did. Building for Mac Intel works just fine. I’ll add 
>>> my inclusions and such.
>>> 
>>> I don’t have Xcode on this system. Perhaps there are some command line 
>>> tools suitable that come with macOS. 
>>> 
>>> I still feel defensive that Mac said “detritus”. ;-)
>>> 
 On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
  wrote:
 
 Hi Dar,
 
 just a shot in the dark
 
 For some time now Livecode does an adhoc code signing when creating a 
 macOS standalone. So therefore the Xcode command line tools have to be 
 installed.
 In case you have installed more than one versions of Xcode on your system, 
 did you select in Xcode preferences the correct Xcode standalone tools 
 that shall be used?
 
 Regards,
 Matthias
 
 
> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
> :
> 
> I have a clue. I changed the build destination to a drive on my Mac. That 
> seemed to have gotten past that error and I ran into other errors.
> 
> I guess building expects a drive on my Mac. And my Mac returns a bogus 
> error message. 
> 
> I suggest one of these as an improvement to the build operation:
> 
> *   Complain and advise when the target is on a network drive.
> *   Build the standalone in a temporary location on the local drive and 
> then copy to the network drive when the target is on a network drive.
> 
> I got past that error, but now I am running into others. They look 
> familiar. I think the problem is that I’m not remembering the magic steps 
> related to saving, purging and so on. I’m not sure, since I can build for 
> Windows. (I can probably stumble through what I did long, long ago, but 
> might figure it out faster.) 
> 
> Suggestion:
> 
> *   I should not have to remember.
> 
> Thanks, everybody, for your help!
> 
> Dar
> 
>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Oh, and I’m building from a network drive.
>> 
>> 
>>> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> xcode-select -p
>>> /Library/Developer/CommandLineTools
>>> 
 On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
  wrote:
 
 I removed all inclusions. I opted to remove all profiles, probably 
 none. There are no Copy Files. I’m building for Intel only. 
 
 For PLIST I chose Chose a PLIST and then clicked Use None.
 
 I set my bundle identifier and have not changed that among my 
 attempts. I left all of the other Version Information as default. 
 
 I have no Icons added.
 
 I get the same error.
 
 Dar
 
> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Signing happens after the app is built and is a manual process, so 
> yours isn't signed /notarized yet. But unsigned apps run on the 
> development machine anyway, so I'd say you built the app successfully.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> I have, but I don’t do any signing or notarizing. If that happens 
>> transparently, then it’s working for me.

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode

I wonder. I don’t have Xcode installed on this machine. Does installing Xcode 
change the command-line tools? Maybe those tools that are the default work a 
little differently.

I’m willing to install Xcode, but before that maybe I can provide some 
information (such as version) about any particular tools.

Dar

> On Aug 9, 2023, at 6:17 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Whoops, I sent the most recent before I saw that Panos had responded.
> 
> Panos, yes, a build to the network drive with a minimal stack has the error. 
> This minimal stack has a name of Test, no inclusions, no copy files.
> 
> The drive provides SMB, AFP and NFS services.
> 
> Dar
> 
>> On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> I don’t know what I did. Building for Mac Intel works just fine. I’ll add my 
>> inclusions and such.
>> 
>> I don’t have Xcode on this system. Perhaps there are some command line tools 
>> suitable that come with macOS. 
>> 
>> I still feel defensive that Mac said “detritus”. ;-)
>> 
>>> On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
>>>  wrote:
>>> 
>>> Hi Dar,
>>> 
>>> just a shot in the dark
>>> 
>>> For some time now Livecode does an adhoc code signing when creating a macOS 
>>> standalone. So therefore the Xcode command line tools have to be installed.
>>> In case you have installed more than one versions of Xcode on your system, 
>>> did you select in Xcode preferences the correct Xcode standalone tools that 
>>> shall be used?
>>> 
>>> Regards,
>>> Matthias
>>> 
>>> 
 Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
 :

 I have a clue. I changed the build destination to a drive on my Mac. That 
 seemed to have gotten past that error and I ran into other errors.

 I guess building expects a drive on my Mac. And my Mac returns a bogus 
 error message. 

 I suggest one of these as an improvement to the build operation:

 *   Complain and advise when the target is on a network drive.
 *   Build the standalone in a temporary location on the local drive and 
 then copy to the network drive when the target is on a network drive.

 I got past that error, but now I am running into others. They look 
 familiar. I think the problem is that I’m not remembering the magic steps 
 related to saving, purging and so on. I’m not sure, since I can build for 
 Windows. (I can probably stumble through what I did long, long ago, but 
 might figure it out faster.) 

 Suggestion:

 *   I should not have to remember.

 Thanks, everybody, for your help!

 Dar

> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Oh, and I’m building from a network drive.
> 
> 
>> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> xcode-select -p
>> /Library/Developer/CommandLineTools
>> 
>>> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> I removed all inclusions. I opted to remove all profiles, probably 
>>> none. There are no Copy Files. I’m building for Intel only. 
>>> 
>>> For PLIST I chose Chose a PLIST and then clicked Use None.
>>> 
>>> I set my bundle identifier and have not changed that among my attempts. 
>>> I left all of the other Version Information as default. 
>>> 
>>> I have no Icons added.
>>> 
>>> I get the same error.
>>> 
>>> Dar
>>> 
 On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
  wrote:

 Signing happens after the app is built and is a manual process, so 
 yours isn't signed /notarized yet. But unsigned apps run on the 
 development machine anyway, so I'd say you built the app successfully.

 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software | http://www.hyperactivesw.com
 On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
  wrote:

> I have, but I don’t do any signing or notarizing. If that happens 
> transparently, then it’s working for me.
> 
> Bob S
> 
> 
>> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Thanks, Jacque!
>> 
>> That gives me a clue. I will try to get more info on this.
>> 
>> However, that note shows how to delete the offending resource using 
>> the xattr tool, but I have no app to point it to. LiveCode did not 
>> build anything.
>> 
>> I’m willing to try some magic values in Standalone Application 
>> Settings.
>>  I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>>  I’m on macOS Ventura.
>> 
>> Has anyone successfully built a Mac application

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode

Whoops, I sent the most recent before I saw that Panos had responded.

Panos, yes, a build to the network drive with a minimal stack has the error. 
This minimal stack has a name of Test, no inclusions, no copy files.

The drive provides SMB, AFP and NFS services.

Dar

> On Aug 9, 2023, at 5:55 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I don’t know what I did. Building for Mac Intel works just fine. I’ll add my 
> inclusions and such.
> 
> I don’t have Xcode on this system. Perhaps there are some command line tools 
> suitable that come with macOS. 
> 
> I still feel defensive that Mac said “detritus”. ;-)
> 
>> On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
>>  wrote:
>> 
>> Hi Dar,
>> 
>> just a shot in the dark
>> 
>> For some time now Livecode does an adhoc code signing when creating a macOS 
>> standalone. So therefore the Xcode command line tools have to be installed.
>> In case you have installed more than one versions of Xcode on your system, 
>> did you select in Xcode preferences the correct Xcode standalone tools that 
>> shall be used?
>> 
>> Regards,
>> Matthias
>> 
>> 
>>> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
>>> :
>>> 
>>> I have a clue. I changed the build destination to a drive on my Mac. That 
>>> seemed to have gotten past that error and I ran into other errors.
>>> 
>>> I guess building expects a drive on my Mac. And my Mac returns a bogus 
>>> error message. 
>>> 
>>> I suggest one of these as an improvement to the build operation:
>>> 
>>> *   Complain and advise when the target is on a network drive.
>>> *   Build the standalone in a temporary location on the local drive and 
>>> then copy to the network drive when the target is on a network drive.
>>> 
>>> I got past that error, but now I am running into others. They look 
>>> familiar. I think the problem is that I’m not remembering the magic steps 
>>> related to saving, purging and so on. I’m not sure, since I can build for 
>>> Windows. (I can probably stumble through what I did long, long ago, but 
>>> might figure it out faster.) 
>>> 
>>> Suggestion:
>>> 
>>> *   I should not have to remember.
>>> 
>>> Thanks, everybody, for your help!
>>> 
>>> Dar
>>> 
 On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
  wrote:
 
 Oh, and I’m building from a network drive.
 
 
> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>  wrote:
> 
> xcode-select -p
> /Library/Developer/CommandLineTools
> 
>> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> I removed all inclusions. I opted to remove all profiles, probably none. 
>> There are no Copy Files. I’m building for Intel only. 
>> 
>> For PLIST I chose Chose a PLIST and then clicked Use None.
>> 
>> I set my bundle identifier and have not changed that among my attempts. 
>> I left all of the other Version Information as default. 
>> 
>> I have no Icons added.
>> 
>> I get the same error.
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>>  wrote:
>>> 
>>> Signing happens after the app is built and is a manual process, so 
>>> yours isn't signed /notarized yet. But unsigned apps run on the 
>>> development machine anyway, so I'd say you built the app successfully.
>>> 
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
 I have, but I don’t do any signing or notarizing. If that happens 
 transparently, then it’s working for me.
 
 Bob S
 
 
> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using 
> the xattr tool, but I have no app to point it to. LiveCode did not 
> build anything.
> 
> I’m willing to try some magic values in Standalone Application 
> Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode

I don’t know what I did. Building for Mac Intel works just fine. I’ll add my 
inclusions and such.

I don’t have Xcode on this system. Perhaps there are some command line tools 
suitable that come with macOS. 

I still feel defensive that Mac said “detritus”. ;-)

> On Aug 8, 2023, at 5:13 PM, matthias rebbe via use-livecode 
>  wrote:
> 
> Hi Dar,
> 
> just a shot in the dark
> 
> For some time now Livecode does an adhoc code signing when creating a macOS 
> standalone. So therefore the Xcode command line tools have to be installed.
> In case you have installed more than one versions of Xcode on your system, 
> did you select in Xcode preferences the correct Xcode standalone tools that 
> shall be used?
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I have a clue. I changed the build destination to a drive on my Mac. That 
>> seemed to have gotten past that error and I ran into other errors.
>> 
>> I guess building expects a drive on my Mac. And my Mac returns a bogus error 
>> message. 
>> 
>> I suggest one of these as an improvement to the build operation:
>> 
>> *   Complain and advise when the target is on a network drive.
>> *   Build the standalone in a temporary location on the local drive and then 
>> copy to the network drive when the target is on a network drive.
>> 
>> I got past that error, but now I am running into others. They look familiar. 
>> I think the problem is that I’m not remembering the magic steps related to 
>> saving, purging and so on. I’m not sure, since I can build for Windows. (I 
>> can probably stumble through what I did long, long ago, but might figure it 
>> out faster.) 
>> 
>> Suggestion:
>> 
>> *   I should not have to remember.
>> 
>> Thanks, everybody, for your help!
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Oh, and I’m building from a network drive.
>>> 
>>> 
 On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
  wrote:
 
 xcode-select -p
 /Library/Developer/CommandLineTools
 
> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I removed all inclusions. I opted to remove all profiles, probably none. 
> There are no Copy Files. I’m building for Intel only. 
> 
> For PLIST I chose Chose a PLIST and then clicked Use None.
> 
> I set my bundle identifier and have not changed that among my attempts. I 
> left all of the other Version Information as default. 
> 
> I have no Icons added.
> 
> I get the same error.
> 
> Dar
> 
>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> Signing happens after the app is built and is a manual process, so yours 
>> isn't signed /notarized yet. But unsigned apps run on the development 
>> machine anyway, so I'd say you built the app successfully.
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>  wrote:
>> 
>>> I have, but I don’t do any signing or notarizing. If that happens 
>>> transparently, then it’s working for me.
>>> 
>>> Bob S
>>> 
>>> 
 On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
  wrote:
 
 Thanks, Jacque!
 
 That gives me a clue. I will try to get more info on this.
 
 However, that note shows how to delete the offending resource using 
 the xattr tool, but I have no app to point it to. LiveCode did not 
 build anything.
 
 I’m willing to try some magic values in Standalone Application 
 Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.
 
 Has anyone successfully built a Mac application recently?
 
 Dar
 
> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> This might help:
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>  wrote:
> 
>> I’m having trouble building an application for Mac Intel.
>> 
>> The first time LiveCode crashed.
>> 
>> Subsequent times, I get this error:
>> There was an error while saving the standalone application
>> Adding ad-hoc signature failed with error:
>> /…/myProgram.app:
>> Replacing existing signature
>> /…/myProgram.app:
>> Resource for, Finder information, or similar detritus not
>> Allowed
>>

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread panagiotis m via use-livecode

Hello Dar,

I can successfully build a Mac standalone in a network drive.

The error you are getting indicates that the app the standalone builder
tries to codesign, has some extended attributes. This is strange, because
the standalone builder does this very thing (i.e. it clears the extended
attributes) just before the codesign command.

I am wondering - do you get the same error when trying to build a
standalone from a new simple stack? Or does that happen only with a
specific stack? If the latter, does this stack contain anything in the Copy
Files?

Kind regards,
Panos

On Wed, 9 Aug 2023 at 08:33, matthias rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Forgot my answer, i just saw your post that your error where caused
> because of building to a network drive.
>
> I had similar problems btw. in the past when building to a dropbox folder
> or a folder that was synchronized with iCloud.
>
> Regards,
> Matthias
>
>
>
> > Am 09.08.2023 um 01:13 schrieb matthias_livecode_150...@m-r-d.de:
> >
> > Hi Dar,
> >
> > just a shot in the dark
> >
> > For some time now Livecode does an adhoc code signing when creating a
> macOS standalone. So therefore the Xcode command line tools have to be
> installed.
> > In case you have installed more than one versions of Xcode on your
> system, did you select in Xcode preferences the correct Xcode standalone
> tools that shall be used?
> >
> > Regards,
> > Matthias
> >
> >
> >> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode <
> use-livecode@lists.runrev.com>:
> >>
> >> I have a clue. I changed the build destination to a drive on my Mac.
> That seemed to have gotten past that error and I ran into other errors.
> >>
> >> I guess building expects a drive on my Mac. And my Mac returns a bogus
> error message.
> >>
> >> I suggest one of these as an improvement to the build operation:
> >>
> >> *   Complain and advise when the target is on a network drive.
> >> *   Build the standalone in a temporary location on the local drive and
> then copy to the network drive when the target is on a network drive.
> >>
> >> I got past that error, but now I am running into others. They look
> familiar. I think the problem is that I’m not remembering the magic steps
> related to saving, purging and so on. I’m not sure, since I can build for
> Windows. (I can probably stumble through what I did long, long ago, but
> might figure it out faster.)
> >>
> >> Suggestion:
> >>
> >> *   I should not have to remember.
> >>
> >> Thanks, everybody, for your help!
> >>
> >> Dar
> >>
> >>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> Oh, and I’m building from a network drive.
> >>>
> >>>
>  On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>  xcode-select -p
>  /Library/Developer/CommandLineTools
> 
> > On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > I removed all inclusions. I opted to remove all profiles, probably
> none. There are no Copy Files. I’m building for Intel only.
> >
> > For PLIST I chose Chose a PLIST and then clicked Use None.
> >
> > I set my bundle identifier and have not changed that among my
> attempts. I left all of the other Version Information as default.
> >
> > I have no Icons added.
> >
> > I get the same error.
> >
> > Dar
> >
> >> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> Signing happens after the app is built and is a manual process, so
> yours isn't signed /notarized yet. But unsigned apps run on the development
> machine anyway, so I'd say you built the app successfully.
> >>
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> HyperActive Software | http://www.hyperactivesw.com
> >> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >>> I have, but I don’t do any signing or notarizing. If that happens
> transparently, then it’s working for me.
> >>>
> >>> Bob S
> >>>
> >>>
>  On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>  Thanks, Jacque!
> 
>  That gives me a clue. I will try to get more info on this.
> 
>  However, that note shows how to delete the offending resource
> using the xattr tool, but I have no app to point it to. LiveCode did not
> build anything.
> 
>  I’m willing to try some magic values in Standalone Application
> Settings.
> I’m using LiveCode 9.6.9, but I’m willing to upgrade.
> I’m on macOS Ventura.
> 
>  Has anyone successfully built a Mac application recently?
> 
>  Dar
> 
> > On

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread matthias rebbe via use-livecode

Forgot my answer, i just saw your post that your error where caused because of 
building to a network drive.

I had similar problems btw. in the past when building to a dropbox folder or a 
folder that was synchronized with iCloud.

Regards,
Matthias



> Am 09.08.2023 um 01:13 schrieb matthias_livecode_150...@m-r-d.de:
> 
> Hi Dar,
> 
> just a shot in the dark
> 
> For some time now Livecode does an adhoc code signing when creating a macOS 
> standalone. So therefore the Xcode command line tools have to be installed.
> In case you have installed more than one versions of Xcode on your system, 
> did you select in Xcode preferences the correct Xcode standalone tools that 
> shall be used?
> 
> Regards,
> Matthias
> 
> 
>> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
>> :
>> 
>> I have a clue. I changed the build destination to a drive on my Mac. That 
>> seemed to have gotten past that error and I ran into other errors.
>> 
>> I guess building expects a drive on my Mac. And my Mac returns a bogus error 
>> message. 
>> 
>> I suggest one of these as an improvement to the build operation:
>> 
>> *   Complain and advise when the target is on a network drive.
>> *   Build the standalone in a temporary location on the local drive and then 
>> copy to the network drive when the target is on a network drive.
>> 
>> I got past that error, but now I am running into others. They look familiar. 
>> I think the problem is that I’m not remembering the magic steps related to 
>> saving, purging and so on. I’m not sure, since I can build for Windows. (I 
>> can probably stumble through what I did long, long ago, but might figure it 
>> out faster.) 
>> 
>> Suggestion:
>> 
>> *   I should not have to remember.
>> 
>> Thanks, everybody, for your help!
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Oh, and I’m building from a network drive.
>>> 
>>> 
 On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
  wrote:
 
 xcode-select -p
 /Library/Developer/CommandLineTools
 
> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I removed all inclusions. I opted to remove all profiles, probably none. 
> There are no Copy Files. I’m building for Intel only. 
> 
> For PLIST I chose Chose a PLIST and then clicked Use None.
> 
> I set my bundle identifier and have not changed that among my attempts. I 
> left all of the other Version Information as default. 
> 
> I have no Icons added.
> 
> I get the same error.
> 
> Dar
> 
>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> Signing happens after the app is built and is a manual process, so yours 
>> isn't signed /notarized yet. But unsigned apps run on the development 
>> machine anyway, so I'd say you built the app successfully.
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>  wrote:
>> 
>>> I have, but I don’t do any signing or notarizing. If that happens 
>>> transparently, then it’s working for me.
>>> 
>>> Bob S
>>> 
>>> 
 On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
  wrote:
 
 Thanks, Jacque!
 
 That gives me a clue. I will try to get more info on this.
 
 However, that note shows how to delete the offending resource using 
 the xattr tool, but I have no app to point it to. LiveCode did not 
 build anything.
 
 I’m willing to try some magic values in Standalone Application 
 Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.
 
 Has anyone successfully built a Mac application recently?
 
 Dar
 
> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> This might help:
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>  wrote:
> 
>> I’m having trouble building an application for Mac Intel.
>> 
>> The first time LiveCode crashed.
>> 
>> Subsequent times, I get this error:
>> There was an error while saving the standalone application
>> Adding ad-hoc signature failed with error:
>> /…/myProgram.app:
>> Replacing existing signature
>> /…/myProgram.app:
>> Resource for, Finder information, or similar detritus not
>> Allowed
>> 
>> I tried

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread matthias rebbe via use-livecode

Hi Dar,

just a shot in the dark

For some time now Livecode does an adhoc code signing when creating a macOS 
standalone. So therefore the Xcode command line tools have to be installed.
In case you have installed more than one versions of Xcode on your system, did 
you select in Xcode preferences the correct Xcode standalone tools that shall 
be used?

Regards,
Matthias


> Am 09.08.2023 um 00:45 schrieb Dar Scott via use-livecode 
> :
> 
> I have a clue. I changed the build destination to a drive on my Mac. That 
> seemed to have gotten past that error and I ran into other errors.
> 
> I guess building expects a drive on my Mac. And my Mac returns a bogus error 
> message. 
> 
> I suggest one of these as an improvement to the build operation:
> 
> *   Complain and advise when the target is on a network drive.
> *   Build the standalone in a temporary location on the local drive and then 
> copy to the network drive when the target is on a network drive.
> 
> I got past that error, but now I am running into others. They look familiar. 
> I think the problem is that I’m not remembering the magic steps related to 
> saving, purging and so on. I’m not sure, since I can build for Windows. (I 
> can probably stumble through what I did long, long ago, but might figure it 
> out faster.) 
> 
> Suggestion:
> 
> *   I should not have to remember.
> 
> Thanks, everybody, for your help!
> 
> Dar
> 
>> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Oh, and I’m building from a network drive.
>> 
>> 
>>> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> xcode-select -p
>>> /Library/Developer/CommandLineTools
>>> 
 On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
  wrote:
 
 I removed all inclusions. I opted to remove all profiles, probably none. 
 There are no Copy Files. I’m building for Intel only. 
 
 For PLIST I chose Chose a PLIST and then clicked Use None.
 
 I set my bundle identifier and have not changed that among my attempts. I 
 left all of the other Version Information as default. 
 
 I have no Icons added.
 
 I get the same error.
 
 Dar
 
> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Signing happens after the app is built and is a manual process, so yours 
> isn't signed /notarized yet. But unsigned apps run on the development 
> machine anyway, so I'd say you built the app successfully.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> I have, but I don’t do any signing or notarizing. If that happens 
>> transparently, then it’s working for me.
>> 
>> Bob S
>> 
>> 
>>> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Thanks, Jacque!
>>> 
>>> That gives me a clue. I will try to get more info on this.
>>> 
>>> However, that note shows how to delete the offending resource using the 
>>> xattr tool, but I have no app to point it to. LiveCode did not build 
>>> anything.
>>> 
>>> I’m willing to try some magic values in Standalone Application Settings.
>>> I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>>> I’m on macOS Ventura.
>>> 
>>> Has anyone successfully built a Mac application recently?
>>> 
>>> Dar
>>> 
 On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
  wrote:
 
 This might help:
 
 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software | http://www.hyperactivesw.com
 On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
  wrote:
 
> I’m having trouble building an application for Mac Intel.
> 
> The first time LiveCode crashed.
> 
> Subsequent times, I get this error:
> There was an error while saving the standalone application
> Adding ad-hoc signature failed with error:
> /…/myProgram.app:
> Replacing existing signature
> /…/myProgram.app:
> Resource for, Finder information, or similar detritus not
> Allowed
> 
> I tried fiddling with the PLIST settings without success.
> ___
> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Dar Scott via use-livecode

I have a clue. I changed the build destination to a drive on my Mac. That 
seemed to have gotten past that error and I ran into other errors.

I guess building expects a drive on my Mac. And my Mac returns a bogus error 
message. 

I suggest one of these as an improvement to the build operation:

*   Complain and advise when the target is on a network drive.
*   Build the standalone in a temporary location on the local drive and then 
copy to the network drive when the target is on a network drive.

I got past that error, but now I am running into others. They look familiar. I 
think the problem is that I’m not remembering the magic steps related to 
saving, purging and so on. I’m not sure, since I can build for Windows. (I can 
probably stumble through what I did long, long ago, but might figure it out 
faster.) 

Suggestion:

*   I should not have to remember.

Thanks, everybody, for your help!

Dar

> On Aug 8, 2023, at 10:47 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Oh, and I’m building from a network drive.
> 
> 
>> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> xcode-select -p
>> /Library/Developer/CommandLineTools
>> 
>>> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> I removed all inclusions. I opted to remove all profiles, probably none. 
>>> There are no Copy Files. I’m building for Intel only. 
>>> 
>>> For PLIST I chose Chose a PLIST and then clicked Use None.
>>> 
>>> I set my bundle identifier and have not changed that among my attempts. I 
>>> left all of the other Version Information as default. 
>>> 
>>> I have no Icons added.
>>> 
>>> I get the same error.
>>> 
>>> Dar
>>> 
 On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
  wrote:
 
 Signing happens after the app is built and is a manual process, so yours 
 isn't signed /notarized yet. But unsigned apps run on the development 
 machine anyway, so I'd say you built the app successfully.
 
 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software | http://www.hyperactivesw.com
 On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
  wrote:
 
> I have, but I don’t do any signing or notarizing. If that happens 
> transparently, then it’s working for me.
> 
> Bob S
> 
> 
>> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> Thanks, Jacque!
>> 
>> That gives me a clue. I will try to get more info on this.
>> 
>> However, that note shows how to delete the offending resource using the 
>> xattr tool, but I have no app to point it to. LiveCode did not build 
>> anything.
>> 
>> I’m willing to try some magic values in Standalone Application Settings.
>>  I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>>  I’m on macOS Ventura.
>> 
>> Has anyone successfully built a Mac application recently?
>> 
>> Dar
>> 
>>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>>  wrote:
>>> 
>>> This might help:
>>> 
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>>  wrote:
>>> 
 I’m having trouble building an application for Mac Intel.
 
 The first time LiveCode crashed.
 
 Subsequent times, I get this error:
 There was an error while saving the standalone application
 Adding ad-hoc signature failed with error:
 /…/myProgram.app:
 Replacing existing signature
 /…/myProgram.app:
 Resource for, Finder information, or similar detritus not
 Allowed
 
 I tried fiddling with the PLIST settings without success.
 ___
 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
> 
> ___
> use-livecode mailing list

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Mark Smith via use-livecode

I get this in response to Xcode-select -p

/Applications/Xcode 13.2.app/Contents/Developer


> On 8 Aug 2023, at 5:41 pm, Dar Scott via use-livecode 
>  wrote:
> 
> xcode-select -p
> /Library/Developer/CommandLineTools
> 
>> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> I removed all inclusions. I opted to remove all profiles, probably none. 
>> There are no Copy Files. I’m building for Intel only. 
>> 
>> For PLIST I chose Chose a PLIST and then clicked Use None.
>> 
>> I set my bundle identifier and have not changed that among my attempts. I 
>> left all of the other Version Information as default. 
>> 
>> I have no Icons added.
>> 
>> I get the same error.
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>>  wrote:
>>> 
>>> Signing happens after the app is built and is a manual process, so yours 
>>> isn't signed /notarized yet. But unsigned apps run on the development 
>>> machine anyway, so I'd say you built the app successfully.
>>> 
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
 I have, but I don’t do any signing or notarizing. If that happens 
 transparently, then it’s working for me.
 
 Bob S
 
 
> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using the 
> xattr tool, but I have no app to point it to. LiveCode did not build 
> anything.
> 
> I’m willing to try some magic values in Standalone Application Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble building an application for Mac Intel.
>>> 
>>> The first time LiveCode crashed.
>>> 
>>> Subsequent times, I get this error:
>>> There was an error while saving the standalone application
>>> Adding ad-hoc signature failed with error:
>>> /…/myProgram.app:
>>> Replacing existing signature
>>> /…/myProgram.app:
>>> Resource for, Finder information, or similar detritus not
>>> Allowed
>>> 
>>> I tried fiddling with the PLIST settings without success.
>>> ___
>>> 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
 
 ___
 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
>> 
>> 
> 
> ___
> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Dar Scott via use-livecode

Oh, and I’m building from a network drive.


> On Aug 8, 2023, at 10:41 AM, Dar Scott via use-livecode 
>  wrote:
> 
> xcode-select -p
> /Library/Developer/CommandLineTools
> 
>> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>>  wrote:
>> 
>> I removed all inclusions. I opted to remove all profiles, probably none. 
>> There are no Copy Files. I’m building for Intel only. 
>> 
>> For PLIST I chose Chose a PLIST and then clicked Use None.
>> 
>> I set my bundle identifier and have not changed that among my attempts. I 
>> left all of the other Version Information as default. 
>> 
>> I have no Icons added.
>> 
>> I get the same error.
>> 
>> Dar
>> 
>>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>>  wrote:
>>> 
>>> Signing happens after the app is built and is a manual process, so yours 
>>> isn't signed /notarized yet. But unsigned apps run on the development 
>>> machine anyway, so I'd say you built the app successfully.
>>> 
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
 I have, but I don’t do any signing or notarizing. If that happens 
 transparently, then it’s working for me.
 
 Bob S
 
 
> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using the 
> xattr tool, but I have no app to point it to. LiveCode did not build 
> anything.
> 
> I’m willing to try some magic values in Standalone Application Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble building an application for Mac Intel.
>>> 
>>> The first time LiveCode crashed.
>>> 
>>> Subsequent times, I get this error:
>>> There was an error while saving the standalone application
>>> Adding ad-hoc signature failed with error:
>>> /…/myProgram.app:
>>> Replacing existing signature
>>> /…/myProgram.app:
>>> Resource for, Finder information, or similar detritus not
>>> Allowed
>>> 
>>> I tried fiddling with the PLIST settings without success.
>>> ___
>>> 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
 
 ___
 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
>> 
>> 
> 
> ___
> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Dar Scott via use-livecode

xcode-select -p
/Library/Developer/CommandLineTools

> On Aug 8, 2023, at 10:19 AM, Dar Scott via use-livecode 
>  wrote:
> 
> I removed all inclusions. I opted to remove all profiles, probably none. 
> There are no Copy Files. I’m building for Intel only. 
> 
> For PLIST I chose Chose a PLIST and then clicked Use None.
> 
> I set my bundle identifier and have not changed that among my attempts. I 
> left all of the other Version Information as default. 
> 
> I have no Icons added.
> 
> I get the same error.
> 
> Dar
> 
>> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> Signing happens after the app is built and is a manual process, so yours 
>> isn't signed /notarized yet. But unsigned apps run on the development 
>> machine anyway, so I'd say you built the app successfully.
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>>  wrote:
>> 
>>> I have, but I don’t do any signing or notarizing. If that happens 
>>> transparently, then it’s working for me.
>>> 
>>> Bob S
>>> 
>>> 
 On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
  wrote:
 
 Thanks, Jacque!
 
 That gives me a clue. I will try to get more info on this.
 
 However, that note shows how to delete the offending resource using the 
 xattr tool, but I have no app to point it to. LiveCode did not build 
 anything.
 
 I’m willing to try some magic values in Standalone Application Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.
 
 Has anyone successfully built a Mac application recently?
 
 Dar
 
> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> This might help:
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>  wrote:
> 
>> I’m having trouble building an application for Mac Intel.
>> 
>> The first time LiveCode crashed.
>> 
>> Subsequent times, I get this error:
>> There was an error while saving the standalone application
>> Adding ad-hoc signature failed with error:
>> /…/myProgram.app:
>> Replacing existing signature
>> /…/myProgram.app:
>> Resource for, Finder information, or similar detritus not
>> Allowed
>> 
>> I tried fiddling with the PLIST settings without success.
>> ___
>> 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
>>> 
>>> ___
>>> 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
> 
> 

___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Dar Scott via use-livecode

I removed all inclusions. I opted to remove all profiles, probably none. There 
are no Copy Files. I’m building for Intel only. 

For PLIST I chose Chose a PLIST and then clicked Use None.

I set my bundle identifier and have not changed that among my attempts. I left 
all of the other Version Information as default. 

I have no Icons added.

I get the same error.

Dar

> On Aug 8, 2023, at 10:08 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Signing happens after the app is built and is a manual process, so yours 
> isn't signed /notarized yet. But unsigned apps run on the development machine 
> anyway, so I'd say you built the app successfully.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> I have, but I don’t do any signing or notarizing. If that happens 
>> transparently, then it’s working for me.
>> 
>> Bob S
>> 
>> 
>>> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>>>  wrote:
>>> 
>>> Thanks, Jacque!
>>> 
>>> That gives me a clue. I will try to get more info on this.
>>> 
>>> However, that note shows how to delete the offending resource using the 
>>> xattr tool, but I have no app to point it to. LiveCode did not build 
>>> anything.
>>> 
>>> I’m willing to try some magic values in Standalone Application Settings.
>>> I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>>> I’m on macOS Ventura.
>>> 
>>> Has anyone successfully built a Mac application recently?
>>> 
>>> Dar
>>> 
 On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
  wrote:
 
 This might help:
 
 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software | http://www.hyperactivesw.com
 On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
  wrote:
 
> I’m having trouble building an application for Mac Intel.
> 
> The first time LiveCode crashed.
> 
> Subsequent times, I get this error:
> There was an error while saving the standalone application
> Adding ad-hoc signature failed with error:
> /…/myProgram.app:
> Replacing existing signature
> /…/myProgram.app:
> Resource for, Finder information, or similar detritus not
> Allowed
> 
> I tried fiddling with the PLIST settings without success.
> ___
> 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
>> 
>> ___
>> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread panagiotis m via use-livecode

Hello all,

The standalone builder does add a signature when building the mac
standalone - but an ad hoc one (i.e. it does not use an actual
certificate). The error Dar gets happens during the standalone building
process.

@Dar
Could you attach the exact error? Just upload the screenshot somewhere and
post the link. It might help us isolate the problem, although I suspect it
is related to the command line tools version you have installed.

Could you try this in the terminal and post the output?

xcode-select -p

Cheers,
Panos

On Tue, 8 Aug 2023 at 19:08, Mark Smith via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Dar,
>
> I just built one unsigned and it worked fine. Will you be signing it for
> distribution in the Mac App store as well?
>
> Mark
>
> > On 8 Aug 2023, at 2:59 pm, Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Thanks, Jacque!
> >
> > That gives me a clue. I will try to get more info on this.
> >
> > However, that note shows how to delete the offending resource using the
> xattr tool, but I have no app to point it to. LiveCode did not build
> anything.
> >
> > I’m willing to try some magic values in Standalone Application Settings.
> >   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
> >   I’m on macOS Ventura.
> >
> > Has anyone successfully built a Mac application recently?
> >
> > Dar
> >
> >> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> This might help:
> >> 
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> HyperActive Software | http://www.hyperactivesw.com
> >> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >>> I’m having trouble building an application for Mac Intel.
> >>>
> >>> The first time LiveCode crashed.
> >>>
> >>> Subsequent times, I get this error:
> >>> There was an error while saving the standalone application
> >>> Adding ad-hoc signature failed with error:
> >>> /…/myProgram.app:
> >>> Replacing existing signature
> >>> /…/myProgram.app:
> >>> Resource for, Finder information, or similar detritus not
> >>> Allowed
> >>>
> >>> I tried fiddling with the PLIST settings without success.
> >>> ___
> >>> 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
>
>
> ___
> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Mark Smith via use-livecode

I should add I used 9.6.8 on Monterey. 

> On 8 Aug 2023, at 2:59 pm, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using the xattr 
> tool, but I have no app to point it to. LiveCode did not build anything.
> 
> I’m willing to try some magic values in Standalone Application Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble building an application for Mac Intel.
>>> 
>>> The first time LiveCode crashed.
>>> 
>>> Subsequent times, I get this error:
>>> There was an error while saving the standalone application
>>> Adding ad-hoc signature failed with error:
>>> /…/myProgram.app:
>>> Replacing existing signature
>>> /…/myProgram.app:
>>> Resource for, Finder information, or similar detritus not
>>> Allowed
>>> 
>>> I tried fiddling with the PLIST settings without success.
>>> ___
>>> 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


___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread J. Landman Gay via use-livecode

Signing happens after the app is built and is a manual process, so yours 
isn't signed /notarized yet. But unsigned apps run on the development 
machine anyway, so I'd say you built the app successfully.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 8, 2023 10:47:34 AM Bob Sneidar via use-livecode 
 wrote:


I have, but I don’t do any signing or notarizing. If that happens 
transparently, then it’s working for me.


Bob S


On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
 wrote:


Thanks, Jacque!

That gives me a clue. I will try to get more info on this.

However, that note shows how to delete the offending resource using the 
xattr tool, but I have no app to point it to. LiveCode did not build anything.


I’m willing to try some magic values in Standalone Application Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.

Has anyone successfully built a Mac application recently?

Dar

On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
 wrote:


This might help:

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
 wrote:



I’m having trouble building an application for Mac Intel.

The first time LiveCode crashed.

Subsequent times, I get this error:
There was an error while saving the standalone application
Adding ad-hoc signature failed with error:
/…/myProgram.app:
Replacing existing signature
/…/myProgram.app:
Resource for, Finder information, or similar detritus not
Allowed

I tried fiddling with the PLIST settings without success.
___
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


___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Mark Smith via use-livecode

Hi Dar,

I just built one unsigned and it worked fine. Will you be signing it for 
distribution in the Mac App store as well? 

Mark

> On 8 Aug 2023, at 2:59 pm, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using the xattr 
> tool, but I have no app to point it to. LiveCode did not build anything.
> 
> I’m willing to try some magic values in Standalone Application Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble building an application for Mac Intel.
>>> 
>>> The first time LiveCode crashed.
>>> 
>>> Subsequent times, I get this error:
>>> There was an error while saving the standalone application
>>> Adding ad-hoc signature failed with error:
>>> /…/myProgram.app:
>>> Replacing existing signature
>>> /…/myProgram.app:
>>> Resource for, Finder information, or similar detritus not
>>> Allowed
>>> 
>>> I tried fiddling with the PLIST settings without success.
>>> ___
>>> 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


___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Bob Sneidar via use-livecode

I have, but I don’t do any signing or notarizing. If that happens 
transparently, then it’s working for me. 

Bob S


> On Aug 8, 2023, at 6:59 AM, Dar Scott via use-livecode 
>  wrote:
> 
> Thanks, Jacque!
> 
> That gives me a clue. I will try to get more info on this.
> 
> However, that note shows how to delete the offending resource using the xattr 
> tool, but I have no app to point it to. LiveCode did not build anything.
> 
> I’m willing to try some magic values in Standalone Application Settings.
>   I’m using LiveCode 9.6.9, but I’m willing to upgrade.
>   I’m on macOS Ventura.
> 
> Has anyone successfully built a Mac application recently?
> 
> Dar
> 
>> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> This might help:
>> 
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>>  wrote:
>> 
>>> I’m having trouble building an application for Mac Intel.
>>> 
>>> The first time LiveCode crashed.
>>> 
>>> Subsequent times, I get this error:
>>> There was an error while saving the standalone application
>>> Adding ad-hoc signature failed with error:
>>> /…/myProgram.app:
>>> Replacing existing signature
>>> /…/myProgram.app:
>>> Resource for, Finder information, or similar detritus not
>>> Allowed
>>> 
>>> I tried fiddling with the PLIST settings without success.
>>> ___
>>> 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

___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread J. Landman Gay via use-livecode

I built a Mac standalone about 3 weeks ago without issue using an RC 
version of 9.6.9. I'm still on Monterey though. Do you have any inclusions 
selected or files in the Copy Files pane of the standalone settings? If so, 
try building without them and see what happens.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 8, 2023 9:01:54 AM Dar Scott via use-livecode 
 wrote:



Thanks, Jacque!

That gives me a clue. I will try to get more info on this.

However, that note shows how to delete the offending resource using the 
xattr tool, but I have no app to point it to. LiveCode did not build anything.


I’m willing to try some magic values in Standalone Application Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.

Has anyone successfully built a Mac application recently?

Dar

On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
 wrote:


This might help:

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
 wrote:



I’m having trouble building an application for Mac Intel.

The first time LiveCode crashed.

Subsequent times, I get this error:
There was an error while saving the standalone application
Adding ad-hoc signature failed with error:
/…/myProgram.app:
Replacing existing signature
/…/myProgram.app:
Resource for, Finder information, or similar detritus not
Allowed

I tried fiddling with the PLIST settings without success.
___
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





___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-08 Thread Dar Scott via use-livecode

Thanks, Jacque!

That gives me a clue. I will try to get more info on this.

However, that note shows how to delete the offending resource using the xattr 
tool, but I have no app to point it to. LiveCode did not build anything.

I’m willing to try some magic values in Standalone Application Settings.
I’m using LiveCode 9.6.9, but I’m willing to upgrade.
I’m on macOS Ventura.

Has anyone successfully built a Mac application recently?

Dar

> On Aug 7, 2023, at 3:43 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> This might help:
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
>  wrote:
> 
>> I’m having trouble building an application for Mac Intel.
>> 
>> The first time LiveCode crashed.
>> 
>> Subsequent times, I get this error:
>> There was an error while saving the standalone application
>> Adding ad-hoc signature failed with error:
>> /…/myProgram.app:
>> Replacing existing signature
>> /…/myProgram.app:
>> Resource for, Finder information, or similar detritus not
>> Allowed
>> 
>> I tried fiddling with the PLIST settings without success.
>> ___
>> 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

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-07 Thread J. Landman Gay via use-livecode


This might help:

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 7, 2023 12:49:03 PM Dar Scott via use-livecode 
 wrote:



I’m having trouble building an application for Mac Intel.

The first time LiveCode crashed.

Subsequent times, I get this error:
There was an error while saving the standalone application
Adding ad-hoc signature failed with error:
/…/myProgram.app:
Replacing existing signature
/…/myProgram.app:
Resource for, Finder information, or similar detritus not
Allowed

I tried fiddling with the PLIST settings without success.
___
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

Unable to build for Mac: adding ad-hoc signature failed

2023-08-07 Thread Dar Scott via use-livecode


I’m having trouble building an application for Mac Intel.

The first time LiveCode crashed.

Subsequent times, I get this error:
There was an error while saving the standalone application
Adding ad-hoc signature failed with error:
/…/myProgram.app:
Replacing existing signature
/…/myProgram.app:
Resource for, Finder information, or similar detritus not
Allowed

I tried fiddling with the PLIST settings without success.
___
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

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Re: Unable to build for Mac: adding ad-hoc signature failed

Unable to build for Mac: adding ad-hoc signature failed

24 matches

Site Navigation

Mail list logo

Footer information