Hi,
to load the pyuno.dll using LoadLibrary() function and call the initpyuno()
function.
I change the makefile, now the pyuno_loadwrapper.obj has been built,
but I don't know how to generate the wrapper pyuno.pyd shared library using the
pyuno_loadwrapper.obj .
Could you give me some advic
Hi,
thinking about adding python import functionality to pyuno during the
last years, I have come to the proposal outlined in
http://www.openoffice.org/issues/show_bug.cgi?id=76281
.
The solution is very simple and solves imho 90% of what can be solved. I
have spent a lot of time thinking a
Hi,
when I looked it up correctly, the cws python25 is still in state new.
What the state currently ?
Bye,
Joerg
Peter Junge wrote:
Hi all,
I am back in Beijing and I will have some time to study the project
pages now. Just one question at this point. Do we have a project
schedule for thi
ye,
Joerg
Joachim Dahl wrote:
Maybe I got a small step further. I received a few advices from Jörg
Budischewski:
Say, I define my IDL like this:
interface Xcvxopt : com::sun::star::uno::XInterface
{
string lp( [in] sequence < sequence < long > > c,
[out] sequence
what I actually wonder about is that you choose a "matrix" signature,
but your sample only takes vectors, maybe change your addin to vectors
or your sample to matrixes, just to see, how it behaves.
But as I said, i dont know calc good enough.
Bye,
Joerg
Joachim Dahl wrote:
thanks, this bro
Hi,
it seems, that the python process cannot find the core typedescription,
they are usually located in the /path/to/office/program/types.rdb. Just
for a test, try
export UNO_TYPES=file:///path/to/office/program/types.rdb
python hello_world.py
(note that /path/to/office is a file url, e.g. a
Hi,
for pyuno, I would address the issue the same way you have addressed
it for the office, thus let python.bat/python.sh set the URE_BOOTSTRAP
variable.
That was my first thought, too.
> But then I noticed that python.sh (and
the python symlink pointing to it) are only included #ifndef
Hi,
python is the public interface, python.sh is an implemetation detail.
I actually introduced this because I didn't know how to create a python
script with our installation procedure when there is the python as
executable in the solver path in the build environment. (In the build
env, it is