koobas.hobune.stream
Build errors : This function declaration is not a prototype.
When I build on Macbook I get like 8000+ this warning and can't run or build project. I looked like everywhere but no solutions clearly.
this goes like that , I tried on my windows project , also tried with new clean project but I got same error every time.
I found the solution : where to deactivate this warnings ! In Xcode, in the project settings (not the Target settings !), you have only 2 tabs : Info and Build settings (for the target settings you have more tabs) in the project settings, open the Build settings tab, in the bottom, you have "Apple Clang - Warnings - all languages" section, and in this section you have a line Strict Prototypes set to Yes by default : set it to No.
Say goodbye to this damn warnings ;)
I am getting the same problem. Has this been reported as a bug to Unity, yet? @enesatlam322 or @LordBelasco ?
I get the same problem but with 60.000 warnings, and I dont find a solution After a lot of research, it seems that Xcode 9 checks the prototype function, and a warning is added for empty param, if the word "void" is not added. example : int my_func(); > warning int my_func(void); > no warning
Unity dont add the word "void". It was possible to ignore this warning previously in Xcode, but it seems not possible now So no solution...
I found the solution : where to deactivate this warnings ! In Xcode, in the project settings (not the Target settings !), you have only 2 tabs : Info and Build settings (for the target settings you have more tabs) in the project settings, open the Build settings tab, in the bottom, you have "Apple Clang - Warnings - all languages" section, and in this section you have a line Strict Prototypes set to Yes by default : set it to No.
Say goodbye to this damn warnings ;)
I have seen many people say "oh, just deactivate the warnings" but no one ever explained how to deactivate them.
I am VERY thankful that you explained it, step by step.
While I don't like ignoring warnings, I was asked to do port this one project into the Apple store, and I would rather set myself on fire than keep working on Apple longer than I need. Seriously, THAN$$anonymous$$ YOU.
I don't do any iOS / xcode development. Though I think you should file a bug report in Unity and explain clearly what the issue is and how it should be fixed during the cross compiling. Suppressing warnings is never a solution just a workaround. Warnings are indicators that something isn't the way it's supposed to be. So this might be some outdated cross compilation issue which should be fixable on the Unity side.
Hey. Could you please report the issue with Unity Bug Reporter and provide a small example project?
