To summarize that discussion: as part of the configuration process, meson wants to test the compiler tool chain to make sure it is callable and produces a working executable.
I cannot post U R L's here, but see the meson google group for that discussion. At first, I though it was related to a new version of the build tool but after tracking it down with the meson team it is actually due to a permissions issue with the virtualbox shared folder. Recently, after updating to a newer vagrant base image, my build tool (meson) started failing. I have been putting my projects in a shared folder with the host to accomplish this. For the projects I'm working on, I also need to be able to work on the project files with some tools on the Windows host. I use Virtualbox (through Vagrant) to get a Linux development environment on a Windows Host.
0 kommentar(er)
