Hi,
I rebuilt the spec and made the following changes but they didn't
prevent the message about pywintypes27.dll already existing when it
should not.
> pathex=['C:\\Python27\\pyinstaller-pyinstaller-ba163ef\\utils'],
> hiddenimports=[],
> hookspath=None)
I added \\utils and the hiddenimports and hookspath details.
Any thoughts?
All the best,
Grant
On 06/09/12 07:15, Grant Paton-Simpson wrote:
> Hi,
>
> I haven't rebuilt the spec yet but I noted that someone else had a
> virtually identical problem which they reported some details of in
> comment 4:
>
http://groups.google.com/group/pyinstaller/tree/browse_frm/month/2012-03?hide_quotes=no
>
> This was supposedly the solution (in my case the problem is
> pywintypes27.dll not pywintypes25.dll):
>
>> By the way, I think I've solved the mixed-case "PyWinTypes25.dll" issue:
>> in hook-pywintypes.py, I changed the format string on line 20 to all
>> lower case. With that done, I no longer get the "exists, but shouldn't"
>> warning message.
>
> Any thoughts? My plan is to make a new exe and test it to see if it
> avoids the false positive message from AVG.
>
>
> All the best,
> Grant
>
>
> On 05/09/12 22:35, Grant Paton-Simpson wrote:
>> Hi Martin,
>>
>> The dev version doesn't seem to trigger the same problem (from
>> initial experimentation). The exe created by the new version of
>> pyinstaller (but using the same spec file) gives an error message
>> when run but otherwise succeeds. The message is: WARNING: file
>> already exists but should not:
>> C:/DOCUMEN~1/GRANTP~1/LOCALS~1/Temp/_MEI1922\.\pywintypes27.dll
>>
>> I'll look at that tomorrow. Perhaps the issue will go away if I build
>> a clean spec file
>>
>> Here is the one I've been using:
>>
>>> # -*- mode: python -*-
>>>
>>> a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'),
>>> os.path.join(HOMEPATH,'support\\useUnicode.py'), 'C:\\dev\\launch.py'],
>>> pathex=['C:\\Python27\\pyinstaller-pyinstaller-ba163ef'])
>>> pyz = PYZ(a.pure, level=9)
>>> binary_includes = [('ssleay32.dll', 'C:\\Program
>>> Files\\wkhtmltopdf\\ssleay32.dll', 'BINARY'),
>>> ('libeay32.dll', 'C:\\Program
>>> Files\\wkhtmltopdf\\libeay32.dll', 'BINARY'),
>>> ('libgcc_s_dw2-1.dll', 'C:\\Program
>>> Files\\wkhtmltopdf\\libgcc_s_dw2-1.dll', 'BINARY'),
>>> ('wkhtmltopdf.exe', 'C:\\Program
>>> Files\\wkhtmltopdf\\wkhtmltopdf.exe', 'BINARY'),
>>> ('convert.exe', 'C:\\Program
>>> Files\\ImageMagick-6.7.8-Q16\\convert.exe', 'BINARY'),
>>> ('libiconv2.dll',
>>> 'C:\\Windows\\System32\\libiconv2.dll', 'BINARY'),
>>> ('pdftk.exe', 'C:\\Windows\\System32\\pdftk.exe',
>>> 'BINARY'),
>>> ('gswin32c.exe', 'C:\\Program
>>> Files\\gs\\gs9.06\\bin\\gswin32c.exe', 'BINARY'),
>>> ('gsdll32.dll', 'C:\\Program
>>> Files\\gs\\gs9.06\\bin\\gsdll32.dll', 'BINARY'),
>>> ]
>>>
>>> exe = EXE( pyz,
>>> a.scripts,
>>> a.binaries + binary_includes,
>>> a.zipfiles,
>>> a.datas,
>>> exclude_binaries=False,
>>> name='C:\\dev\\sofastats.exe',
>>> icon='C:\\dev\\images\\sofa_32x32.ico',
>>> strip=False,
>>> upx=False,
>>> debug=False,
>>> console=False)
>> Anyway, it looks like the trojan warning was probably spurious.
>>
>>
>> All the best,
>> Grant
>>
>>
>>
>> On 05/09/12 19:38, Grant Paton-Simpson wrote:
>>> Thanks Martin,
>>>
>>> I'll do some experiments and report back.
>>>
>>> All the best,
>>> Grant
>>>
>>>
>>> On 05/09/12 19:13, Martin Zibricky wrote:
>>>> Grant Paton-Simpson píše v St 05. 09. 2012 v 14:40 +1200:
>>>>> Any thoughts? I suspect it might be a false positive but obviously I
>>>>> need to be careful.
>>>> I think it's definitely a false positive. I don't know how to
>>>> modify the
>>>> bootloader code to make AVG happy. Could you try avg with development
>>>> version?
>>>>
>>>> I think this something for avg support. They experts could tell us
>>>> more
>>>> since they have access to source code.
>>>>
>>>
>>
>