Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Enhancements to the CB Build System
MortenMacFly:
--- Quote from: scarphin on November 16, 2015, 12:41:27 am ---I don't know when the next version will be released but if it's not too soon, I can break the patch into smaller ones corresponding to the features (and bug fixes) I presented here:
--- End quote ---
Please do so. And also mention shortly i the description what are the bugs you think that should be fixed (so no new features).
--- Quote from: scarphin on November 16, 2015, 12:41:27 am ---Thanks for pointing that out. I'll look into it and try to come up with a fix.
--- End quote ---
Great! :-)
--- Quote from: scarphin on November 16, 2015, 12:41:27 am ---Please discard them.
--- End quote ---
I think you can do this yourself. There might be more patches obsolete now. If you can't, just post a list of links to the patches that are obsolete here and I'll do.
scarphin:
Sorry for the delay. As a start I tried to close the invalid tickets but sourceforge won't let me do that. I think a developer must do that. Please close the tickets listed below as they don't handle the features/bugs well enough. I'll post more appropriate ones when I split the big patch into smaller pieces. The one you applied is fine.
https://sourceforge.net/p/codeblocks/tickets/140/
https://sourceforge.net/p/codeblocks/tickets/141/
https://sourceforge.net/p/codeblocks/tickets/146/
I decided to go with the route of implementing a safer design for the problem I mentioned here:
--- Quote ---There is one thing that's troubling me though. In the first implementation (the one lacking the target macros), a compiler id was assigned to every file to make sure that the correct files were generated in case the file's designated compiler was changed by the user. I had to replace these compiler ids with target ids to allow for target macros to be used (which is definitely a necessity). Now that introduces a small problem. When the user changes the compiler of a target, checking which files the newly assigned compiler creates is unnecessarily complex and not included in the latest implementation. This may result in incorrect behavior. There are 2 solutions to correct this that I can think of. First, a simple dialog to warn the user to reload his/her project to take the new changes into effect. Second, a more complex design to assign both the compiler and target ids to each file to automatically decide which files to generate. Which one do you think will be a better approach?
--- End quote ---
I'll try to implement both the compiler id and target id checks to handle different scenarios safely (at least not result in abnormal behavior). I want it to be a solid implementation so that might take longer than what I expected.
I'm in the process of moving to another country currently so my previous estimated time of submitting patches might not (probably won't) hold up. It might take a couple of weeks before I can settle things down but I assure you this won't be forgotten.
MortenMacFly:
--- Quote from: scarphin on November 19, 2015, 07:06:35 pm ---Sorry for the delay. As a start I tried to close the invalid tickets but sourceforge won't let me do that. I think a developer must do that. Please close the tickets listed below as they don't handle the features/bugs well enough. I'll post more appropriate ones when I split the big patch into smaller pieces. The one you applied is fine.
https://sourceforge.net/p/codeblocks/tickets/140/
https://sourceforge.net/p/codeblocks/tickets/141/
https://sourceforge.net/p/codeblocks/tickets/146/
--- End quote ---
Done that.
--- Quote from: scarphin on November 19, 2015, 07:06:35 pm ---I'm in the process of moving to another country currently so my previous estimated time of submitting patches might not (probably won't) hold up. It might take a couple of weeks before I can settle things down but I assure you this won't be forgotten.
--- End quote ---
Take your time, we are not in a hurry... Just make sure you nag me once its done, if you like also via PM so I don't oversee things.
MortenMacFly:
...is here any news?
The new release is out.
scarphin:
Sorry for the delay. Currently I don't possess a capable enough computer to work on this. I only have this crap laptop that is of no use other than browsing the web (in a very slow manner). I didn't forget about this and will start working on it as soon as I get a decent computer. It may take another couple of weeks though. Sorry again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version