Compiler error when using an #include "..." on the first line of an .azsl file

[santipaprika]

AZSLc returns an error when the first line of an .azsl file contains an #include "...". It works well if it begins in the second line, or if the include has an #include <...> format.

To quickly reproduce, move the first #include "Skin_Common.azsli" from Skin.azsl to the first line (above the copyright notice).

[siliconvoodoo]

Azslc is not supposed to accept preprocessor directives. So this report probably needs to be moved toward the repository where the builders are.

Just tested mcpp alone, and seems to be working:

If issue there indeed is, it has to be related to some treatment in the builders, like include list processing:
https://github.com/o3de/o3de/blob/6912c88b0892f8e68a7c42935cc6e5eb7d2b355e/Gems/Atom/Asset/Shader/Code/Source/Editor/CommonFiles/Preprocessor.cpp#L291

Or around here
https://github.com/o3de/o3de/blob/6912c88b0892f8e68a7c42935cc6e5eb7d2b355e/Gems/Atom/Asset/Shader/Code/Source/Editor/ShaderAssetBuilder.cpp#L110

[CSteel22]

I've stumbled onto the same, if not similar, issue. My issue occurs with #include with angle brackets as well. My example below is using the shader code given in this tutorial: https://www.o3de.org/docs/learning-guide/tutorials/rendering/get-started-materialtypes-and-shaders/

When no empty line is present at the top of the .azsl file such as:

The following error is generated as though the "#include <viewsrg.srgi>" was not present:

However, when an empty line is placed at the top of the .azsl file as such:

No errors are generated in the Asset Processor by the Asset Builder.

[santorac]

I ran into this recently too, also with angle brackets. Moving it to the second line resolved the issue.

[santorac]

@galibzon We might want to consider prioritizing this fix for the upcoming release.

[tonybalandiuk]

@galibzon if you want to work on this for the upcoming release, we will need to do one of two things to make sure we track it properly either (A) move this issue into the main repo and assign it to the "Release/2210" milestone. OR (B) create a "Release/2210" milestone here in this repo and alert @AMZN-Dk and I that this milestone exists in this depot.

We are ok with either option. Thanks