alexsorokoletov
commented
6 years ago @Emixam23 Maxime, do you have all the prerequisites installed?
Specifically, can you run sharpie in your terminal and make sure it is starting?
Open Emixam23 opened 6 years ago
alexsorokoletov
commented
6 years ago @Emixam23 Maxime, do you have all the prerequisites installed?
Specifically, can you run sharpie in your terminal and make sure it is starting?
Emixam23
commented
6 years ago Hey :)
I already tried to bind a static library but it generates 18k lines of code for APIDefinitions and 25k for StructsAndEnums. At least, it shows that sharpie seems to work
MacBook-Pro-de-Emixam23:XamarinIOS_Bindings emixam23$ sharpie bind -output Test2 -namespace Test2 -sdk iphoneos11.2 Test2/Test2/Test2.h Parsing 1 header files...
Binding... [write] ApiDefinitions.cs [write] StructsAndEnums.cs
Binding Analysis: Automated binding is complete, but there are a few APIs which have been flagged with [Verify] attributes. While the entire binding should be audited for best API design practices, look more closely at APIs with the following Verify attribute hints:
ConstantsInterfaceAssociation (101 instances): There's no foolproof way to determine with which Objective-C interface an extern variable declaration may be associated. Instances of these are bound as [Field] properties in a partial interface into a nearby concrete interface to produce a more intuitive API, possibly eliminating the 'Constants' interface altogether.
MethodToProperty (121 instances): An Objective-C method was bound as a C# property due to convention such as taking no parameters and returning a value (non-void return). Often methods like these should be bound as properties to surface a nicer API, but sometimes false-positives can occur and the binding should actually be a method.
StronglyTypedNSArray (21 instances): A native NSArray was bound as NSObject[]. It might be possible to more strongly type the array in the binding based on expectations set through API documentation (e.g. comments in the header file) or by examining the array contents through testing. For example, an NSArray containing only NSNumber* instances can be bound as NSNumber[] instead of NSObject[].
PlatformInvoke (2407 instances): In general P/Invoke bindings are not as correct or complete as Objective-C bindings (at least currently). You may need to fix up the library name (it defaults to '__Internal') and return/parameter types manually to conform to C calling conventionsfor the target platform. You may find you don't even want to expose the C API in your binding, but if you do, you'll probably also want to relocate the definition to a more appropriate class and expose a stronger type-safe wrapper. For P/Invoke guidance, see http://www.mono-project.com/docs/advanced/pinvoke/.
InferredFromMemberPrefix (24 instances): The name of this originally anonymous declaration was taken from a common prefix of its members.
Once you have verified a Verify attribute, you should remove it from the binding source code. The presence of Verify attributes intentionally cause build failures.
For more information about the Verify attribute hints above, consult the Objective Sharpie documentation by running 'sharpie docs' or visiting the following URL:
http://xmn.io/sharpie-docsDone.
The code I have:
Test2.h
//
// Test2.h
// Test2
//
// Created by Emixam23 on 07/08/2018.
// Copyright © 2018 Noname. All rights reserved.
//
#import <Foundation/Foundation.h>
@interface Test2 : NSObject
+ (void) PrintCustomLog : (NSString*) data;
@endTest2.m
//
// Test2.m
// Test2
//
// Created by Emixam23 on 07/08/2018.
// Copyright © 2018 Noname. All rights reserved.
//
#import "Test2.h"
@implementation Test2
+ (void) PrintCustomLog : (NSString*) data
{
NSLog(@"%@", data);
}
@end@Emixam23 I can reproduce your problem, looking into it. Long story short, lottie (as an example) had an update to it's structure and so XCode and cocoapods. Since lottie is not a conventional framework cocoapod and just something that "looks like it", there is a lot of custom dance involved in the objc-automatic to guess the right settings for that kind of pods.
Working on a small update as well as some documentation on how to address and detect these issues
Hey, I just tried to follow your video but with no luck :( I am looking to bind TwitterKit3 for iOS