User forums > Using Code::Blocks
File Explorer and Shell Extension Plugin
acinfo64:
Dear All,
Can you give me more details on how you solved your problem? I have downloaded the ShellExtensions-0.2.0.cbplugin but it fails to install.
I have compiled c::b, although it is not what I prefer (now I need a wxmsw28u_gcc_yyyy.dll with yyyy a 'dummy' project name of me), but I cannot find the source of the ShellExtensions plugin. What has this extension to do with the 'IL Plugins' (I don't know what IL PLugins are)?
Did you compile the newest version of c::b (v8.02) or an much older version?
lexis:
As for me, I compiled a CB nightly build with all plugins including subject one.
As I understand it's not needed to build overall CB, only plugin using appropriate version of plugins API.
Then you can add every svn command as separate menu item one by one to the File Extension plugin.
dmoore:
--- Quote from: acinfo64 on April 16, 2008, 10:12:56 am ---I have downloaded the ShellExtensions-0.2.0.cbplugin but it fails to install.
--- End quote ---
sorry, that one is out of date (the C::B plugin API changed since I made that plugin binary). I'm downloading the source for the 8.02 API now and will recompile the plugin and post it in the next 24 hours. If you can't wait, you should be able to compile from source without difficulty by checking out the trunk from the cbilplugin subversion repository (follow the link in my sig).
As for why the project has the name it does: IL = Interpreted Languages. The purpose of the project is to host plugins that are useful to people who want to use C::B with Interpreted Languages. The Shell Extensions plugin falls into that category (even though it is useful even for people who don't use ILs)
dmoore:
binary here (ShellExtensions v0.2.1):
http://developer.berlios.de/project/showfiles.php?group_id=7745&release_id=14501
acinfo64:
Thank you for your help. The binary (v0.2.1) works perfectly. I also found the code and I was able to compile everything.
The plugin works and so I assume that the IL part is automatically distributed with the compiled C::B v8.02.
Now I have to figure out how the SVN pluging works exactly. As I understood is that every SVN command has to be added in the file extension plugin and now I'm going to figure out how this has to be done.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version