title: Bitcode disabled on Carthage dependencies
body: <p><strong>Scenario</strong></p>
  
  <p>My project (codebase shared for iOS/watchOS/tvOS ) has build settings with <code>ENABLE_BITCODE = YES</code> and takes advantage of fundamental libraries which are not yet supporting bitcode, although quoting Apple documentation in <a href="https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AppThinning/AppThinning.html" rel="nofollow noreferrer">App Thinning</a></p>
  
  <blockquote>
    <p>Bitcode is the default, but optional. For watchOS and tvOS apps,
    bitcode is required. If you provide bitcode, all apps and frameworks
    in the app bundle (all targets in the project) need to include bitcode</p>
  </blockquote>
  
  <p>I am currently integrating those fundamental libraries with Carthage.</p>
  
  <p><strong>Problem</strong></p>
  
  <p>In order to have a clean build process, I tried to submit some pull requests to the respective owners for enabling the bitcode but, due to the complexity of their codebases, which are working for multiple operating systems/architectures, my pull requests are still in pending: so, to be able to build my own project, I still have to change manually their build settings.</p>
  
  <p><strong>Question</strong></p>
  
  <p>How can I short-circuit the Carthage process for injecting specific build settings (in this case <code>ENABLE_BITCODE = YES</code>) into the relevant libraries?</p>