Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Support for Interpreted Languages?
dmoore:
Thanks for the feedback Morten and keenblade. I guess it is good to hear people have found the plugin useful. So with that in mind, I'll fix the windows pathnames bug and post the latest version of interpreted langs shortly. Has anyone tried it on Linux (I'm lucky if i boot my linux installation more than about an hour a month so i haven't had a chance). I'm embarassed that people have been using such a buggy version (especially when you see how stupid the menu bug makes me look :lol:). I can't promise there won't be bugs left, but it should at least be usable. (Morten: I'm not sure whether i fixed the down button crash)
I want to spend most of my time working with the python plugin. My original vision was (and still is) to work on a generic runner/debugger/project manager plugin for any interpreted language, but I decided I needed a case study to determine the flexibility a generic plugin would require and Python is my language of the moment. So I'll come back to interpreted langs from time to time. One obvious thing I can add is the option to run the interpreter in a codeblocks dockable window.
dmoore:
Ok, my CVS server is down (harddrive), but I'm pretty sure this version is close to the latest (my one fear is that this isn't a complete fix of the dreaded menu bug - at least it didn't show up in my testing). I did a quick patch of the path name bug by simply subtituting the windows short name for the interpreter executable and the source file path. The down move crash in the environment settings didn't show up, so I'm pretty sure I fixed it, but possibly not. The code is also very messy and needs a clean up.
If anyone wants to see specific features added let me know. I'm thinking about adding user specified flags to actions for things like input/output redirection and specifying unix style vs windows style path names (the latter is important for pdb, the python debugger, for some reason it expects unix style "/" for pathname separators even on windows). debugger support within CB is a little trickier. I have it working for pdb in my python plugin (albeit with a patch to the C::B sdk), but making that sufficiently generic to handle any debugger that has redirectible output without requiring custom c/c++ code will take some work.
Two other things:
1. Thomas's alternative to wxExecute would probably come in handy here
2. Someone (probably me) should write the tutorial wiki entry for this plugin
[attachment deleted by admin]
keenblade:
--- Quote from: dmoore on November 18, 2006, 11:18:52 pm ---... One obvious thing I can add is the option to run the interpreter in a codeblocks dockable window.
--- End quote ---
That's what I exactly need. Hope you have time to do.
keenblade:
I can't build the new version. It gives this error referring to #include <sdk.h>:
InterpretedLangs.h:21: calling fdopen: No such file or directory
It seems Code::Blocks has troubles with the paths. At the project build options -> Directories -> Compiler this line exists;
$(#cb)\sdk
When I select it and press edit -> browse, It finds the sdk directory successfuly. Global variables are also set. I can build Code::Blocks itself successfuly.
Any idea?
I use;
Code::Blocks svn build 3236
Pecan:
--- Quote from: keenblade on November 19, 2006, 01:35:47 am --- I can't build the new version. It gives this error referring to #include <sdk.h>:
InterpretedLangs.h:21: calling fdopen: No such file or directory
It seems Code::Blocks has troubles with the paths. At the project build options -> Directories -> Compiler this line exists;
$(#cb)\sdk
When I select it and press edit -> browse, It finds the sdk directory successfuly. Global variables are also set. I can build Code::Blocks itself successfuly.
Any idea?
I use;
Code::Blocks svn build 3236
--- End quote ---
Caused by an incorrect arrangement of #includes and pre-compiled header.
Or an -include sdk.h flag in the project while using pre-compiled headers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version