Hi,
the name clash of pyuno.ddl and a directory named pyuno (which can be a
module and a file __init__.py would initialize the module) might be the
problem please try to rename the pyuno directory to pyuno2 in the
output tree, change this also in PYTHONPATH and try again. The treatment
of dlls and directories in PYTHONPATH might have changed with 2.5.
You don't have to think about the __init__.py file, you dont need it.
Bye,
Joerg
Liyuan(Internet) wrote:
Hi Joerg,
The pyuno.dll can be found within pythonpath.
but pyuno.dll can be loaded.
Now when I run python.exe , which is in
ooo_SRC680_m172_src\solver\680\wntmsci10.pro\bin,
and load pyuno,the error information as follows:
/*--------------------------------------------------------------------------------------------
import pyuno
warning: Not importing directory 'pyuno': missing __init__.py
warning: Not importing directory 'E:\ooo_SRC680_m172_src\solver\680\wntmsci10.pr
o\bin\pyuno': missing __init__.py
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named pyuno
----------------------------------------------------------------------------------------------*/
the '__init__.py' file cann't be found in
'E:\ooo_SRC680_m172_src\solver\680\wntmsci10.pr
o\bin\pyuno',
but the file is not included in the same directory of the python-2.3.5.
I added an empty file '__init__.py' into the directory,
there isn't any error information came out when I run the command 'import pyuno'.
but when I dmake runtest in the \testtools\source\bridgetest\pyuno, the error
information
as follows:
/*---------------------------------------------------------------------------------------------
[e:\ooo_src680_m172_src\testtools\source\bridgetest\pyuno]dmake runtest
dmake: Executing shell macro: +echo %_cwd
dmake: Executing shell macro: +echo %_4ver
starttestwithdmakeruntest
-------------
dmake: Executing shell macro: echo import os;print os.getcwd() | $(PYTHON)
cd ..\..\..\wntmsci10.pro\bin && set FOO=file:///E:/ooo_SRC680_m172_src/testtool
s/source/bridgetest/pyuno/../../../wntmsci10.pro/bin && set UNO_
TYPES=pyuno_regcomp.rdb && set UNO_SERVICES=pyuno_regcomp.rdb && python main.py
Traceback (most recent call last):
File "main.py", line 35, in <module>
import uno
File "e:\ooo_SRC680_m172_src\solver\680\wntmsci10.pro\bin\pyuno\uno.py", line
42, in <module>
_g_ctx = pyuno.getComponentContext( )
AttributeError: 'module' object has no attribute 'getComponentContext'
dmake: Error code 129, while making 'runtest'
'---*tg_merge.mk*---'
------------------------------------------------------------------------------------------------*/
I think that the file '__init__.py' has initialized environment before
pyuno.dll be loaded in python-2.5 ?
but I initialized pyuno environment with an empty file '__init__.py',
So I think the pyuno.dll is not actually loaded.
wht should I do next ?
Thank you
Liyuan
----- Original Message -----
From: "Joerg Budischewski" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, December 05, 2006 4:11 AM
Subject: Re: [udk-dev] C++ - command line tool to convert VC project files to
Makefile
Hi,
this can have several reasons, difficult to diagnose from here.
Please check your PYTHONPATH environment variable, pyuno.dll must be
found within pythonpath.
You should start a python process within the ms debugger to check
whether the pyuno.dll is actually loaded (dll loading is somewhere
logged). When pyuno.dll gets loaded, try to put a breakpoint in
initpyuno() in pyuno/source/modules/pyuno_module.cxx.
Bye,
Joerg
Liyuan(Internet) wrote:
Hi Joerg, hi all,
I have rebuilt and delivered the pyuno module.
In the process there is no error.
The pyuno.dll is updated.
but pyuno still can't be imported to .
Liyuan
----- Original Message -----
From: "Joerg Budischewski" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, December 02, 2006 4:19 PM
Subject: Re: [udk-dev] C++ - command line tool to convert VC project files to
Makefile
Hi,
try to rebuild and deliver the pyuno module before. The pyuno.dll is
built there.
Bye,
Joerg
Liyuan(Internet) wrote:
Hi Joerg, hi all,
Thanks for your replying!
I have converted VC project files(.dsp) to Makefile for the Python-2.5 Source.
I have rewrote the patch file (Python-2.5.patch), and compilied successfully.
but when I run the testtools,errors appear as below:
//----------------------------------------------------------------------------
[e:\ooo_src680_m172_src\testtools\source\bridgetest\pyuno]dmake runtest
dmake: Executing shell macro: +echo %_cwd
dmake: Executing shell macro: +echo %_4ver
starttestwithdmakeruntest
-------------
dmake: Executing shell macro: echo import os;print os.getcwd() | $(PYTHON)
cd ..\..\..\wntmsci10.pro\bin && set FOO=file:///E:/ooo_SRC680_m172_src/test
s/source/bridgetest/pyuno/../../../wntmsci10.pro/bin && set
TYPES=pyuno_regcomp.rdb && set UNO_SERVICES=pyuno_regcomp.rdb && python main
Traceback (most recent call last):
File "main.py", line 35, in <module>
import uno
File "e:\ooo_SRC680_m172_src\solver\680\wntmsci10.pro\bin\pyuno\uno.py", l
37, in <module>
import pyuno
ImportError: No module named pyuno
dmake: Error code 129, while making 'runtest'
'---*tg_merge.mk*---'
//------------------------------------------------------------------------------------
Any idea of how to get rid of the problem?
Thanks
Liyuan.
Hi,
indeed microsoft removed support for exporting makefiles in VC2003 and
later. I have yet no good idea, how to do a python build now, I saw that
support for vc6 is still there (which can generate makefiles), but I
don't know, if everything works with it ... (and you would need to adapt
them to the new compiler).
Bye,
Joerg
Liyuan wrote:
hi all
Does anyone know of a Windows compatible command line tool that capable
of parsing Microsoft's VC++ workspace/project (e.g., .dsw, .dsp, .sln,
..vcproj, etc.) files and generating an nmake-compatible Makefile.
Thanks.
Liyuan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
