Hi, I am having a lot of build issues with vex PROS on vscode. My current project is on GitHub as a repository and it works and builds fine on both my home laptop and my teammate’s laptop. However, when trying to use the same repository on my surface, the build fails. I am unable to clean my project and I can’t afford to create a new project since the code works on other devices. I have looked at other vex forum posts but nothing works for me. There are also compilation errors that are exclusive to my surface which all stem from the fact that system headers cannot be found. What’s more, some old projects still work fine on my surface with no issues, though I cannot find any discrepancies between the files. Here are some images of the the issues that I have seen. I have also detailed other stuff I have tried below.
I have tried to delete the files in the pros folder under appdata and then install
copying makefiles and compile_commands.json from projects that do build on my surface succesfully
This is not the first time the issue has occurred for me, and it keeps happening, with the same sort of build issues. It is really important it works on my surface since it is what I take to school. Any help would be greatly appreciated. I can provide some more information if necessary.
By the way, this is my first time posting on the Vex Forum so please tell me if I need to do anything else with this post
Is it only this project that is unable to build, or do you encounter this error on every PROS project? The problem seems to be that the toolchain does not have write permissions to the bin and .d folders, which is something I have not seen before. If it only happens on this project, you should ensure that those folders are set to be writable, modifiable, etc by anybody in their security settings. If it happens on every PROS project, it sounds like your IT department has blocked unknown applications from having write permissions. Please let me know the results of testing my first question.
Hi, thank you for reaching out. To answer your question, this is not true for every project: it works on a particular project that I created on my laptop. I tried to copy over the makefiles and compile_commands.json from that project into my new project. In fact, I was able to get the program that had these issues to clean and build through this. However as soon as it cleaned and rebuilt, future builds continued to break. I can try and send a screenshot of that issue. It is a really strange problem, though I believe there are some issues that are to do with permissions. I will see how I can circumvent these permission issues and see if that is the fix.
Hi quick update @BennyBoy. I went to IT support and they tried running vscode as an administrator as well as messing around with the permissions of the .d and .bin folders (basically everything you said to do). Sadly, nothing works so I am not sure what to do. If anyone has come across this issue before and fixed it, please feel free to say what you did. If I ever come around to fixing the problem, I will try to outline exactly what I did. Once again, thanks for the help.
