+ if todir is None:
+ todir = os.path.join(os.path.join(os.environ["APPDATA"],
+ "Python-Eggs"),
+ name + "-tmp")
As a default, why not using the standard Windows temporary directory?
This is the directory also used by pkg_resources/setuptools. So, if the
specific egg was accessed before (not necessarily by pyinstaller), the
extracted contents already exist (pkg_resources puts them there) and can
be used by pyinstaller.
OK, makes sense. Could you please add a comment then?
Done. I also added a function borrowed from pkg_resources
`pkg_resouces_get_default_cache()` so the path will adhere to its
conventions on non-Windows systems too (and I fixed an issue I
accidentally created with os.path.altsep which is not set on those systems).
@@ -40,7 +42,7 @@
# to be self-contained. Extra care was put in writing it so
# that it does not share objects/memory with python.dll (which
# it loads).
- env.Append(CCFLAGS = ["/ML"])
+ env.Append(CCFLAGS = ["/MT"])
if flavour == "debug":
# No optimizations
Why is this required? Since there is no threading code in the
bootloader, and no sharing of standard library between the bootloader
and the application+python+pyds, I thought this was not necessary.
Ah, thanks for pointing me to this. I think actually the changes to
Sconstruct can be reverted/ignored, I added them waay back when I was
trying to build the bootloaders myself with MS Visual C++ 2008 Express,
and those changes allowed me to do it. But its not really necessary (I
think the same applies to the changes I made to run.rc and runw.rc).
OK, please revert them then. I will avoid merging the binary bootloaders
then, since they are not modified in your branch.
I reverted the changes, the files should now match whats currently in trunk.
I will merge the branch tomorrow or the day after. After the merge, I
will close (aka rm) the branch; you will have to switch your working
copies.
Ok!
Thank you very much for your great contribution! I would have been quite
lost in this manifest stuff without you :)
It was quite the exercise ;) but really interesting, I learned a lot
about WinSxS, and also pyinstaller in the process. And of course I'm
also benefitting from it :)
--
Florian Höch
--
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.
