Alright, the files are all going in.  Your suspicion about the .zcml  
file not working when it is included in the zipped library directory  
was correct.  There is way to make my app without the .zcml file, so  
I'm going try that.

> If you need any help with that, please provide a small Zope example
> that I can run that uses the configuration file. If you do so, it
> might be convenient to include as another example in the cx_Freeze
> distribution.

I have never made a straight up zope app, so I can't do this very  
easily.  If I can get my non-zcml method to work, though, I'll be  
happy to send something your way that will help out with the examples  
for the cx_freeze distribution.

I'll let you know tomorrow how it goes.

Craig


On Mar 2, 2010, at 7:38 AM, Anthony Tuininga wrote:

> On Tue, Mar 2, 2010 at 6:59 AM, Craig Swank <[email protected]>  
> wrote:
>> Ah - ha!  It worked.  Mostly.  My namespace packages are going into
>
> Hooray! :-)
>
>> the library.  The executable still won't run, however, because a non-
>> python configuration file did not get copied over.  It is a .zcml  
>> file
>> that the zope world uses.  I think it would be nice if all files
>> inside a package were copied into the library (except .pyc files, of
>> course).  Is there a fix for that?  If not, I could just unzip the
>> library, put the missing file in, then zip it back up, right?
>
> Actually, there is a way of dealing with that. Specifically, you can
> use include_files (to include files in the distribution outside of the
> library.zip) or zip_includes (to include files inside the zip file).
> Note, however, that you need to consider whether or not Zope (or any
> other module with data files) has support for a frozen executable. In
> most cases I would suspect that you want to use include_files and not
> zip_includes but I could be wrong -- I don't know how Zope works its
> magic. :-)
>
> If you need any help with that, please provide a small Zope example
> that I can run that uses the configuration file. If you do so, it
> might be convenient to include as another example in the cx_Freeze
> distribution.
>
>> Thanks again for your persistence.
>
> You're welcome. Thanks for your patience! :-)
>
> Anthony
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> cx-freeze-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cx-freeze-users


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
cx-freeze-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users

Reply via email to