Summary/Update: Re: Trying to build Ming SWF-output library with Python?

Antaeus Feldspar feldspar at ix.netcom.com
Tue Oct 2 18:05:55 CEST 2001


I want to thank everyone who helped me try and figure out what was going
wrong with the installation I described earlier.

Right now, the evidence supports what's said below:  that of
mingcmodule.so and mingc.pyd, only one of the two can be or should be
installed -- the former if on a Linux box and the latter if on Windows. 
This is probably why the "all" target of the Makefile was left blank;
unfortunately there was no documentation to explain that one should
select just one or the other to build.

Unfortunately the package is still not working correctly but I am
reasonably confident it is correctly installed.  Thank you all for your
help!

Chris Gonnerman wrote:
> 
> ----- Original Message -----
> From: "Second Trombone" <schmertz at wam.umd.edu>
> 
> > So to clarify, there are two "Ming"s, so to speak.  There's MinGW32
> > (actually stands for "Minimal GNU for Windows"), a port of GCC to
> > Windows; and then there's the Ming library for creating and manipulating
> > "Flash" files.  Could be that the makefile for "Ming the SWF library"
> > has a target to compile for use with "Ming the Windows compiler".
> 
> Exactly.  Sorry to have been so obscure; I shouldn't post late at night.
> 
> > For sure, that "dllwrap" command sounds very Windows-y.  If you're
> > compiling this for Linux, you may not even need the mingc.pyd target to
> > be compiled, I'm guessing.
> 
> Two cigars for you.  dllwrap is a command that hides much of the complexity
> of making Windows DLLs using MinGW32, and the mingc.pyd file would not be
> created on Linux (I imagine it would be mingc.so or mingcmodule.so based
> on standard usage.
> 
> > Silly question, but are you sure you downloaded the right "Ming"?
> 
> I suspect he did, and has just given an incorrect configuration option.
> 
> > Chris Gonnerman wrote:
> >
> > > I'm no expert on Ming but I use MinGW32... the GCC compiler suite
> > > for *Windows*.  Something is screwed in that Makefile; the target
> > > shouldn't even be SPECIFIED (so the default i386-linux would be
> > > selected).
> > >
> > > ----- Original Message -----
> > > From: "Antaeus Feldspar" <feldspar at ix.netcom.com>
> > > Newsgroups: comp.lang.python
> > > To: <python-list at python.org>
> > > Sent: Saturday, September 29, 2001 1:47 AM
> > > Subject: Trying to build Ming SWF-output library with Python?
> > >
> > >
> > >
> > >>I have been trying to install the Ming software library for output of
> > >>SWF ("Flash") files on my Linux box, and the Python bindings.  As far as
> > >>I can tell, installing Ming went without a hitch, but the Python
> > >>bindings were considerably hitched.  In particular, trying to make
> > >>"mingc.pyd" seemed to be the major problem, as it resulted in the
> > >>following log:
> > >>
> > >> ***
> > >>
> > >> bash$ make mingc.pyd
> > >> dllwrap --dllname mingc.pyd --driver-name gcc --def mingc.def \
> > >>   -o mingc.pyd ming_wrap.o -s --entry _DllMain at 12 \
> > >>   --target=i386-mingw32 -Llib/ -lpython15
> > >> make: dllwrap: Command not found
> > >> make: *** [mingc.pyd] Error 127
> > >> bash$
> > >>
> > >> ***
> > >>
> > >>>From what I've been able to make out from my research, the "mingw32"
> may
> > >>be just coincidence, and not related to the Ming software library.  In
> > >>any case, though, neither I nor any of my Linux friends have been able
> > >>to come up with what the Makefile *should* be to make it work.  Can
> > >>anyone shed more light on this?
> > >>
> > >>-jc
> > >>--
> > >>http://mail.python.org/mailman/listinfo/python-list
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >
> > --
> > Cheers,
> > Bob Schmertz
> >
> > --
> > http://mail.python.org/mailman/listinfo/python-list
> >
> >



More information about the Python-list mailing list