Vitis Bug: xil_types.h: No such file or directory when creating platform project on Windows

[stmartin81]

When I try to compile a platform project with Vitis 2019.2 on Windows for my hardware I get the following error messages when trying to compile the platform project:

"Compiling bram"

In file included from xbram.c:56:
xbram.h:132:10: fatal error: xil_types.h: No such file or directory
 #include "xil_types.h"
          ^~~~~~~~~~~~~
compilation terminated.
In file included from xbram_g.c:33:
xbram.h:132:10: fatal error: xil_types.h: No such file or directory
 #include "xil_types.h"
          ^~~~~~~~~~~~~
compilation terminated.
In file included from xbram_intr.c:52:
xbram.h:132:10: fatal error: xil_types.h: No such file or directory
 #include "xil_types.h"
          ^~~~~~~~~~~~~
compilation terminated.
In file included from xbram_selftest.c:68:
xbram.h:132:10: fatal error: xil_types.h: No such file or directory
 #include "xil_types.h"
          ^~~~~~~~~~~~~
compilation terminated.
xbram_sinit.c:53:10: fatal error: xstatus.h: No such file or directory
 #include "xstatus.h"
          ^~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:20: libs] Error 1
make: *** [Makefile:30: microblaze_processor_system_microblaze_processor/libsrc/bram_v4_3/src/make.libs] Error 2

I can successfully compile the platform project on Linux. Somehow a lot of header files are not included in the MicroBlaze BSP project on Windows.

[hongh]

For Vitis, only SDK feature is supported in windows operating system.

[stmartin81]

What do you mean by only SDK feature is supported on Windows? This is a project I ported from Xilinx SDK to Vitis. It uses a MicroBlaze processor and the platform project was created with standalone as operating system. Is there an overview somewhere which features are supported on which platform?

[thisisbaback]

Why there's no answer to this topic? I have a same problem. My design works on linux, but not on windows. 

[vhdlwhiz]

I noticed that I got this error when moving my project to a OneDrive-synchronized folder. I experimented with creating the same project in "C:\Users\username\Downloads", which is offline. It works there, but not when I do the same in a folder that's backed up to OneDrive.

I tried turning off syncing, but the error persists.

Anyway, the workaround for me is to move the project to the Downloads folder when I want to work on it.

[tamas.kiss]

I had a similar problem, when I moved a project from one PC to another.

Both of them had Ubuntu 18.04 and Vivado/Vitis 2019.2 installed. The only difference was the installation directory of the tools. Vitis gave me a warning that it couldn't find some include file in the Vitis install directory. I had to delete my platform project and application projects altogether, and create them again.

Unfortunately it looks like Vitis stores full paths to everything by default, which is rather annoying.