Linking the plugin to a Nightly Build - Revision history

Techtonik: + some screens

2008-09-12T11:46:51Z

+ some screens

← Older revision		Revision as of 11:46, 12 September 2008
Line 1:		Line 1:
	[[Category:Plugin development]]		[[Category:Plugin development]]
	~~'''Work in Progress!!!'''<br /><br />~~
	This article describes how to assemble your plugin to work with officially released Code::Blocks distribution (either nightly or not) on Windows. It's accomplished by linking your plugin against the DLL's shipped with Code::Blocks.		This article describes how to assemble your plugin to work with officially released Code::Blocks distribution (either nightly or not) on Windows. It's accomplished by linking your plugin against the DLL's shipped with Code::Blocks.

Line 22:		Line 21:

	====Step Four - Link Everything Together ====		====Step Four - Link Everything Together ====

	After having your plugin compiled (or up and running if you prefer) you will need to edit the project build options and add the directory where your official release or nightly is residing to the linker. Project -> Build Options... -> Search directories -> Linker		After having your plugin compiled (or up and running if you prefer) you will need to edit the project build options and add the directory where your official release or nightly is residing to the linker. Project -> Build Options... -> Search directories -> Linker

	Then add the needed libraries to the linker to ~~compile~~ the plugin. These are wxmsw28u_gcc_cb.dll and codeblocks.dll. You don't need to write the .dll extension or the lib ~~word~~ (if present) so they will look like this on the linker options:		[[Image:05_search_directories.png\|none]]

			Then add names of the needed libraries to the linker to assemble the plugin. These are wxmsw28u_gcc_cb.dll and codeblocks.dll. You don't need to write the .dll extension or the lib prefix (if present) so they will look like this on the linker options:

	*codeblocks		*codeblocks
	*wxmsw28u_gcc_cb		*wxmsw28u_gcc_cb


			[[Image:05_linker_settings.png\|none]]
			<br clear="all" />

	====Step Five - Package ====		====Step Five - Package ====
	Wrap your plugin in .cbplugin archive as described in [[Managing Plug-in Resources]] page~~. That's all~~.		Wrap your plugin in .cbplugin archive as described in [[Managing Plug-in Resources]] page.

	=Conclusion=		=Conclusion=
	You should now be able to compile the plugin and load it to the current nightly without the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one.		You should now be able to compile the plugin and load it to the current nightly without the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one.

	~~This was a quick howto so is maybe missing info, I will update it later as add some images.~~ Good Luck!		Good Luck!

Techtonik: /* Procedure */ + expand with comments

2008-09-12T11:13:58Z

Procedure: + expand with comments

