Loading a macOS project on a Windows virtual machine
-
Hi @Pl45m4 ,
Thanks for this lead, which indicates that my problem is a configuration problem.
I have to admit that I'm a bit confused between my two Qt installations, the one on macOS and the one on Windows, because I can't configure the same settings for my project on one side and the other.
When I try to open a .pro file on the Windows side I get this message :
"No valid configuration files could be found.
All the configuration files found in the "Y:\Qt\Procedures4XP\Procedures4XP.pro.user" directory are not suitable for the current version of Qt Creator, for example because they were written by an incompatible version of Qt Creator, or because a different configuration path was used."I also don't understand anything about adding "kits" and configuring them...
-
@MortyMars yes that error is normal. from what little knowledge I have about Qt you see when you load the .pro file Qt creator looks for configuration file but they are different as Windows uses MinGW and Mac uses native files. I get that when ever I open up a project make in Windows on Mac and I just simply choose to configure the project.
I also do one more thing, the files on my Windows documents folder are synced with google drive so what ever change I make and what ever new files I add are automatically streamed to my mac
-
The .pro.user file can not be shared between different systems - it does not belong to the source tree even it is created in there by QtCreator
-
Thank you for these clarifications.
Unfortunately it doesn't tell me how to add the right kit and open my macOS project on Windows... -
@MortyMars said in Loading a macOS project on a Windows virtual machine:
my macOS project on Windows...
You can not compile MacOS under Windows.
Install Qt and QtCreator with the Qt online installer then QtCreator should automatically detect the Qt installation. When you want to use MSVC you also have to install it separately. Nothing more needed.
-
If you have a working Qt installation on Mac and Windows, you can copy the project over to Windows and delete everything from the project folder except the
.h
,.cpp
and oneyourProject.pro
file...
Everything else, files likesomething.pro.user
orsomething.pro5372527362
can be deleted. You can also delete the build folder if it's included in your project dir.
When you project is "clean", you just open QtCreator, load the project with "Open Project..." and then configure it using your local kit which is installed. -
@Christian-Ehrlicher said in Loading a macOS project on a Windows virtual machine:
You can not compile MacOS under Windows.
I understand that this is unfortunately not possible :-(
I misspoke, sorry.
I meant that I can't open the project created on macOS, in a Qt installation on Windows. -
@Pl45m4, @Aronox, @Christian-Ehrlicher
After running the maintenance tool to consolidate my Qt installation, and deleting the 'myproject.pro.user' file, the project finally opens under Windows. That's great!
Thanks a lot @Pl45m4 for the help.I'm just discovering my application on Windows and I can see that I'm going to have to do some work to make the interface look similar to what I have on the macOS side (in particular the alignment of the text in my QComboboxes, and the size of the QTextedit fonts).
But that's another subject that will no doubt open up new posts ;-)Thanks again to everyone.
-
-
@MortyMars here's how I do it, after I click to sleect a kit, i sleect the kit with the same Qt version (you have to have the same version installed to do this). And it just works.
See i have two debug files? That is one was created on MacOS and one on Windows. And "post_login" is the main project folder with the .h, .prp, .cpp and any other source files i have in there.
and google drive keeps the files synced between the two systems, no copying needed.
-
@Aronox said in Loading a macOS project on a Windows virtual machine:
(you have to have the same version installed to do this)
No you don't ;-)
Unless there are major differences in your code and you use features that one version has and the other don't, the same code can be configured, for example, using a Qt 6.6 Kit on Windows and a Qt 6.7 or Qt 6.5 Kit on Mac.
When configuring a project that originates from Qt 6.7 with a very ancient kit that uses Qt 4.8, you might face some difficulties ;-)
13/16