John,
John Emmas writes:
At the time I tried versions 2.7 and 3.1 but they both gave me the same
problem. Going back to Tarnyko's email
On 17/07/2013 19:55, Tarnyko wrote:
- in gdbus-codegen, we have :
path=$PATH:/lib/gdbus-2.0
from codegen import codegen_main
That's a bit
Hi John,
(list people: I understand this is a rather old topic that was brought
up few months ago:) ).
I was poking around with the Python scripts for gdbus-codegen lately,
and I thought it might be good to let you know a few things about its
use on Windows, especially under Visual Studio builds
Hi Fan,
Thanks for sharing. FYI, MinGW makefiles from latest master generate and
install gdbus-codegen correctly. You may want to take inspiration from
them if you plan to add gdbus-codegen generation for MSVC (don't know this
toolchain enough to do it myself).
I just suggested a little
Thanks guys.
My memory is hazy now but from what I can recall, any lines like this
were always problematic;-
from . import some_module
No matter what I did, I couldn't get (Windows) Python to understand what
from . meant. If the module to be imported was in a subfolder - e.g.
Hmmm, that's strange, works here.
- in gdbus-codegen, we have :
path=$PATH:/lib/gdbus-2.0
from codegen import codegen_main
- and in /lib/gdbus-2.0/codegen/codegen_main.py we have :
from . import config
where config.py is in the same directory.
Using Windows (not MSYS) Python 2.5, and
Hi John,
[Tarnyko wrote: ]
Hmmm, that's strange, works here.
- in gdbus-codegen, we have :
path=$PATH:/lib/gdbus-2.0
from codegen import codegen_main
- and in /lib/gdbus-2.0/codegen/codegen_main.py we have :
from . import config
where config.py is in the same directory.
Using Windows (not MSYS)
On 18/07/2013 02:04, Fan Chun-wei wrote:
I also ran Python 2.7 in both x86 and x64 flavors in the same way
Tarnyko ran the script (which I built myself using Visual Studio, so
this is a native Windows build/version of Python, running under
cmd.exe), and this worked for me too.
Thanks
