DevZone: Difference between revisions

From wiki.jriver.com
Jump to navigation Jump to search
No edit summary
 
Line 2: Line 2:


==Package Files==
==Package Files==
Here's an example from scthom that shows how to package a plug-in and the MJP file in a single zip:
Here's an example from scthom that shows how to package a plug-in and the MJP file in a single zip.
It is required by the way SourceForge hosts files, though having the MJP outside the zip file and
a real link for the URL is easier.


:[Package]
:[Package]
Line 13: Line 15:
:File1=in_wavpack.dll
:File1=in_wavpack.dll
:File1Action1=COPY_PLUGINDIR
:File1Action1=COPY_PLUGINDIR
:File1Action2=REG_PLUGIN[/code]
:File1Action2=REG_PLUGIN


Use Action=NONE when the mjp is inside the zip.
Mine are Action=NONE because the mjp is inside the zip and in order to use it you've already unzipped the file. One headache required due to the way Sourceforge hosts files. It would actually be easier to have the URL link to a hosted file, which is the way J.River's plugin download mechanism works.

Revision as of 16:33, 11 January 2007

This page is under construction. It should contain all the info in the original DevZone, but it doesn't yet.

Package Files

Here's an example from scthom that shows how to package a plug-in and the MJP file in a single zip. It is required by the way SourceForge hosts files, though having the MJP outside the zip file and a real link for the URL is easier.

[Package]
Name=WavPack Plugin
Action=NONE
Version=2.1.0
URL=in_wavpack.dll
[Action]
File1=in_wavpack.dll
File1Action1=COPY_PLUGINDIR
File1Action2=REG_PLUGIN

Use Action=NONE when the mjp is inside the zip.