On Wed, May 28, 2008 at 3:24 PM, Dinesh Chothe <[EMAIL PROTECTED]> wrote:
Hi Dinesh, > How do I achieve this? you should use unopkg in your installer (it's located in OO.o/program directory). For example ... unopkg add -f myextension.oxt ... this command installs your extension (-f means force). Run unopkg without arguments to get more info about arguments. > Can anybody guide me how do I solve this problem? My recommendation is NSIS. You can write install scripts easily and then generate exe installation file. You should do it in this way ... - get info from registry, where OO.o is installed - run <OO.o install path>/program/unopkg add -f yourextension.oxt - copy additional files somewhere ... this can be done in several minutes. I've never saw NSIS few weeks ago and I was able to write installation program very quickly. Question is - why are these files outside .oxt? There is API, which gives you a possibility to access files in .oxt, so, you can easily include them in .oxt too. P.S. Do not cross post you questions to dev and dev-api mailing lists, thanks. -- Robert Vojta --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
