Simple question about freeze

[mrstephengross]

I'm working with the freeze utility, and I'm trying to learn the
basics. For the most part, I think I understand how it works. I have a
question about modules, though.

I want to make sure that my native executable is entirely standalone.
That is, it should have no dynamic linking. I've read through a number
of posts on the subject, and think I get it. In order to make this
work, I need to do two things:

(1) Recompile libpythonXXX.a so that the required modules are indeed
compiled into the archive.
(2) Modify the freeze-generated Makefile to force gcc to use static
linking and to use my custom-built libpythonXXX.a in linking together
the native executable.

My question is: is it sufficient to carry out the above steps? Freeze
is designed to use the version of python installed on the host system,
*not* a custom build in a different directory. If freeze looks to the
system's default installation, but I've modified the makefile to use my
custom-built libpython.a, will that cause problems? My sense is that it
will not, but I want to make sure I think things through. Any thoughts?

Thanks,
--Steve (mrstephengross at hotmail.com)