Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Compiling codeblocks original source code to develop my own customized codeblock
BlueHazzard:
--- Code: ---[debug]> cont
[debug]Continuing.
[debug]Starting Code::Blocks svn build rev 0 Feb 7 2017, 17:16:55 - wx2.8.12 (Windows, unicode) - 32 bit
[debug][Inferior 1 (process 4488) exited with code 037777777777]
[debug]>>>>>>cb_gdb:
--- End code ---
Your application still crashes and at the moment i have no idea how i can help you with this...
[EDIT:] Can you post the code of your plugin?
anandamu16:
--- Quote ---Now if you run my script and build the "to_codeblock" target
--- End quote ---
You want me to run your script through CODEBLOCKS_INSTALLATION or CODEBLOCKS_DEVEL?
FYI: I am developing everything through CODEBLOCKS_DEVEL and checking on CODEBLOCKS_DEVEL only.
Note: I used CODEBLOCKS_INSTALLATION to create CODEBLOCKS_DEVEL and from then I am using only CODEBLOCKS_DEVEL. Let me know, if i am doing something wrong.?
I will make a plugin project separately through CODEBLOCKS_DEVEL based on "your" wizard. I will add the project here itself.
Bdw I don't think, It is something related to plugin code.
anandamu16:
ok, let me update it.
I will use the same terminology like below.
--- Quote ---1) CODEBLOCKS_INSTALLATION <-- Something like C:\Program Files\Codeblocks - This is your installation of codeblocks. If you use Codeblocks in your daily work this executable should be used
2) CODEBLOCKS_DEVEL <-- Something like C:\User\MYUSER\Documents\Programming\Codeblocks\src\codeblocks_sf\src\devel - This is the output directory if you build codeblocks. This gets overwritten every time you build codeblocks
3) CODEBLOCKS_OUTPUT <-- This folder gets created/updated if you run the update.bat script from the src folder. You can copy the content from this folder over CODEBLOCKS_INSTALLATION to update your installation
--- End quote ---
Firstly: I create a plugin through CODEBLOCKS_DEVEL and try to execute it. It gave me the execution error.
Next: I create a plugin through CODEBLOCKS_INSTALLATION (with updated wizard.script for plugin that you shared)and try to execute it. It works fine i.e; after execution it opens the CODEBLOCKS_DEVEL IDE window to check the plugin.
Next: I create a plugin through CODEBLOCKS_INSTALLATION (with default wizard.script for plugin that comes by default)and try to execute it, it gave me the same error that I was receiving from beginnin.
So, I doubt my plugin is executing fine because of the changes you have made in wizard.script file. Can you help me to understand the changes?
So my question is:
- Why it didn't work in the First case?
- So for now, I should remember that.... I need to develop everything through CODEBLOCKS_INSTALLATION, check it on CODEBLOCKS_DEVEL and for distribution, I should use CODEBLOCKS_OUTPUT?
- I tried to build wxwidget application through CODEBLOCKS_DEVEL and try to execute it using CODEBLOCKS_DEVEL only and that works fine, why was it so. I mean likewise plugin, wxwidget application should also fail to execute but that worked fine?
BlueHazzard:
You copy the script to CODEBLOCKS_INSTALLATION or CODEBLOCKS_OUTPUT. Then you run the appropriate codeblocks.exe. With this instance you create and develop your plugin. If you run the plugin it will run trough CODEBLOCKS_DEVEL with a separate profile so you won't kill your working environment if something goes wrong.
Generally you should not run CODEBLOCKS_DEVEL while you are developing on codeblocks/plugins but always CODEBLOCKS_INSTALLATION or minimal CODEBLOCKS_OUTPUT.
Things are like this
not stable < a bit stable < stable
CODEBLOCKS_DEVEL < CODEBLOCKS_OUTPUT < CODEBLOCKS_INSTALLATION
Also CODEBLOCKS_DEVEL will get overwritten every time you build codeblocks.
BlueHazzard:
What i changed in the script:
1) Add the target to_codeblocks
1.1) Set the output directory to CODEBLOCKS_DEVEL
1.2) Copy all needed resources to CODEBLOCKS_DEVEL
1.3) Add the call parameters so CODEBLOCKS_DEVEL will get called with a grade of isolation
Now this makes it possible to debug the plugin. It should not influence your plugin, but only how you debug it. So if you say it "executes" right do you mean "debugging" or also executing?
One possibility would be that you are missing some DLL and if you call it with CODEBLOCKS_DEVEL all dlls are in place, but it is hard to tell...
Q: Why are this steps needed for debugging the plugin?
GDB needs a executable to debug dlls (a plugin is a dll) and in our case this is CODEBLOCKS_DEVEL. My script copies all to CODEBLOCKS_DEVEL and runs CODEBLOCKS_DEVEL trought the debugger. CODEBLOCKS_DEVEL will then load your plugin and you can debug it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version