Re: [reSIProcate-users] Compiling resiprocate on iOS
Nothing too much special.
I think the biggest thing is iOS special requirements for VoIP applications.
You can't expect iOS will retain TCP/TLS connection in background.
See Apple's doc:
https://developer.apple.com/library/content/documentation/Performance/Conceptual/EnergyGuide-iOS/OptimizeVoIP.html
On Fri, Nov 17, 2017 at 3:30 AM, Francesco Lamonica
<alienpenguin@xxxxxxxxx> wrote:
> Hi all,
> i am wondering if there is any special care that should be taken when
> compiling for iOS.
>
> i.e. i see in compat.hxx that there is some code definition enclosed in
> TARGET_IPHONE_OS
> Should that be defined when compiling it?
>
> Beacuse when i try to link my application to the ios libraries i get an
> undefined symbol errors regarding resip::Data::copy(const char*, unsigned
> long) and resip::Data(const char*, unsigned long)
>
> with nm i noticed that in librutil.a i can see the symbols for those
> functions defined for unsigned int, NOT long
>
> So, for some reasons my code when compiling and including resiprocate
> includes UInt32 seems to match unsigned long, but my IDE seems to point to
> unsigned int.
>
> Can anyone suggest me something?
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>