Segmentation fault: 11 when testing a Qt project in a MacOS virtual machine
-
wrote on 21 Oct 2017, 09:12 last edited by
Hi,
This is not really a question but a post for reference.
If you develop your Qt project on a Windows machine, as I am, and then try it out on a Mac OS X virtual machine (I use VMWare Player), then you will get an error like this one if you start the project from a shared folder that you mount via VMWare:clang: error: unable to execute command: Segmentation fault: 11 clang: error: clang frontend command failed due to signal (use -v to see invocation) Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin15.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script. clang: error: unable to execute command: Segmentation fault: 11 clang: note: diagnostic msg: Error generating preprocessed source(s). make: *** [audioengine.o] Error 254 15:18:18: The process "/usr/bin/make" exited with code 2. Error while building/deploying project mytest (kit: Desktop Qt 5.9.1 clang 64bit) When executing step "Make" 15:18:18: Elapsed time: 00:02.To avoid this error, I just copied the project to a local folder on my virtual Mac drive.
-
wrote on 21 Oct 2017, 16:31 last edited by Diracsbracket
Probably the project should also work from the VM Mounted drive if you set your shadow build directory to a Mac local drive instead. I did not think of that at first...
This then raises the question if you can set the shadow build directory in the .pro file or so and use selectors to switch between build environments. If that is possible, than I could use the same shared source directory for both my Windows and my MacOS Qt projects and avoid the copying to the local Mac drive.
-
Hi,
Usually you would use a VCS repository to share between the tow machines. You don't need a remote git server, you can use a local git repository and checkout your project from there. Simple stuff like file ending conversion is managed for you by git itself so you don't have to worry about that kind of difference between OSes.
-
Hi,
Usually you would use a VCS repository to share between the tow machines. You don't need a remote git server, you can use a local git repository and checkout your project from there. Simple stuff like file ending conversion is managed for you by git itself so you don't have to worry about that kind of difference between OSes.
wrote on 23 Oct 2017, 09:14 last edited by@SGaist
Great suggestion, thanks!
1/4