OggPlay/Win32 - Revision history

Martin.leese: Undo revision 14702 by NicoleLPowell (talk) SPAM link

2014-05-23T13:46:36Z

Undo revision 14702 by NicoleLPowell (talk) SPAM link

← Older revision		Revision as of 13:46, 23 May 2014
Line 59:		Line 59:

	To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].		To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].
	(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left ~~[http://bestwirelessmouse.biz/ wireless~~ mouse] click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources. Please note, that the checkout can take a while over slow links because the plugin requires a number of libraries such as:		(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left mouse click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources. Please note, that the checkout can take a while over slow links because the plugin requires a number of libraries such as:
	* libogg		* libogg

NicoleLPowell: /* Developing OggPlay plugin */

2014-05-23T06:55:20Z

Developing OggPlay plugin

← Older revision		Revision as of 06:55, 23 May 2014
Line 59:		Line 59:

	To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].		To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].
	(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left mouse click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources. Please note, that the checkout can take a while over slow links because the plugin requires a number of libraries such as:		(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left [http://bestwirelessmouse.biz/ wireless mouse] click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources. Please note, that the checkout can take a while over slow links because the plugin requires a number of libraries such as:
	* libogg		* libogg

Laser13: /* Binaries of the OggPlay Mozilla plugin */

2008-01-25T06:52:50Z

Binaries of the OggPlay Mozilla plugin

← Older revision		Revision as of 06:52, 25 January 2008
Line 98:		Line 98:
	== Binaries of the OggPlay Mozilla plugin ==		== Binaries of the OggPlay Mozilla plugin ==

	For people not interested in developing the plugin but willing test it on their own machine are very much encouraged to download the ~~following binaries of~~ the plugin:		For people not interested in developing the plugin but willing test it on their own machine are very much encouraged to download the the plugin from:

	[http://~~wiki~~.~~xiph~~.~~org~~/index.~~php npliboggplugin.dll~~]<br>		[http://www.annodex.net/software/plugin/index.html Plugin Installator]<br>
	~~[http://wiki.xiph.org/index.php npliboggplugin.xpt]~~

	~~Both file should be placed in~~ the ~~Mozilla~~ plugin ~~directory. You will need to restart~~ Mozilla ~~after copying the plugin files to ''plugin''~~ directory. This is usually ''C:\Program Files\Mozilla Firefox\plugins'' unless your Mozilla Firefox has been installed in different than default location. To test the plugin go to [http://media.annodex.net/cmmlwiki/Special:ListAllItems cmmlwiki]. If you see the video playing then you successfully installed the plugin. Enjoy!		The installer places the plugin binaries in default system Mozilla directory. This is usually ''C:\Program Files\Mozilla Firefox\plugins'' unless your Mozilla Firefox has been installed in different than default location. To test the plugin go to [http://media.annodex.net/cmmlwiki/Special:ListAllItems cmmlwiki]. If you see the video playing then you successfully installed the plugin. Enjoy!

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:41:22Z

Developing OggPlay plugin

← Older revision		Revision as of 15:41, 17 June 2007
Line 83:		Line 83:

	* .\gecko-sdk		* .\gecko-sdk
	** .\gecko-sdk		** .\gecko-sdk\bin\ ('''xpidl.exe''')
	*** .\gecko-sdk\bin\ ('''xpidl.exe''')
	* .\plugin_sources		* .\plugin_sources
	** .\plugin_sources\lib		** .\plugin_sources\lib
Line 91:		Line 90:
	*** .\plugin_sources\sln\plugin_all_200x ('''plugin_all.sln''')		*** .\plugin_sources\sln\plugin_all_200x ('''plugin_all.sln''')

	[of course the names of the Gecko SDK (''.\gecko-sdk'' above) and directory storing plugin source files (''.\plugin_sources'') can be completely arbitral]		[of course the names of the Gecko SDK (''.\gecko-sdk'') above and directory storing plugin source files (''.\plugin_sources'') can be completely arbitral]

	If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.		If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:38:58Z

Developing OggPlay plugin

← Older revision		Revision as of 15:38, 17 June 2007
Line 95:		Line 95:
	If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.		If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.

	By default a post build step is copying the plugin files (npliboggplugin.dll and npliboggplugin.xpt) to ''C:\Program Files\Mozilla Firefox\plugins'' (default Mozilla Firefox location). If you have Mozilla Firefox installed in a different location you need to change the path in '''liboggplay''' ''Post-Built Event'' configuration (left mouse click on '''liboggplugin''' project then ''Properties'' then expand '''Build Events''' and navigate to '''Post-Built Event''').		By default a post build step is copying the plugin files ('''npliboggplugin.dll''' and '''npliboggplugin.xpt''') to ''C:\Program Files\Mozilla Firefox\plugins'' (default Mozilla Firefox location). If you have Mozilla Firefox installed in a different location you need to change the path in '''liboggplay''' ''Post-Built Event'' configuration (left mouse click on '''liboggplugin''' project then ''Properties'' then expand '''Build Events''' and navigate to '''Post-Built Event''').

	== Binaries of the OggPlay Mozilla plugin ==		== Binaries of the OggPlay Mozilla plugin ==

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:38:15Z

Developing OggPlay plugin

← Older revision		Revision as of 15:38, 17 June 2007
Line 89:		Line 89:
	** .\plugin_sources\project_files		** .\plugin_sources\project_files
	** .\plugin_sources\sln		** .\plugin_sources\sln
	** .\plugin_sources\sln\plugin_all_200x ('''plugin_all.sln''')		*** .\plugin_sources\sln\plugin_all_200x ('''plugin_all.sln''')

			[of course the names of the Gecko SDK (''.\gecko-sdk'' above) and directory storing plugin source files (''.\plugin_sources'') can be completely arbitral]

	If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.		If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.

	By default a post build step is copying the plugin files to ''C:\Program Files\Mozilla Firefox\plugins'' (default Mozilla Firefox location). If you have Mozilla Firefox installed in a different location you need to change the path in '''liboggplay''' ''Post-Built Event'' configuration (left mouse click on '''liboggplugin''' project then ''Properties'' then expand '''Build Events''' and navigate to '''Post-Built Event''').		By default a post build step is copying the plugin files (npliboggplugin.dll and npliboggplugin.xpt) to ''C:\Program Files\Mozilla Firefox\plugins'' (default Mozilla Firefox location). If you have Mozilla Firefox installed in a different location you need to change the path in '''liboggplay''' ''Post-Built Event'' configuration (left mouse click on '''liboggplugin''' project then ''Properties'' then expand '''Build Events''' and navigate to '''Post-Built Event''').

	== Binaries of the OggPlay Mozilla plugin ==		== Binaries of the OggPlay Mozilla plugin ==

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:35:31Z

Developing OggPlay plugin

← Older revision		Revision as of 15:35, 17 June 2007
Line 88:		Line 88:
	** .\plugin_sources\lib		** .\plugin_sources\lib
	** .\plugin_sources\project_files		** .\plugin_sources\project_files
	** .\plugin_sources\sln ('''plugin_all.sln''')		** .\plugin_sources\sln
			** .\plugin_sources\sln\plugin_all_200x ('''plugin_all.sln''')

	If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on nsILibOggPlugin.idl file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory.		If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on ''nsILibOggPlugin.idl'' file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory. You can test the setup by compiling just the ''nsILibOggPlugin.idl'' file. If the build is sucessfull you can start compiling the plugin. In particular, compiling the default '''liboggplay''' project should build all the project in the VS solution and build the plugin in the end. The plugin binaries as well as binaries of other libraries on which plugin depends can be found under ''.\plugin_sources\sln\plugin_all_200x\debug'' if your default build configuration was '''Debug'''. When the plugin is released the '''Release''' build will be compiled to .\plugin_sources\sln\plugin_all_200x\release.

			By default a post build step is copying the plugin files to ''C:\Program Files\Mozilla Firefox\plugins'' (default Mozilla Firefox location). If you have Mozilla Firefox installed in a different location you need to change the path in '''liboggplay''' ''Post-Built Event'' configuration (left mouse click on '''liboggplugin''' project then ''Properties'' then expand '''Build Events''' and navigate to '''Post-Built Event''').

	== Binaries of the OggPlay Mozilla plugin ==		== Binaries of the OggPlay Mozilla plugin ==

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:26:36Z

Developing OggPlay plugin

← Older revision		Revision as of 15:26, 17 June 2007
Line 59:		Line 59:

	To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].		To compile and start hacking on Win32 version of OggPlay plugin you need to check out [http://trac.annodex.net/browser/OggplayPluginWin32SDK/trunk OggplayPluginWin32SDK] from [http://svn.annodex.net svn.annodex.net].
	(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left mouse click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources ~~('''Note:''' The~~ checkout can take a while over slow links because the plugin requires a number of libraries such as:		(you need to point your svn client to : http://svn.annodex.net/OggplayPluginWin32SDK/trunk). If you are using Tortoise SVN create a new directory in your favourite development location on your hard drive. Then navigate to the location where the new directory has been created. Use left mouse click on the directory where you want to check out the plugin code and development configuration and select '''SVN Checkout''' option in the context menu. In the repository URL provide http://svn.annodex.net/OggplayPluginWin32SDK/trunk and checkout the head revision of the plugin sources. Please note, that the checkout can take a while over slow links because the plugin requires a number of libraries such as:
	* libogg		* libogg

Line 78:		Line 78:
	* liboggplay.		* liboggplay.

	When your checkout is completed navigate to ''sln/plugin_all_200x''' (e.g. plugin_all_2005 for Visual Studio 2005). You should be able to open the ''plugin.sln'' file.		When your checkout is completed navigate to ''sln/plugin_all_200x''' (e.g. plugin_all_2005 for Visual Studio 2005). You should be able to open the ''plugin_all.sln'' file.

			The development configutation by default assumes that you installed gecko-sdk (with working version of '''xpidl''' compiler) in a directory parallel to the directory where you checked out the plugin sources. In paritcular, the directory structure by default should be as follows:

			* .\gecko-sdk
			** .\gecko-sdk
			*** .\gecko-sdk\bin\ ('''xpidl.exe''')
			* .\plugin_sources
			** .\plugin_sources\lib
			** .\plugin_sources\project_files
			** .\plugin_sources\sln ('''plugin_all.sln''')

			If you have '''Gecko SDK''' in different location in relation to ''plugin_all.sln'' file you will need to go the ''Properties'' of liboggplugin project in Visual Studio and find ''nsILibOggPlugin.idl'' file in the sources of that project. Next you need to change the directory of the custom compilation step (i.e. left-click on nsILibOggPlugin.idl file, choose ''Properties'' expand ''Custom Build Step'' and in ''Command Line'' option change the relative path to the location of '''xpidl''' compiler as well as to Gecko SDK ''.\idl'' directory.

	== Binaries of the OggPlay Mozilla plugin ==		== Binaries of the OggPlay Mozilla plugin ==

Laser13: /* Developing OggPlay plugin */

2007-06-17T15:15:38Z

Developing OggPlay plugin

@@ Line 55: / Line 55: @@
 Once you have a working Mozilla plugin development environment you can start configuring the environment for OggPlay plugin.
-First of all, you need to install SVN client on your development machine. There are many options there but this document assumes that you a client with the capabilities of Tortoise SVN.
+First of all, you need to install SVN client on your development machine. There are many Win32 SVN clients available but this document assumes that you have a client with the capabilities of Tortoise SVN.
 == Binaries of the OggPlay Mozilla plugin ==

Laser13: /* Binaries of the OggPlay Mozilla plugin */

2007-06-16T03:09:48Z

Binaries of the OggPlay Mozilla plugin

← Older revision		Revision as of 03:09, 16 June 2007
Line 64:		Line 64:
	[http://wiki.xiph.org/index.php npliboggplugin.xpt]		[http://wiki.xiph.org/index.php npliboggplugin.xpt]

	Both file should be ~~place~~ in the Mozilla plugin directory. This is usually ''C:\Program Files\Mozilla Firefox\plugins'' unless your Mozilla Firefox has been installed in different than default location. To test the plugin go to [http://media.annodex.net/cmmlwiki/Special:ListAllItems cmmlwiki]		Both file should be placed in the Mozilla plugin directory. You will need to restart Mozilla after copying the plugin files to ''plugin'' directory. This is usually ''C:\Program Files\Mozilla Firefox\plugins'' unless your Mozilla Firefox has been installed in different than default location. To test the plugin go to [http://media.annodex.net/cmmlwiki/Special:ListAllItems cmmlwiki]. If you see the video playing then you successfully installed the plugin. Enjoy!