[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #33522 [Core Tor/Tor]: Add iOS support in your CI

#33522: Add iOS support in your CI
-------------------------+------------------------------
 Reporter:  tla          |          Owner:  (none)
     Type:  enhancement  |         Status:  new
 Priority:  Medium       |      Component:  Core Tor/Tor
  Version:               |       Severity:  Normal
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+------------------------------
 AFAIK, Tor.framework is the most advanced library to package Tor for iOS.

 You can find it here:
 https://github.com/iCepa/Tor.framework

 It has a Travis-CI configuration, which I just updated to work on the
 latest macOS/Xcode image:

 https://github.com/iCepa/Tor.framework/blob/master/.travis.yml


 Currently, we have issues in getting past Tor 0.4.0.6 on iOS. When I try
 to use a newer core, I get this error message:

 > Unknown type name 'dispatch_queue_t'

 in CFStream of Apple's CoreFoundation framework.


 But "dispatch_queue_t" is actually a valid symbol from Apple's Foundation
 libraries.

 So somehow, it gets cancelled out through something which changed in Tor
 recently.

 We're really stuck here, so it would be a huge help, if you could add
 Tor.framework to your Continuous Integration so you'd be able to support
 us here and detect problems earlier in the future.

 For your purposes, there's no need to have Macs and Xcode.
 The most important files to control the build are these shell scripts:

 https://github.com/iCepa/Tor.framework/blob/master/Tor/tor.sh
 https://github.com/iCepa/Tor.framework/blob/master/Tor/libevent.sh
 https://github.com/iCepa/Tor.framework/blob/master/Tor/openssl.sh
 https://github.com/iCepa/Tor.framework/blob/master/Tor/xz.sh

 Tor and the other libraries come in via Git submodules:
 https://github.com/iCepa/Tor.framework/blob/master/.gitmodules

 So the dev process on your side would be:

 Update submodules to your latest state, let it build in Travis. If broken,
 fix above build scripts. Re-run through Travis.


 Could that work for you?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33522>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs