My native library seems to be breaking the non-LLVM armv6 build….LLVM armv7
works fine. However we MUST be able to debug code on the device. I compiled
my (fat) library with LLVM GCC 4.2 and Apple LLVM compiler 3.0. In both
cases running the non-LLVM-nibless armv6 App on my iPad2 throws a
NullReferenceException with DialogViewController..ctor at the top-of-stack: 

mMyViewController = new MyViewController();

MyViewController is defined as follows:

public class MyViewController : MonoTouch.Dialog.DialogViewController
{
        public MyViewController () : base(null /* no…it's not this */)  
        {
                // ...
        }
}

Note that NONE of my native code has been called at that point in the
App...except c++ statics. In addition the App runs fine if I remove all the
P/Invoke calls to my native library. The native library runs fine when
called from a native (XCode) App. Are there any known issues with the
armv6…I'm doing a debug iOS5 build with no optimizations ?

xcode 4.2 4C199
mtouch 5.0.1.1319647906
Additional mtouch arguments:
-cxx -gcc_flags "-ObjC -deadstrip
-L${ProjectDir}/../../MobileSynchronizer_XCode/User/build/Debug-iphonesimulator
-L${ProjectDir}/../../Tools/Arch/lib/Universal
-L${ProjectDir}/../../Tools/openssl-1.0.0b/build/Debug-iphonesimulator
-L${ProjectDir}/../../Tools/Sqlite-3.7.6.1/build/Debug-iphonesimulator
-framework SystemConfiguration -larc -lcrypto -licucore -lUser -lsqlite
-lssl -lxml2.2.7.3 -force_load
${ProjectDir}/../../Tools/openssl-1.0.0b/build/Debug-iphonesimulator/libcrypto.a
${ProjectDir}/../../Tools/openssl-1.0.0b/build/Debug-iphonesimulator/libssl.a
${ProjectDir}/../../Tools/Sqlite-3.7.6.1/build/Debug-iphonesimulator/libsqlite.a"



--
View this message in context: 
http://monotouch.2284126.n4.nabble.com/Native-library-with-Monotouch-5-0-part-2-tp3992408p3992408.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch

Reply via email to