Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fatal error C1014: too many include files: depth = 1024 #939

Closed
sergegers opened this issue Dec 14, 2022 · 3 comments
Closed

fatal error C1014: too many include files: depth = 1024 #939

sergegers opened this issue Dec 14, 2022 · 3 comments
Labels

Comments

@sergegers
Copy link

sergegers commented Dec 14, 2022

Looks like a bug. During jumbo build if continue a build after fixing code or build with key -clean there is an error message:

fatal error C1014: too many include files: depth = 1024

The cleaning intermediate and output files and full solution build is working fine.

@ffulin
Copy link
Contributor

ffulin commented Dec 15, 2022

This is not a known general problem and is very likely something specific to your setup or codebase.

I can think of two possible reasons something like this might occur:
a) you have some cyclic dependencies, that for some reason are usually hidden but not when compiling a certain way
b) you are emitting the generated Unity files into the source folder of your code which is then feeding them back into themselves

To debug this issue, when you encounter the problem:
a) build from the command line with -showcmds
b) take the command shown and add /showIncludes (of if multiple passes are invoked and one has /showIncludes already, use that)

This should highlight where the bad include recursion is occurring.

@sergegers
Copy link
Author

Yes, there was a unity file on the input path. Thank you for clarification.

@ffulin
Copy link
Contributor

ffulin commented Jan 27, 2023

Conceivably something like this could be detected at bff parse time, but it could be tricky to allow for desirable edge-cases.

In any case, I'm glad you solved the problem. I'll close this issue as resolved in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants