Another "building" problem...

Getting into LiveCode for iOS? Ask your questions here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
GoneToSail
Posts: 40
Joined: Sun Jan 24, 2010 10:34 pm
Location: French Atlantic Island

Another "building" problem...

Post by GoneToSail » Fri Feb 17, 2017 6:43 pm

Hi !
After a recent upgrade (LC, xCode, etc...), I have the following message when trying to save a standalone for iOS:

QUOTE
linking for arm (arm64)failes with Undefined symbols for architecture arm64:
"__libinfoptr_mergMK" referenced from: -u command line option
Id: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
UNQUOTE

And I don't understand so much about this message except that the problem should be related to mergMK extension.

My environment is as follows:
MacBook Pro with OSX 10.11.6
LC Indy 8.1.2
xCode 8.1 (build 8B62)
iPhone 5c with iOS 10.2.1 (14D27)

I have copied the latest mergMK extension in the standalone Application Settings, i.e. version 3.0.17.

Any idea about what I am doing wrong ?

Klaus
Posts: 13806
Joined: Sat Apr 08, 2006 8:41 am
Location: Germany
Contact:

Re: Another "building" problem...

Post by Klaus » Fri Feb 17, 2017 6:57 pm

Hello Sailor,

maybe this helps:
http://forums.livecode.com/viewtopic.php?f=49&t=28760
?


Best

Klaus

LiveCode_Panos
Livecode Staff Member
Livecode Staff Member
Posts: 818
Joined: Fri Feb 06, 2015 4:03 pm

Re: Another "building" problem...

Post by LiveCode_Panos » Fri Feb 17, 2017 6:57 pm

Hi GoneToSail,

Starting from LC 8.1.0, you no longer need to use the "classic" way of including the emergent externals. So you don't need to included the external in the "Copy Files" section.

All you have to do now is:

0. Remove any references to mergMK from the "Copy Files" pane
1. In "General" pane choose "Select Inclusions for the standalone application"
2. In "Inclusions" pane just check the mergExt externals you need.

Best,
Panos
--

GoneToSail
Posts: 40
Joined: Sun Jan 24, 2010 10:34 pm
Location: French Atlantic Island

Re: Another "building" problem...

Post by GoneToSail » Fri Feb 17, 2017 7:27 pm

Thanks for your quick replies.
I have chosen "Select Inclusions" in the "General" pane of the Standalone Application Settings, and then checked "mergMK" in the "Inclusions" pane, and I am glad that I made one step forward, but I have now the following error: "could not open standalone engine file" !

GoneToSail
Posts: 40
Joined: Sun Jan 24, 2010 10:34 pm
Location: French Atlantic Island

Re: Another "building" problem...

Post by GoneToSail » Fri Feb 17, 2017 11:46 pm

A few hours later...

I just tried to start LiveCode again, and surprisingly it works fine again.
@Klaus, @LiveCode_Panos, thank you for your assistance !

I have checked that my new build works normally on the Simulator, however I have the following message when installing on an iPhone 5c:
This iPhone 5c is running iOS 10.2.1 (14D27) which may not be supported by this version of Xcode.

Should I have to wait until LC 8.1.3 is released and then switch to Xcode 8.2, or is there any mean to reinstall an older iOS version on this iPhone ?
Any suggestion is welcome...

LiveCode_Panos
Livecode Staff Member
Livecode Staff Member
Posts: 818
Joined: Fri Feb 06, 2015 4:03 pm

Re: Another "building" problem...

Post by LiveCode_Panos » Mon Feb 20, 2017 6:06 pm

Hi GoneToSail,
This iPhone 5c is running iOS 10.2.1 (14D27) which may not be supported by this version of Xcode.
This is just a warning, which you can safely ignore. The app will be installed in your phone as expected, if you just drag the .app file onto the "Installed Apps" area, as usual.

Best,
Panos
--

GoneToSail
Posts: 40
Joined: Sun Jan 24, 2010 10:34 pm
Location: French Atlantic Island

Re: Another "building" problem...

Post by GoneToSail » Tue Feb 21, 2017 7:21 pm

Thanks Panos,
The message was actually more disturbing as it was also saying at first line:
"Could not locate device support files."
But I tried again and it woks fine ! Thank you again.

Post Reply

Return to “iOS Deployment”