Thanks Pietro,
I'm replying on the mailing list to keep this discussion in public, so
others can weigh in too. A few thoughts on your charmingly written document
:)
- You intend to use the cxfreeze script. I'd advise against this, because
it only supports a limited set of options. I'd suggest that for Eric, it's
worth biting the bullet and using cx_Freeze's classes directly. This would
allow you to e.g. generate a list of required modules that cx_Freeze will
package, and allow the user to add and remove items from the list before
packaging it.
- I agree that the different bases and initscripts could be better
explained in our documentation.
- For most of your users, Win32GUI will indeed be the correct base - the
Console base will pop up an annoying empty command prompt window. But note
that the Win32 bases are only needed or available on Windows.
- KeepPath means that the application can load Python modules installed
on the target system. Otherwise, it can only import libraries packaged with
it.
- The 3 suffix on some initscripts means they are versions for Python 3.
- If you see problems with dependency detection that you think can be
resolved, please let us know. The most common problem is with dynamically
loaded code (e.g. plugins) that we don't have any good way to detect.
- You express an interest in how DLLs get included. I think this came up in
another thread, but in brief: cx_Freeze includes platform-specific
functions to scan binary files and find their dependencies. In this case,
the .pyd files you see require the .dll files.
- The issue with the re module should be sorted out in the next release.
See pull request 18.
- We're interested in improving the situation with the MSVCR, but it seemed
to be an unclear legal situation when we looked into it. I forget the
details, but it was something like only people with the paid version of
Visual Studio could officially distribute those DLLs.
- Qt image formats issue: there's code already in to automatically copy the
imageformats plugins [1]. Can you test that.
- Odd Qt paths: Most likely refer to Qt resources, files which get stored
in the code itself.
- QtDeclarative error: haven't come across it before. It sounds like it
might be as simple as adding an extra hook.
- Subprocesses when freezing the eric editor: how and when is it starting a
subprocess? Some things are different in the frozen application, e.g.
sys.executable points to your exe, not to a Python interpreter.
[1]
https://bitbucket.org/anthony_tuininga/cx_freeze/src/d9461c3d4ff5c91f0405e1e5993b18bbdc0390aa/cx_Freeze/hooks.py?at=default#cl-466
Hope that helps - please feel free to follow up with questions.
Thomas
On 25 April 2013 09:42, Pietro Moras <[email protected]> wrote:
> Dear Thomas,
>
> Purpose of this “E(5)-PrjPackager – Tech.Report” (see attached
> “Cover+Contents”), now available at URL:
> https://www.box.com/s/uzw8f77jyqlidbq8vv35
>
> is that of building together a valid opportunity of understanding and
> improvement between cx_Freeze people and the Eric users' community. Looking
> forward collaborating with you, to the common benefit.
>
> All the best.
>
> - P.M.
>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
cx-freeze-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
