"__int128 is not supported on this target" when trying to generate bindings for OpenCV for iOS

Open
#1,009 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, csharp, ios, opencv

Research direction

Start with the attached shell script, generated Clang-defines header, and unified diff for opencv_modules.hpp; reproduce the CppSharp command against the OpenCV 3.2.0 iOS headers. Trace the target configuration related to the __int128 diagnostics, and consider the issue resolved when the bindings generate without these parsing errors.

Written by the indexing model from the issue text.

Description

Brief Description

I want to use OpenCV in C# with Xamarin, so I downloaded OpenCV 3.2.0 iOS Pack from their release page (https://opencv.org/releases.html [I know there is a newer version available but I have working code using the 3.2.0 version I want to port it from Windows .NET to Xamarin iOS]) and CppSharp 0.8.16. I had several parsing errors and was able to solve most

  • by adding paths to C, C++ and Clang headers
  • generating an header file from standard Clang defines
  • locally patching opencv_modules.hpp to disable modules I actually will not use and add a few defines

However I get several "__int128 is not supported on this target" parsing errors which I am unable to solve.

OS: OS X El Capitan 10.11.6
Target: Clang

I will attach a few files :

  • the shell script I wrote containing the paths to headers, the command to generate the header from standard Clang defines and the CppSharp command line
  • the header generated from standard Clang defines
  • A unified diff of my changes to opencv_modules.hpp
Dominant language
C#
Stars
3.4k
Forks
541
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mono/CppSharp

All issues in mono/CppSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.