Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

Is there a way to make the IL2CPP deployment not generate 9 thousand header files? :)

Discussion in 'iOS and tvOS' started by crushforth, Dec 18, 2015.

  1. crushforth

    crushforth

    Joined:
    Jul 22, 2010
    Posts:
    113
    Could we have a check box that possibly merges all these in to maybe the same header file. Not complaining just curious.
     
    crushforth, Dec 18, 2015
    #1

  2. crushforth

    crushforth

    Joined:
    Jul 22, 2010
    Posts:
    113
    @JoshPeterson Isn't there anything that can be done about this? Maybe compile lots of the UnityEngine code/Native folder into a lib. When building locally its really not an issue but trying to explain to the rest of the team that you really do need to commit 13 thousand source files to github so that our distributed build machine can make builds is embarrassing :) And the fact that each deployment all the files are modified each time.

    It's mostly just a problem with the Classes/Native folder. If any one has any suggestions on how I can automate compiling this folder down to a lib to try and reduce the number of files that'd be very helpful.
     
    crushforth, Jan 6, 2016
    #2

  3. CPXTom

    CPXTom

    Joined:
    Apr 24, 2010
    Posts:
    113
    Not sure what CI system you're using, but you probably don't want to be committing the XCode project. The build system should get Unity to Build the XCode Project and then build that.
     
    CPXTom, Jan 6, 2016
    #3

  4. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,775
    @crushforth

    I don't think this is something that we can easily change. Combining these headers can cause problems for incremental builds, making it difficult for us to improve the iteration times for local development builds. Of course you probably don't care about incremental builds on a CI system.

    More generally, I agree with @CPXTom here. I don't think that should should be committing the generated XCode project to source control anywhere. There could be lost of churn in these files for which the source code history is likely not meaningful. I wonder if there is a different way to get the files to your CI system, or just to generated the files from the Unity project as part of the CI build.
     
    JoshPeterson, Jan 7, 2016
    #4

  5. crushforth

    crushforth

    Joined:
    Jul 22, 2010
    Posts:
    113
    Thanks for the feedback. I adjusted everything so that Unity lives on the build machine and deploys from the command line and we don't have the intermediate files (or any of the xcode project) in github.
     
    crushforth, Jan 7, 2016
    #5
    CPXTom likes this.