[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: beginning GSOC preparations: was Re: [pygame] Thank You



You can run everything from the Msys console, which is more Unix like. In Msys a Windows drive letter translates to a top level Msys directory of the same name. So C:\windows\system32 becomes /c/windows/system32. Add the Python root directory to the executable path and everything should work:

export PATH="<python root path>:$PATH"

The path must be in Msys form.

msys_build_deps.py installs everything to /usr/local in the Msys path (msys\1.0\local in Windows). DLLs go into the bin subdirectory.

Lenard

Tyler Laing wrote:


Normally things work for me, but I'm having a lot of trouble here, because nothing is clear, and Windows has the worst command-line utility around. This is by no means a condemnation of you guys, just that you guys are expecting more out of me, and its just not happening.

-Tyler

On Wed, Apr 22, 2009 at 4:34 PM, René Dudfield <renesd@xxxxxxxxx <mailto:renesd@xxxxxxxxx>> wrote:

    hi,

    try this:
    http://rene.f0o.com/~rene/pygame_mingw32_compile_pack.zip
    <http://rene.f0o.com/%7Erene/pygame_mingw32_compile_pack.zip>

    They are the installers for mingw stuff I last installed on my
    windows machine to compile pygame.  Other people have used those
    to successfully compile it too... so it should work.

    Also, if you get the dependency sources that Lenard collected on
    his page in one bundle:
    http://www3.telus.net/len_l/pygame/Pygame-1.9.0-deps-src.zip

    I think the directory structure matters too:

    # directory with all the source deps in it:
    pygame/

    # the trunk is here:
    pygame/PyGame/



    cu,



    On Thu, Apr 23, 2009 at 8:39 AM, Tyler Laing <trinioler@xxxxxxxxx
    <mailto:trinioler@xxxxxxxxx>> wrote:

        Unfortunately, it doesn't work. Does anyone have a better
        guide or series of steps to compiling pygame? Those steps
        should include properly install msys and associated packages.
        If not, I'll go over and start using the prebuilts. Thanks for
        the effort Lenard.

        -Tyler


        On Wed, Apr 22, 2009 at 2:55 PM, Lenard Lindstrom
        <len-l@xxxxxxxxx <mailto:len-l@xxxxxxxxx>> wrote:

            Did you install the Msys autoconf, automake and m4
            packages from sourceforge? They are found under the MSYS
            Supplementary section of the MinGW download page. I
            suggest using the most recent versions available.

            Lenard

            Tyler Laing wrote:

                Its failing on SDL. I tried running .autogen.sh in the
                directory, and this is what I got. I just made sure
                all the extra packages had been extracted to where
                they should be... including the update automake,
                autoconf and m4 tars.

                $ ./autogen.sh
                Generating build information using autoconf
                This may take a while ...
                Can't locate object method "path" via package
                "Request" (perhaps you forgot to load "Request"?) at
                /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1>
                line 111.
                Couldn't find autoconf, aborting


                On Wed, Apr 22, 2009 at 1:44 PM, Lenard Lindstrom
                <len-l@xxxxxxxxx <mailto:len-l@xxxxxxxxx>
                <mailto:len-l@xxxxxxxxx <mailto:len-l@xxxxxxxxx>>> wrote:

                   Which package are you trying to build. Unless the
                thing crashed
                   completely msys_build_deps.py should have displayed
                a listing at
                   the end showing where it stalled, that is, it will
                show which DLL
                   were not installed. The packages taken straight
                form SVN may not
                   have a .configure file. msys_build_deps.py will
                create those
                   automatically for SDL, SDL_mixer and smpeg. If any
                other packages
                   were taken from SVN then it will fail. To manually
                create a
                   configure file start the Msys console, go into the
                package's root
                   directory and type './autogen.sh'.

                   Anyway, the general Unix steps msys_build_deps.py
                takes to
                   installing a package are:

                   ./autogen.sh   # only for SVN packages
                   ./configure
                   make
                   make install
                   strip /usr/local/bin/<lib-name>.DLL

                   The msys shell scripts run to build the packages
                are found at the
                   end of msys_build_deps.py

                   Lenard

                   Tyler Laing wrote:

                       Okay, thanks! It went past that, but now its
                getting an error
                       that says:
                       /bin/sh: line 17: ./configure: No such file or
                directory

                       Any idea whats going on here?

                       On Wed, Apr 22, 2009 at 11:18 AM, Lenard Lindstrom
                       <len-l@xxxxxxxxx <mailto:len-l@xxxxxxxxx>
                <mailto:len-l@xxxxxxxxx <mailto:len-l@xxxxxxxxx>>
                       <mailto:len-l@xxxxxxxxx
                <mailto:len-l@xxxxxxxxx> <mailto:len-l@xxxxxxxxx
                <mailto:len-l@xxxxxxxxx>>>> wrote:

                          Hi Tyler,

                          I wrote msys_build_deps.py and look after
                the Windows
                          dependencies. I haven't seen this error
                before. I run the
                       program
                          on both Win 98 and XP. If you are using Msys
                1.0.10 try
                       upgrading
                          to 1.0.11. I only user 1.0.10 because 1.0.11
                doesn't work
                       on Win
                          98 and I have limited access to XP. Msys
                1.0.11 will be
                       needed to
                          build ffmpeg anyway, since the bash shell in
                1.0.10 is
                       apparently
                          too old for the ffmpeg configure script. If
                you continue having
                          problems then just use the prebuilt
                dependencies for now:

http://www3.telus.net/len_l/pygame/prebuilt-pygame1.9.0-msvcr71-win32.zip
                            (for Python 2.4-2.5)
                          (md5sum 0c9b5c65dbd10b5469d2523cf58b7890)

http://www3.telus.net/len_l/pygame/prebuilt-pygame1.9.0-msvcr90-win32.zip
                            (for Python 2.6-3.x)
                          (md5sum 8dcd7e7c840d656c3ca7576095777c81)

                          Install the prebuilt directory into the
                Pygame root
                       directory, run
                          config.py and answer 'n' to msys built, 'y'
                to use prebuilts.

                          I suppose now I must really try to get
                ffmpeg built.

                          Lenard

                          Tyler Laing wrote:

                              Not python under cygwin. Thats a
                leftover string from msys
                              using cygwin code. The command I was
                trying to execute was
                              python msys_build_deps.py --all

                              Python is installed. Msys is installed,
                but throwing
                       that error.

                              And no worries. I just wasn't clear
                enough. :)

                              -Tyler

                              On Wed, Apr 22, 2009 at 10:24 AM, Evan
                Kroske
                              <e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx> <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx>>
                       <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx> <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx>>>
                              <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx> <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx>>
                       <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx> <mailto:e.kroske@xxxxxxxxx
                <mailto:e.kroske@xxxxxxxxx>>>>> wrote:

                                 Tyler Laing wrote:

                                     <snip />


                                     The error says that it "Couldn't
                reserve space
                       for cygwin's
                                     heap, Win32 error 6" when sh.exe
                was executed.

                                 Why are you trying to install Python
                under CygWin?
                       From what I
                                 understand, most programmers consider
                that a
                       separate platform
                                 from Windows. You should probably try
                to install the
                       native
                                 windows version, instead of the linux
                version
                       running under
                                 cygwin. Sorry if I misunderstood you.






-- Visit my blog at http://oddco.ca/zeroth/zblog





-- Visit my blog at http://oddco.ca/zeroth/zblog





--
Visit my blog at http://oddco.ca/zeroth/zblog