[Bug 777528] XCode Template does not work

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Sat Jan 21 09:23:02 UTC 2017


https://bugzilla.gnome.org/show_bug.cgi?id=777528

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slomo at coaxion.net

--- Comment #3 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Nick Kallen from comment #0)

> Which I can fix by adding the linker flag -liconv to my Build Settings

That's indeed needed and was forgotten to be added also to the template (the
example applications all go it). Want to provide a patch?

> FWIW, I have created a Objective-C/Swift bridge and module.map that allows
> me to use the library from Swift -- if anyone wants them.

That would indeed be interesting. Did you base it on the GObject-Introspection
information to also get information about how to do memory management?

(In reply to Nick Kallen from comment #1)
> Even if you tell xcode to use the gnu stdc++ library rather than the new
> libc++, you must also force  xcode to use clang++ rather than clang to get
> past these errors. I did this, for example, by making a .mm file... There's
> got to be a better way.

Yes you currently have to use the GNU C++ STL, see bug #766366. Which generally
means that your "target" iOS version has to be set to 6.0 (or 7.0?) currently
to make this work out of the box.

> However, the codecs plugin now fails with '"_opj_image_create", referenced
> from:' errors.

That's a bug in the 1.11.1 development release on platforms using static
linking. Try 1.10.2 instead.

(In reply to Nick Kallen from comment #2)
> I forgot to mention I also had to turn off 'Enable bitcode' in Build options
> otherwise I got 

We don't built with bitcode, simply because it's not generally possible or easy
to do. Quite a few libraries have assembly optimizations and are not plain C.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list