Code::Blocks Forums
User forums => Help => Topic started by: Alaric on February 08, 2007, 10:55:55 pm
-
Where do I get plugins like the devpak installer for Codeblocks?
-
It's already there... See Plugins->Dev-Pak installer/updater. If it's not there try to enable it in Manage Plugins.
-
umm... no... it's not... I don't even have it in my manage plugins. I'm using version "svn build rev 3586 (2007-02-07 13:53:13) gcc 4.0.3 Linux/unicode" if it helps
-
The contributed plugins are in src/plugins/contrib.
-
... and where would that be? Already on my harddrive? Inside of a CVS server? On the main website? I've seen that path before, but WHERE is it?
-
Are you building the sources? Did you run an svn checkout? If so, the plugins will be in codeblocks/trunk/src/plugins/contrib
-
I got it from the nightly build forums. What's this SVN I keep hearing about?
-
I got it from the nightly build forums.
If it truly doesn't show up even in the Manage Plugins dialog, try wiping your Code::Blocks installation folder and installing a new nightly. (You will not lose any customized settings.)
-
umm... still nothing. I got the Feb 06
svn build rev 3577 (2007-02-06 16:23:55) gcc 4.0.3 Linux/unicode build. The Feburary 8 link was down.
-
I got the Feb 06 svn build rev 3577 (2007-02-06 16:23:55) gcc 4.0.3 Linux/unicode build.
I don't use C::B under Linux, so I can't help you here. I'm not sure whether the DevPak plugin is even available for non-Windows systems.
-
O.k. then where do I get new wizards, in specific, one for Gtk?
-
Did you use ./configure --enable-contrib command to configure? Plugins should also get compiled after that, AFAIK.
Regards,
Biplab :)
-
I didn't use ./configure, I used apt. Can I still recomiple with these plugins?
-
Have u compiled C::B from source or have downloaded using apt? If you are compiling C::B from source then use ./configure --enable-contrib and this should solve the problem.
Regarding recompiling plugins only, you can do them by regenerating the make files using configure and then compiling again.
-
As I said before, I got Code::Blocks with syaptic/apt.
-
You can't compile plugins alone as they require C::B lib to link. You have to download C::B source through SVN and then compile it with that option. :)
-
O.k. then, now what the heck is an SVN?
-
the version control system wee use for the CB sources.
See codeblocks home page -> Sources
or go to the wiki and search on nightly cookbook -> will have some explanation
-
The homepage of svn is http://subversion.tigris.org/ (http://subversion.tigris.org/). It's a version control system. If you want a gui, open synaptic and select rapidsvn (http://rapidsvn.tigris.org/). The svn urls for codeblocks are listed at http://developer.berlios.de/svn/?group_id=5358 (http://developer.berlios.de/svn/?group_id=5358).
-
The devpak plugin is NOT compiled in linux.
-
SVN stands for Subversion.
It is a tool that helps developers work on the same set of source codes without having to download the package when one single difference was made... really safes a heck of a lot of bandwidth... believe me...
It is also very useful if you make a small change and you want to contribute that change... that small change is what is usually referred to as a patch... Very nifty...
When you want the source of a project, you need to identify the URL and do a "checkout", this will then download all the files that are within that "repository". After you downloaded that initial checkout... you only have to update your repository with the URL provided (You don't need to remember the URL, SVN does that for you... cool hey!), SVN will "see" what changes was made to the server and update you, it will also "see" any changes you made so that if you screwed up somewhere, you can "revert" to the original on the server... even cooler! (I screwup allot you see! :) )
I recommend Tortoise SVN... integrates with Explorer of Windows (Don't know about Linux though, normal command SVN might be sufficient)
A small brief intro to SVN... I hope...