Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
cbMakefileGen plugin
kisoft:
--- Quote from: Grom on October 24, 2007, 05:57:46 pm ---I can try... I have 64 bit OpenSUSE 10.3, that have been dead and I have to reinstall it :evil:. Just say me how I can help you.
--- End quote ---
I have no experience to create a linux distributives. Somebody can help me. I have Ubuntu 6.10 only.
--- Quote from: Grom on October 24, 2007, 05:57:46 pm ---Would be grate also to write a plugin that will download updates, compile them and install.
--- End quote ---
I can't help you. Time is money.
Good luck!
kisoft:
I does released ver 0.3.11.10
Features:
- Bugfix, added check to existance a compiler settings
- Added cbmakegenempty.po file for translate to other langs
To gd_on:
Bug concerned with compiler settings. Now I does add check to existance a compiler settings.
Also I does add output to "Code::Blocks Debug" window before call Compiler::GenerateCommandLine. It can help to debug a generating process.
I try my plugin on 3 your projects and found then 1 & 2 projects (c/c++) worked ok, and 3 project (fortran) send me message about absent a compiler settings (it's ok, I don't have this compiler).
You can try, trap must be is absent now. But a makefile generation is impossible before setting a compiler settings for your project.
General mine is: For generate makefile you must compile your project for beginning at once.
Good luck!
gd_on:
Thanks a lot.
Works now with my C and C++ projects.
Works also with my Fortran projects, but, as you said, if I understand well, it's necessary to first generate the project then Generate the Makefile.
If you don't first generate, there are still crashes.
Let me explain :
I open the fortran project and directly click on Generate Makefile. (That's bad, I know :( )
I obtain a message window "Unhandled exception" and three buttons at the bottom of that window. Until now it's OK.
1) If I click on the right one "Ignore", an empty Makefile is generated, but C::B continues to work.
2) If I click on the middle one "Retry", C::B crashes.
3) If I click on the left one "Quit" (? Abandonner in French), I first obtain an error message, telling me that there is an exception, in compiler.cpp at line 255, that Compiler::Init() is not called or generator is invalid, and that my C::B version is 4554. Until now, it's OK. But if I click on the OK button, C::B crashes.
It should be better if in the last 2 cases, I had a message telling me to first generate my project, at least one time, rather than a C::B crash. A crash is always frustrating, even when the user has made something wrong ! Further on, the codeblocks.rpt file has no new messages. C:BB exits without telling why.
But, nevertheless, it's OK. May be a few enhancements for the next release.
And thanks too for publishing a .po file.
I'll have a look and will send you a french translation, probably this week end.
gd_on
kisoft:
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---Thanks a lot.
Works now with my C and C++ projects.
--- End quote ---
Ok.
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---Works also with my Fortran projects, but, as you said, if I understand well, it's necessary to first generate the project then Generate the Makefile.
--- End quote ---
For generate a simple makefile you MUST at ONCE only:
1. Create project.
2. Add files and setup project.
3. Build project with successfull result. (On build C::B create project.depend file)
For next time you can close project, open it again. You can edit sources and compile again. Many times.
Now you can generate a simple makefile.
For example, you does execute 3 steps described above. Close project. Open it again and do start "Generate Makefile".
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---If you don't first generate, there are still crashes.
Let me explain :
I open the fortran project and directly click on Generate Makefile. (That's bad, I know :( )
--- End quote ---
If you does execute 3 steps, described above, this action is true.
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---I obtain a message window "Unhandled exception" and three buttons at the bottom of that window. Until now it's OK.
--- End quote ---
My plugin don't handled exceptions. External instance send this message.
Motive unknown for me now. I will see to sources again, more carefully.
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---I first obtain an error message, telling me that there is an exception, in compiler.cpp at line 255, that Compiler::Init() is not called or
generator is invalid, and that my C::B version is 4554. Until now, it's OK. But if I click on the OK button, C::B crashes.
--- End quote ---
My C::B:
svn 4556 (wxWidgets 2.8.4)
I compile it self, on my computer.
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---It should be better if in the last 2 cases, I had a message telling me to first generate my project, at least one time, rather than a C::B crash. A crash is always frustrating, even when the user has made something wrong ! Further on, the codeblocks.rpt file has no new messages. C:BB exits without telling why.
But, nevertheless, it's OK. May be a few enhancements for the next release.
--- End quote ---
No message windows! :) I like programs without errors.
--- Quote from: gd_on on October 26, 2007, 12:07:10 pm ---And thanks too for publishing a .po file.
I'll have a look and will send you a french translation, probably this week end.
--- End quote ---
Ok. I will add your file to my repository and release.
Send me .po and .mo files, I will append new messages to your .po file in next releases.
Thanks a lot for bugreports and your projects for testing.
gd_on:
I think I have found a key for the problem.
I have 3 different fortran compilers on my PC : g77, g95 and gfortran.
After loading a fortran project, I open Project/Build Options.
Here I can see at the higher lever the "Selected compiler" and at a lower level, in my case "Release" (but it can be Debug also), I can also see the "Selected compiler". If both are the same, there are no problems. I can Generate Makefile now.
But if they are not the same, for example g95 at the higher level and g77 at the release level, I'll have problems if I Generate Makefile now (though generation of project and Makefile was OK the previous time, before closing C::B). I must first regenerate the project in that case. It's not necessary if both compiler declarations are the same.
You'll find effectively in my Fortran project (Motor2.cbp) I sent you a few days ago, that both "<Option compiler=" lines are not the same. First one contains gnu_g95_compiler, and the second one contains gnu_g77_compiler. Normally it is this second one I wanted to use here. The first one should be probably ignored !
gd_on
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version