With macOS Sierra 10.12.6 and LC Community (any 9.x latest and prerelease versions) it is not possible anymore to build standalones for any platform. When MacOS, Windows and Linux are enabled in the build settings, LC just creates an empty Folder "Windows" and exits.
I find several entries in the console logs like:
19:09:20.774364 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.config
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 2
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
May 8 19:07:21 server LiveCode-Community[608]: assertion failed: 16G1405: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
May 8 19:07:29 server LiveCode-Community[608]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked
May 8 19:09:22 server LiveCode-Community[689]: assertion failed: 16G1405: libxpc.dylib + 74307 [BF896DF0-D8E9-31A8-A4B3-01120BFEEE52]: 0x89
May 8 19:09:25 server LiveCode-Community[689]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked
21:11:38.300485 +0200 diagnostics_agent com.apple.message.domain: com.apple.usage.app_activetime
com.apple.message.signature: autoupdater
com.apple.message.signature2: com.runrev.livecode ||| 9.0.0.15016 (9.0.0.15016)
com.apple.message.value: 126
com.apple.message.value2: 8
com.apple.message.value3: 2
com.apple.message.value4: 0
com.apple.message.value5: 1
com.apple.message.value6: 1
com.apple.message.value7: 8
com.apple.message.result: YES
com.apple.message.summarize: YES
SenderMachUUID: DFB398C5-FBEE-3DBF-8EE2-E03091DF9F84
21:11:38.309113 +0200 diagnostics_agent com.apple.message.domain: com.apple.usage.app_activetime
com.apple.message.signature: LiveCode-Community
com.apple.message.signature2: com.runrev.livecode ||| 9.0.0.15016 (9.0.0.15016)
com.apple.message.value: 88
com.apple.message.value2: 88
com.apple.message.value3: 2
com.apple.message.value4: 0
com.apple.message.value5: 2
com.apple.message.value6: 1
com.apple.message.value7: 88
com.apple.message.result: YES
com.apple.message.summarize: YES
SenderMachUUID: DFB398C5-FBEE-3DBF-8EE2-E03091DF9F84
23:10:44.889974 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.config
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 2
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890129 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.pv
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 0303
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890203 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.cs
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: c02b
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890270 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.key_type
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: ecc
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890337 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.kxSigAlg
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 04_03
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890399 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.curve
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: p256
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:44.890461 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.value_events: 1
com.apple.message.value_alpn_received: 1
com.apple.message.value_sct_list: 1
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.057993 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.config
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 2
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058063 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.pv
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 0303
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058104 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.cs
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: c02f
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058139 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.key_type
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: rsa
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058174 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.kxSigAlg
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: 04_01
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058210 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished.curve
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.signature3: p256
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:10:45.058242 +0200 LiveCode-Community com.apple.message.domain: com.apple.coretls.client_finished
com.apple.message.signature: tls
com.apple.message.signature2: redacted_bundle_id
com.apple.message.value_events: 1
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
23:11:18.884049 +0200 LiveCode-Community OSActivityID: 0x8000000000002c10
com.apple.message.domain: com.apple.open.document
com.apple.message.signature: Open Panel - Opened a file
com.apple.message.summarize: YES
SenderMachUUID: 85E094CC-4F37-3BF0-8EFB-5758D1E43249
Standalones not built anymore with 10.12.6
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Posts: 4
- Joined: Wed Nov 15, 2006 1:44 pm
-
- Livecode Staff Member
- Posts: 818
- Joined: Fri Feb 06, 2015 4:03 pm
Re: Standalones not built anymore with 10.12.6
Hi Gerald,
Works fine for me here. Do you see that with every stack you try, or just a specific one? If you see it only with a specific stack, could you attach the stack here? If the stack is confidential I suggest you file a bug report at https://quality.livecode.com and send your stack directly to panos.merakos@livecode.com
Best regards,
Panos
--
Works fine for me here. Do you see that with every stack you try, or just a specific one? If you see it only with a specific stack, could you attach the stack here? If the stack is confidential I suggest you file a bug report at https://quality.livecode.com and send your stack directly to panos.merakos@livecode.com
Best regards,
Panos
--
-
- Posts: 4
- Joined: Wed Nov 15, 2006 1:44 pm
Re: Standalones not built anymore with 10.12.6
Hi Panos,
I found a very simple cause for the behavior which has nothing to do with the macOS version, but apparently occurs since some of the LC 9 prerelease versions until 9.0.0:
At the beginning of my stack script I got the following lines:
on closeStack
quit
end closeStack
If I removes these lines, all builds are done correctly.
The reason for this is that I want to exit the application when I click in the close box of the main stack window. window.
(I found no other way to do this and it worked in many previous LC versions.)
So it seems that the build process sends this event somewhere at the beginning and the build terminates itself too early.
Is this some kind of bug in the builder or is the above event handling not the best way to do what I want ?
Best regards,
Gerald
I found a very simple cause for the behavior which has nothing to do with the macOS version, but apparently occurs since some of the LC 9 prerelease versions until 9.0.0:
At the beginning of my stack script I got the following lines:
on closeStack
quit
end closeStack
If I removes these lines, all builds are done correctly.
The reason for this is that I want to exit the application when I click in the close box of the main stack window. window.
(I found no other way to do this and it worked in many previous LC versions.)
So it seems that the build process sends this event somewhere at the beginning and the build terminates itself too early.
Is this some kind of bug in the builder or is the above event handling not the best way to do what I want ?
Best regards,
Gerald
vi
-
- Livecode Staff Member
- Posts: 818
- Joined: Fri Feb 06, 2015 4:03 pm
Re: Standalones not built anymore with 10.12.6
Hi Gerald,
Ok, this does help. Short story, the standalone builder in LC 9 no longer locks messages when building the standalone. This was a necessary change to fix other problems. This means that the (pre)openstack and closestack messages are now sent to the stack when you build a standalone. So in your case the "quit" is called, thus LC quits.
To prevent this, you can modify the closestack handler as follows:
For more details, see the Release Notes of LC 9 in the section "Breaking Changes"
Hope this helps.
Best,
Panos
--
Ok, this does help. Short story, the standalone builder in LC 9 no longer locks messages when building the standalone. This was a necessary change to fix other problems. This means that the (pre)openstack and closestack messages are now sent to the stack when you build a standalone. So in your case the "quit" is called, thus LC quits.
To prevent this, you can modify the closestack handler as follows:
Code: Select all
on closeStack
if the mode of stack "revStandaloneProgress" > 0 then
exit closestack
end if
quit
end closeStack
Hope this helps.
Best,
Panos
--
-
- Posts: 4
- Joined: Wed Nov 15, 2006 1:44 pm
Re: Standalones not built anymore with 10.12.6
Hi Panos,
Though I consulted through the release notes after installing, I overlooked the section "Standalone Building.
Many thanks for your help.
Best regards,
Gerald
Though I consulted through the release notes after installing, I overlooked the section "Standalone Building.
Many thanks for your help.
Best regards,
Gerald
vi