put rendergraph_sg and rendergraph_gl in different namespaces #304
m0dBbuild.yml
on: push
Matrix: build
Update manifest file on download server
0s
Annotations
4 errors and 4 warnings
|
macOS 12 arm64
Process completed with exit code 1.
|
|
Windows 2019 (MSVC)
Process completed with exit code 1.
|
|
Ubuntu 22.04
Process completed with exit code 2.
|
|
macOS 12 x64
Process completed with exit code 1.
|
|
macOS 12 arm64
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|
|
Windows 2019 (MSVC):
src/rendergraph/opengl/backend/basegeometrynode.cpp#L19
'`anonymous namespace'::toGlDrawingMode': not all control paths return a value
|
|
Ubuntu 22.04:
src/rendergraph/opengl/backend/basegeometrynode.cpp#L19
control reaches end of non-void function [-Wreturn-type]
|
|
macOS 12 x64
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|