Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33522

Closed (moved)
Open
Opened Mar 04, 2020 by Trac@tracbot

Add iOS support in your CI

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?

Trac:
Username: tla

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33522