Installing Qt Creator for colleague

[ecorm]

I need to set up a complete development environment for a colleague who will be working remotely, which includes Qt Creator (and not the Qt libraries). We are using Qt Creator under the terms of the open source license. The project is CMake-based and Qt Creator is used as an IDE only (a kickass IDE!). We could just as easily be using VS Code.

My question is how can I set up Qt Creator on my colleague's machine without sharing Qt Account passwords? In the Qt Maintenance Tool running on my machine, I see no way to change Qt Accounts, nor how to make it forget my Qt Account credentials.

[ecorm]

@ecorm said in Installing Qt Creator for colleague:

I've found the --reset-qtaccount option from the online installer. Is it as simple as this?

1. Use my own credentials for the installation
2. Run the installer again with --reset-qtaccount
3. Having my colleague enter their Qt Account credentials in the Maintenance Tool after I handover the development machine to them?

I've had my colleague create their Qt Account with a temporary password that's been shared with me, with the understanding that my colleague will change their password once they receive their development machine. With that information in hand, I tried using --reset-qtaccount option that I discovered for the installer. However, when the installer gets to the Installation Folder step, it complains about the destination directory already existing.

It turns out that the MaintenanceTool also has the --reset-qtaccount option. I've tried this using my colleague's Qt Account credentials, and performed an update operation. However, the next time I launch the MaintenanceTool, it's still my email that shows up as the Qt Account username. If I enter my colleague's Qt Account credentials, it complains that it doesn't match the ones used for installation.

I ended up reinstalling from scratch using my colleague's credentials with the temporary password. I wish there was a cleaner way of doing this without having to share temporary passwords.

In case anyone is wondering, I'm taking this opportunity to document the steps involved in setting up a new development environment, so that a new programmer can do it themself using their own credentials.

I should also clarify that the new programmer can ultimately use whatever editor or IDE they want, as long as no major changes are required to the CMake scripts. It's just that I'm required to provide them with a working IDE that can debug our code, so that they can hit the ground running.

[ecorm]

While I'm at it, might I suggest that a standalone Qt Creator (without the Qt libraries) be made freely available (without an account) for C++ enthusiasts and students? That could be a way to promote your other commercially-licensed products (as long as it's not too nagging). Beginners who learn C++ using Qt Creator might be more tempted to reach for Qt in their future endeavors when they need a UI.

[ecorm]

I've found the --reset-qtaccount option from the online installer. Is it as simple as this?

1. Use my own credentials for the installation
2. Run the installer again with --reset-qtaccount
3. Having my colleague enter their Qt Account credentials in the Maintenance Tool after I handover the development machine to them?

[ecorm]

@ecorm said in Installing Qt Creator for colleague:

I've found the --reset-qtaccount option from the online installer. Is it as simple as this?

1. Use my own credentials for the installation
2. Run the installer again with --reset-qtaccount
3. Having my colleague enter their Qt Account credentials in the Maintenance Tool after I handover the development machine to them?

I've had my colleague create their Qt Account with a temporary password that's been shared with me, with the understanding that my colleague will change their password once they receive their development machine. With that information in hand, I tried using --reset-qtaccount option that I discovered for the installer. However, when the installer gets to the Installation Folder step, it complains about the destination directory already existing.

It turns out that the MaintenanceTool also has the --reset-qtaccount option. I've tried this using my colleague's Qt Account credentials, and performed an update operation. However, the next time I launch the MaintenanceTool, it's still my email that shows up as the Qt Account username. If I enter my colleague's Qt Account credentials, it complains that it doesn't match the ones used for installation.

I ended up reinstalling from scratch using my colleague's credentials with the temporary password. I wish there was a cleaner way of doing this without having to share temporary passwords.

In case anyone is wondering, I'm taking this opportunity to document the steps involved in setting up a new development environment, so that a new programmer can do it themself using their own credentials.

I should also clarify that the new programmer can ultimately use whatever editor or IDE they want, as long as no major changes are required to the CMake scripts. It's just that I'm required to provide them with a working IDE that can debug our code, so that they can hit the ground running.