Strange timestamps for created executable about cx_freeze HOT 4 CLOSED

Original comment by Thomas Kluyver (Bitbucket: takluyver, GitHub: takluyver):

I think if there's a straightforward way to update the timestamp, it could be integrated into cx_Freeze. There's a function to embed an icon resource, for example, in source/util.c. But I don't use Windows much, and Anthony is very busy, so it's probably up to you - or anyone else who's interested - to write the code.

from cx_freeze.

Original comment by Sergio Pulgarin (Bitbucket: serpulga, GitHub: serpulga):

cx_Freeze.version = 4.3.1

I'm running a setup script.

Do you mean from my script or inside cx_Freeze code?

from cx_freeze.

Original comment by Thomas Kluyver (Bitbucket: takluyver, GitHub: takluyver):

What version of cx_Freeze are you using, and how are you freezing (with a setup.py script, or by running cxfreeze at a command line)?

My guess would be that the executables have a timestamp from when cx_Freeze was built, and it isn't updated when you freeze your program. Can you find what's necessary to update the timestamp?

from cx_freeze.

Closing due to inactivity.
cx_Freeze 6.1 has just been released.

from cx_freeze.