On Thu, Apr 15, 2010 at 5:44 PM, Giovanni Bajo <[email protected]> wrote:

> On Tue, 13 Apr 2010 08:46:21 -0700 (PDT), Peter <[email protected]> wrote:
> > I'm running pyinstaller 1.4 with python 2.5 on Windows XP.  I've also
> > got UPX installed.  I can make functioning executables, but now I'm
> > trying to replace the default icon, but it's not working.  Using
> > ImageMagick, I converted a 32x32 png to an ico file, and then modified
> > my spec file to include the icon file.  Here's my spec file:
> >
> > # -*- mode: python -*-
> > a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'),
> > os.path.join(HOMEPATH,'support\\useUnicode.py'), 'makeisogui.py'],
> >              pathex=['V:\\pythonstuff'])
> > a.datas += [('mkisofs.exe', 'v:/pythonstuff/fdu/mkisofs.exe','DATA'),
> >       ('isolinux/initrd.img','v:/pythonstuff/fdu/isolinux/
> > initrd.img','DATA'),
> >       ('isolinux/isolinux.bin','v:/pythonstuff/fdu/isolinux/
> > isolinux.bin','DATA'),
> >       ('isolinux/isolinux.cfg','v:/pythonstuff/fdu/isolinux/
> > isolinux.cfg','DATA'),
> >       ('isolinux/vmlinuz','v:/pythonstuff/fdu/isolinux/vmlinuz','DATA'),
> >       ('isolinux/vesamenu.c32','v:/pythonstuff/fdu/isolinux/
> > vesamenu.c32','DATA'),
> >       ('isolinux/vsi_grub.jpg','v:/pythonstuff/fdu/isolinux/
> > vsi_grub.jpg','DATA')]
> > pyz = PYZ(a.pure)
> > exe = EXE( pyz,
> >           a.scripts,
> >           a.binaries,
> >           a.zipfiles,
> >           a.datas,
> >           name=os.path.join('dist', 'makeisogui.exe'),
> >           debug=False,
> >           strip=False,
> >           upx=True,
> >           console=False,
> >           icon='makeiso5.ico' )
> >
> > The icon file is in the current directory, same as the spec file, when
> > I run Build.py.  The resulting executable works, it just doesn't use
> > my icon.  Windows correctly displays the icon when I see it listed in
> > the file manager.  This seems similar to the bug that existed in 1.3
> > and was fixed in 1.4, fwiw.  Any ideas?
>
> Try with an .ico file that supports multiple resolutions. I know that it
> should not be needed, but I think it currently is. I should eventually drop
> the lame default icon which is causing these problems.
> --
> Giovanni Bajo   ::  [email protected]
> Develer S.r.l.  ::  http://www.develer.com
>
> My Blog: http://giovanni.bajo.it
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<pyinstaller%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/pyinstaller?hl=en.
>
> I made a 32x32 png file of the original 192x192 image I want for the icon,
along with a 64x64, a 128x128, and a 256x256.  Then I put those four images
into an .ico file using imagemagick's convert command, as described at
http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=14080.
Then, I specified that icon file in my spec file and generated a new
executable.  And...I still just get the default pyinstaller icon rather than
my icon.  Sigh.  I don't think it's relevant, but the four png files add up
to about 73K, but the resulting icon file from 'convert' is 359k!  That's a
lot of overhead.

I tried setting Debug=True, but that only applies to the runtime executable,
not the build stage.  Is there any other way to see why it's not taking the
icon?

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyinstaller?hl=en.

Reply via email to