Kai, I opened a ticket at Qt support.
I could find no qtlicences.ini files. Only “.qt-license”. Thanks for the tips! -Ed On Jul 2, 2015, at 9:25 AM, Koehne Kai <kai.koe...@theqtcompany.com<mailto:kai.koe...@theqtcompany.com>> wrote: -----Original Message----- From: Edward Sutton [mailto:edward.sut...@subsite.com] Sent: Thursday, July 02, 2015 3:50 PM To: Koehne Kai Cc: Interests Qt Subject: Re: [Interest] Where to does Qt expect to find ".qt-license" file when running on a Jenkins slave machine? Kai, Thank you for your help. On a Windows 7 VM machine it installs to: C:\Users\edward3\.qt-license When logged on as edward3 all is good. This same machine operates as a Jenkins slave. Dumping the environment from the Jenkins job: USERDOMAIN=WORKGROUP USERNAME=WIN7X64-ESUTTON$ USERPROFILE=C:\Windows\system32\config\systemprofile I tried copying C:\Users\edward3\.qt-license to the following without success: C:\Windows\System32\config\systemprofile\AppData\Roaming\Qt\.qt- license Actually it searches for a 'qtlicenses.ini' file here, that is usually created & updated by the Qt Installers... C:\Windows\System32\config\systemprofile\.qt-license This location should work. Please double check that the file is there (without any hidden .txt suffixes or so), and that your Jenkins job has read access to it. C:\jenkins\.qt-license I had the slave building before using Qt Enterprise. What could have changed I do not know? One difference is that the license is now checked for the licenses also when running qmake, see also the ChangeLog. In earlier versions it was only run at configure time. May I suggest to open a ticket via the Qt Support? Regards Kai This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest