Bug 22028 - Error while using NLua
Summary: Error while using NLua
Status: RESOLVED INVALID
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.2
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-08-12 03:33 UTC by Sven Carstensen
Modified: 2015-05-18 19:42 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Testcase (6.54 MB, application/zip)
2014-08-23 08:17 UTC, Sven Carstensen
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Sven Carstensen 2014-08-12 03:33:19 UTC
Hello,

if i try to use NLua in my Xamarin Forms Project i get the following linking error

error MT5214: Native linking failed, undefined symbol: _lua_call. This symbol was referenced the managed member KeraLua.NativeMethods.LuaCall. Please verify that all the necessary frameworks have been referenced and native libraries linked. error MT5202: Native linking failed. Please review the build log.

The NLua Component is properly added to the system shared projects (Android and iOS).

Any suggestions?

Regards Sven.
Comment 1 Sunil Kumar 2014-08-21 12:46:29 UTC
I tried to reproduce this issue but I am unable to reproduce. I created Shared Project(Xamarin.Forms Shared) and Added package NLua version 1.2.2.14 then deploy the application. application is deploy successfully on device and it runs.

Screencast: http://www.screencast.com/t/6bsl9BuVihL

Please let me know if I have to follow any other steps to reproduce this issue?

Environment info:
=== Xamarin Studio ===

Version 5.3 (build 430)
Installation UUID: 561c7a69-0a91-4bae-ad7c-f0c79d594337
Runtime:
	Mono 3.8.0 ((no/62a857e)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000007

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.Mac ===

Version: 1.10.0.7 (Trial Edition)

=== Xamarin.Android ===

Version: 4.16.0 (Trial Edition)
Android SDK: /Users/tajinder/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.iOS ===

Version: 7.4.0.104 (Trial Edition)
Hash: 63b403b
Branch: 
Build date: 2014-08-19 16:20:25-0400

=== Build Information ===

Release ID: 503000430
Git revision: 5587c96e1557fc9f87a1e3b05a71c35682ebdee5
Build date: 2014-08-20 13:30:32-04
Xamarin addins: b82a80805b6d75d25dd0ef6a98561fd0a378235b

=== Operating System ===

Mac OS X 10.8.4
Darwin Tajinders-iMac.local 12.4.2 Darwin Kernel Version 12.4.2
    Mon Jun 17 18:00:12 PDT 2013
    root:xnu-2050.45.8~1/RELEASE_X86_64 x86_64
Comment 2 Sven Carstensen 2014-08-23 04:00:41 UTC
Only adding the component will works. But if you try to instantiate a Lua Object linking will fail.

Screencast: http://www.screencast.com/t/dNdNB16FC
Comment 3 Sven Carstensen 2014-08-23 08:17:46 UTC
Created attachment 7781 [details]
Testcase

Xamarin Studio Solution with Testcase.
Comment 4 Sunil Kumar 2014-08-25 06:29:44 UTC
We tried to reproduce this issue. We build the attached project and we are also getting the error.


Screencast: http://www.screencast.com/t/x8WMjA2ANiuk
Error: https://gist.github.com/sunil360/45acecfe98f53d8b6e35
Build Output: https://gist.github.com/sunil360/fe85713e69ccb16e43f0
IDE log: https://gist.github.com/sunil360/43bb4211ed69e14ef27c


Environment info: 
=== Xamarin Studio ===

Version 5.3 (build 434)
Installation UUID: 561c7a69-0a91-4bae-ad7c-f0c79d594337
Runtime:
	Mono 3.8.0 ((no/62a857e)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000007

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.iOS ===

Version: 7.4.0.106 (Business Edition)
Hash: 3991e99
Branch: 
Build date: 2014-08-22 13:09:34-0400

=== Xamarin.Android ===

Version: 4.16.0 (Business Edition)
Android SDK: /Users/tajinder/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.Mac ===

Version: 1.10.0.7 (Business Edition)

=== Build Information ===

Release ID: 503000434
Git revision: 9b508e2173c6a211fa020d9743a86b484b5ed0d2
Build date: 2014-08-21 12:41:28-04
Xamarin addins: 69708b283b171ea053d0edfbf09d98457d21fbee

=== Operating System ===

Mac OS X 10.8.4
Darwin Tajinders-iMac.local 12.4.2 Darwin Kernel Version 12.4.2
    Mon Jun 17 18:00:12 PDT 2013
    root:xnu-2050.45.8~1/RELEASE_X86_64 x86_64
Comment 5 Eric Maupin 2015-05-18 19:42:16 UTC
This appears to be an issue with NLua directly and not a Forms related issue.