Re: [Civil-devel]Ignore previous mail, got it running...

[Jan E. <ch...@in...>]

On Tue, 12 Oct 2004, Gareth Noyce wrote:

>> You mean the installation actually worked for you? At least on Linux
>> there
>
>No, not at all. :(
>
>I just created a new directory, threw the src etc directories in there,
>compiled the c extension and edited properties.py - took a bit of
>fiddling was all.

So it would've worked just fine from the same directory where you unpacked
it all? As there is no way to get an universal installer and distutils
falls a bit short, I think that just unpacking the Civil source package
and compiling the C files should be enough. Distutils can do the
compilation though.

>> is still the matter with the binaries, where should they go? Other than
>> that I think most stuff should get installed just fine in
>> /usr/lib/python/site-packages/civil/. Alternatively the installer could
>
>Yeah, I'll need to check what I did, as setup.py didn't bother making
>the civil directory. I also dunno if that's on the default OS X path -
>not that it matters if I can work out how the app bundle stuff does its
>thing.

Hm, it may actually not do the civil directory at all...

>Speaking of which, I've got an application bundle running arbitrary
>python scripts. It's just normal #! /usr/bin/python stuff, but in a
>specific directory structure.
>
>Unfortunately, on the Mac there's a python for the terminal, and one
>for anything that needs the window manager (pythonw). I've no idea why
>this is the case, but my little app bundle hack doesn't seem to work
>with pythonw. Still trying to work this out atm...
>
>There's an app bundler thing as well, which I can try, but it puts all
>the frameworks and stuff in the application as well, which would mean a
>massive download. I'd rather that wasn't part of Civil's dist, tbh...
>
>> instead of copying files create them? Or instead of binaries in
>> /usr/bin/
>> or /usr/games/ just create suitable .desktop files in the proper
>> directory
>> (I think /usr/share/applications/games/, or something like that). The
>> .desktop file could specify a line like this as the executable:
>>
>> Exec=python -c "import civil....; civil.main()"
>>
>> For Windows there is probably something similar that could be created?
>
>For win32 I'd be tempted to dish out a py2exe'd up version? I'm not
>sure what the defaults for that machine are these days, been so long
>since I did any work on them.

Not used Python on Win32 for a few years, so I'm not sure of what works
there, but I'd say that anything that can be done for Linux can also be
done for the Windows side.

-- 

             Gravity is a habit that is hard to shake off.
                                              -- Terry Pratchett, Small Gods