Hi,
xutuan Zhang wrote:
In your email When you said:
4a. Client applications
C++: rename your application with leading "_", copy unoapploader
binary in the same directory and rename it to your original
application name
If I have an add-in, e.g., MyAddin.uno.so and MyAddin.uno.rdb, do you
mean I should rename them to _MyAddin.uno.so and _MyAddin.rdb?
No. As Juergen said, this concerns client applications, i.e. program
binaries that use UNO rather than UNO components. I believe the reason
for this is that the process environemnt needs to be set up correctly
for UNO to work. The unoapploader does this and then executes the
renamed program (and it knows the name from its own name).
What do you mean by "unoapploader binary"? Should I copy it over and
rename it to, say, "MyAddin"?
No.
4b. UNO components
zip all necessary files into a zip file with the extension
*.uno.pkg,
create a manifest.xml with the appropriate entries
For details of UNO packages see the Developers Guide or ask me again.
Do I need "manifest.xml" if my addin is written in C++?
My package has the following structure now:
+MyAddinPkg.zip
|-- MyAddin.uno.so
|-- MyAddin.uno.rdb
(and it works under Windows XP/OOo 1.1.4/SDK 1.1.0 and latest snapshot
builds)
AFAIK manifest.xml is new with OOo 2.0 and wasn't needed for OOo 1.1.x.
Packages without manifest xml should still work for backwards
compatibility, but using the manifest.xml provides better control what
gets installed how.
HTH, Joerg
--
Joerg Barfurth Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer [EMAIL PROTECTED]
OpenOffice.org Configuration http://util.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