← Older revision		Revision as of 11:13, 12 September 2008
Line 8:		Line 8:
	=Procedure=		=Procedure=

	====Step One====		====Step One - Get Binaries ====
	Download and install Code::Blocks ~~release~~ to link your plugin with. You may choose either official release available from https://www.codeblocks.org/downloads/5 or latest nightly from this forum - /index.php/board,20.0.html To build your plugin you will also need Code::Blocks SDK for your version, which is currently merged in CB sources, so checkout them from [https://www.codeblocks.org/downloads/7 SVN] if you haven't done so already.		Download and install version of Code::Blocks you would like to link your plugin with. You may choose either official release available from https://www.codeblocks.org/downloads/5 or latest nightly from this forum - /index.php/board,20.0.html

	====Step Two====		====Step Two - Get Sources ====
	~~Get the~~ wxWidgets ~~sources at http~~:~~//wxwidgets.org and configure the setup.h to be compatible with the actual wxmsw28u_gcc_cb_wxXXX.dll compilation~~.		To ensure your plugin will run smoothly with chosen C::B version you need headers and libraries of this version as well as headers and libraries for wxWidgets library used by this Code::Blocks.

	~~====Step Three====~~		Headers and libraries alone constitute SDK. In CB case headers are distributed with sources, libraries come with CB or can be recompiled from source if needed. Get sources for your required version of Code::Blocks from [https://www.codeblocks.org/downloads/7 SVN] if you haven't done so already.
	~~After having your plugin up~~ and ~~running you will need to edit the compiler options and add the directory where your nightly is residing to the linker~~. ~~Then add the~~ needed ~~libraries to the linker to compile the plugin that usually are wxmsw28u_gcc_cb~~.~~dll and libcodeblocks~~.~~dll~~. ~~You don~~'t ~~need to write the~~ .~~dll extension or the lib word so they will look like this on the linker Options:~~

			wxWidgets libraries need to be [https://wiki.next.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows#Compile_wxWidgets_in_Unicode_mode compiled] (or configured) or else you will most probably get "wx/setup.h: No such file or directory" message. Get version used to build your C::B at http://wxwidgets.org

			====Step Three - Build Plugin ====
			Try to compile the plugin after building wxWidgets. It is ok if you got a message "cannot find -lcodeblocks" from ld.exe It means that codeblocks library for linking plugin is missing, because library paths were not setup correctly. Next step will fix this.

			====Step Four - Link Everything Together ====
			After having your plugin compiled (or up and running if you prefer) you will need to edit the project build options and add the directory where your official release or nightly is residing to the linker. Project -> Build Options... -> Search directories -> Linker

			Then add the needed libraries to the linker to compile the plugin. These are wxmsw28u_gcc_cb.dll and codeblocks.dll. You don't need to write the .dll extension or the lib word (if present) so they will look like this on the linker options:

			*codeblocks
	*wxmsw28u_gcc_cb		*wxmsw28u_gcc_cb
	*codeblocks
			====Step Five - Package ====
			Wrap your plugin in .cbplugin archive as described in [[Managing Plug-in Resources]] page. That's all.

	=Conclusion=		=Conclusion=

Techtonik: /* Step One */ + SDK is merged with CB sources

2008-09-12T08:19:20Z

Step One: + SDK is merged with CB sources

← Older revision		Revision as of 08:19, 12 September 2008
Line 9:		Line 9:

	====Step One====		====Step One====
	Download and install Code::Blocks release to link your plugin with. You may choose either official release available from https://www.codeblocks.org/downloads/5 or latest nightly from this forum - /index.php/board,20.0.html ~~You~~ will also need ~~the~~ Code::Blocks SDK sources ~~to build your plugin~~, so checkout them from [https://www.codeblocks.org/downloads/7 SVN] if you haven't done ~~this~~ already.		Download and install Code::Blocks release to link your plugin with. You may choose either official release available from https://www.codeblocks.org/downloads/5 or latest nightly from this forum - /index.php/board,20.0.html To build your plugin you will also need Code::Blocks SDK for your version, which is currently merged in CB sources, so checkout them from [https://www.codeblocks.org/downloads/7 SVN] if you haven't done so already.

	====Step Two====		====Step Two====

Techtonik: reworded introduction: TODO steps 2 and 3 with screens

2008-09-10T16:20:58Z

reworded introduction: TODO steps 2 and 3 with screens

← Older revision		Revision as of 16:20, 10 September 2008
Line 1:		Line 1:
	[[Category:Plugin development]]		[[Category:Plugin development]]
	'''Work in Progress!!!'''<br /><br />		'''Work in Progress!!!'''<br /><br />
	This article describes how to ~~link~~ your plugin against the ~~dll~~'s shipped with ~~codeblocks on windows~~.		This article describes how to assemble your plugin to work with officially released Code::Blocks distribution (either nightly or not) on Windows. It's accomplished by linking your plugin against the DLL's shipped with Code::Blocks.

	=Introduction=		=Introduction=
	Is useful to know how to compile Code::Blocks sources from scratch to link with our plugin, but when we want to share it with the community then we need to link it against the latest nightly build or final release of ~~codeblocks~~. This is a simple procedure that many people ~~doesn~~'t know at first~~, and that will help you accelerate development in many ways~~. Enjoy :)		Is useful to know how to compile Code::Blocks sources from scratch to link with our plugin, but when we want to share it with the community then we need to link it against the latest nightly build or final release of Code::Blocks. This is a simple procedure that many people don't know at first. Enjoy :)

	=Procedure=		=Procedure=
	~~Here are the instructions divided in steps for the easy navigation of our eyes.~~

	====Step One====		====Step One====
	Download and install ~~the~~ latest nightly ~~found on~~ this forum /index.php/board,20.0.html ~~Also you~~ will need the Code::Blocks SDK so checkout ~~the sources on berlios~~.~~de using svn~~.		Download and install Code::Blocks release to link your plugin with. You may choose either official release available from https://www.codeblocks.org/downloads/5 or latest nightly from this forum - /index.php/board,20.0.html You will also need the Code::Blocks SDK sources to build your plugin, so checkout them from [https://www.codeblocks.org/downloads/7 SVN] if you haven't done this already.

	====Step Two====		====Step Two====

Jgm: /* Conclusion */

2008-01-19T01:26:22Z

Conclusion

← Older revision		Revision as of 01:26, 19 January 2008
Line 22:		Line 22:

	=Conclusion=		=Conclusion=
	You should now be able to compile the plugin and load it to the current nightly without the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one. This was a quick howto so is maybe missing info, I will update it later. Good Luck!		You should now be able to compile the plugin and load it to the current nightly without the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one.

			This was a quick howto so is maybe missing info, I will update it later as add some images. Good Luck!

Jgm at 01:23, 19 January 2008

2008-01-19T01:23:12Z

← Older revision		Revision as of 01:23, 19 January 2008
Line 1:		Line 1:
	[[Category:Plugin development]]		[[Category:Plugin development]]
			'''Work in Progress!!!'''<br /><br />
	This article describes how to link your plugin against the dll's shipped with codeblocks on windows.		This article describes how to link your plugin against the dll's shipped with codeblocks on windows.

Jgm at 01:21, 19 January 2008

2008-01-19T01:21:16Z

← Older revision		Revision as of 01:21, 19 January 2008
Line 1:		Line 1:
			[[Category:Plugin development]]

	This article describes how to link your plugin against the dll's shipped with codeblocks on windows.		This article describes how to link your plugin against the dll's shipped with codeblocks on windows.

Jgm: /* Procedure */

2008-01-19T01:18:31Z

Procedure

← Older revision		Revision as of 01:18, 19 January 2008
Line 7:		Line 7:
	Here are the instructions divided in steps for the easy navigation of our eyes.		Here are the instructions divided in steps for the easy navigation of our eyes.

	==Step One==		====Step One====
	Download and install the latest nightly found on this forum /index.php/board,20.0.html Also you will need the Code::Blocks SDK so checkout the sources on berlios.de using svn.		Download and install the latest nightly found on this forum /index.php/board,20.0.html Also you will need the Code::Blocks SDK so checkout the sources on berlios.de using svn.

	==Step Two==		====Step Two====
	Get the wxWidgets sources at http://wxwidgets.org and configure the setup.h to be compatible with the actual wxmsw28u_gcc_cb_wxXXX.dll compilation.		Get the wxWidgets sources at http://wxwidgets.org and configure the setup.h to be compatible with the actual wxmsw28u_gcc_cb_wxXXX.dll compilation.

	==Step Three==		====Step Three====
	After having your plugin up and running you will need to edit the compiler options and add the directory where your nightly is residing to the linker. Then add the needed libraries to the linker to compile the plugin that usually are wxmsw28u_gcc_cb.dll and libcodeblocks.dll. You don't need to write the .dll extension or the lib word so they will look like this on the linker Options:		After having your plugin up and running you will need to edit the compiler options and add the directory where your nightly is residing to the linker. Then add the needed libraries to the linker to compile the plugin that usually are wxmsw28u_gcc_cb.dll and libcodeblocks.dll. You don't need to write the .dll extension or the lib word so they will look like this on the linker Options:

Jgm: /* Conclusion */

2008-01-19T01:17:31Z

Conclusion

← Older revision		Revision as of 01:17, 19 January 2008
Line 20:		Line 20:

	=Conclusion=		=Conclusion=
	You should now be able to compile the plugin and load it to the current nightly ~~with out~~ the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one. This was a quick howto so is maybe missing info, I will update it later. Good Luck!		You should now be able to compile the plugin and load it to the current nightly without the symbols error. A problem that many developers confront after compiling the plugin with a compilation that differs from the official one. This was a quick howto so is maybe missing info, I will update it later. Good Luck!

Jgm: /* Introduction */

2008-01-19T01:15:33Z

Introduction

← Older revision		Revision as of 01:15, 19 January 2008
Line 2:		Line 2:

	=Introduction=		=Introduction=
	Is useful to know how to compile Code::Blocks sources from scratch to link with our plugin, but when we want to share it with the community then we need to link it against the latest nightly build or final release of codeblocks. This is a simple procedure that many people doesn't know at first, and that will help you accelerate ~~your~~ development in many ways. Enjoy :)		Is useful to know how to compile Code::Blocks sources from scratch to link with our plugin, but when we want to share it with the community then we need to link it against the latest nightly build or final release of codeblocks. This is a simple procedure that many people doesn't know at first, and that will help you accelerate development in many ways. Enjoy :)

	=Procedure=		=Procedure=