-
Notifications
You must be signed in to change notification settings - Fork 40
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
Can't compile in nested directory #104
Comments
You'd need src/broadcom/cle/ in the -I previously, for srcdir != builddir. nir was fine at that, but automake didn't have it. Bugzilla: #104
You'd need src/broadcom/cle/ in the -I previously, for srcdir != builddir. nir was fine at that, but automake didn't have it. Bugzilla: #104
|
Why close? It is not fixed by the change above. |
Is it not? It passed on travis for me, with a srcdir != builddir test added. |
src/broadcom/Makefile.am has "-I$(top_builddir)/src/compiler/nir ", which is where your built nir_opcodes.h should be. are you maybe trying to just build from a subdirectory of your builddir, instead of the whole thing? |
Yes, I am creating a build directory inside mesa directory. This is a typical approach I have used for many libraries, and it all worked fine. This is how you can preserve initial source tree from modifications. |
Oh, my bad, excuse me. |
When I create a nested build directory and then invoke configure & make from it I always get compilation errors, like:
In file included from /home/sergey/Projects/orpaltech/mesa-anholt/src/broadcom/compiler/v3d_compiler.h:36:0,
from /home/sergey/Projects/orpaltech/mesa-anholt/src/broadcom/compiler/vir_live_variables.c:29:
/home/sergey/Projects/orpaltech/mesa-anholt/src/compiler/nir/nir.h:48:25: fatal error: nir_opcodes.h: No such file or directory
#include "nir_opcodes.h"
^
compilation terminated.
The text was updated successfully, but these errors were encountered: