You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--WARNING: This bug may only be pertinent to the MacOS platform--
Whenever trying to compile the Hazel library, the compiler complains how it cannot find the hzpch.h file. I suspect that Hazel's premake5 build file is causing the issue. Specifically, this line:
The hzpch.h file is not in the project's root folder, but it's inside the source folder.
Once I changed that line of code in Hazel's premake5 file, the issue was fixed.
However, I'm not sure if this is an issue on Windows, and if this fix will affect the Windows build. If this fix doesn't cause any problems, I would be happy to open a pull request.
To Reproduce
Steps to reproduce the behavior:
Build Hazel as normal
Expected behavior
The compiler to find hzpch.h file without issue.
Operating system: (please complete the following information)
OS: MacOS
Version: 15.1.1
Additional context
This may only be an issue on MacOS.
The text was updated successfully, but these errors were encountered:
Describe the bug
--WARNING: This bug may only be pertinent to the MacOS platform--
Whenever trying to compile the Hazel library, the compiler complains how it cannot find the hzpch.h file. I suspect that Hazel's premake5 build file is causing the issue. Specifically, this line:
The hzpch.h file is not in the project's root folder, but it's inside the source folder.
Once I changed that line of code in Hazel's premake5 file, the issue was fixed.
However, I'm not sure if this is an issue on Windows, and if this fix will affect the Windows build. If this fix doesn't cause any problems, I would be happy to open a pull request.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The compiler to find hzpch.h file without issue.
Operating system: (please complete the following information)
Additional context
This may only be an issue on MacOS.
The text was updated successfully, but these errors were encountered: