User forums > Using Code::Blocks
.def & import library names
Seronis:
dont bump threads unless you are adding more to the discussion.
MortenMacFly:
--- Quote from: thedmd on February 15, 2010, 11:54:16 am ---Do you agree to implement this solution in C::B?
--- End quote ---
What did I say:
--- Quote from: MortenMacFly on February 15, 2010, 11:41:37 am ---
--- Quote from: thedmd on February 15, 2010, 10:35:58 am ---Is it sufficient?
--- End quote ---
I guess so... :lol:
--- End quote ---
???
I am awaiting a patch accordingly.
thedmd:
I have bumped this thread since I don’t believe discussion is over. Yes, we agree to that solution, but this don’t close the topic. Nothing was said about possible implementation details.
I had asked Morten if he is willing to implement this feature, because I believe he is best for this job. My changes may hit parts of C::B that I’m unaware of and my knowledge about C::B source code is very limited at the moment.
I believe “I guess so...” don’t carry the information: “This is a reasonable solution, please prepare a patch so we can be able to test it and give you a feedback.”. I’s tempting to place here some smiling emoticon, but I’m trying to avoid them for a while now, so you can read this comment instead.
I still have one question unanswered. Why target name is computed in more than one place in C::B? This information will be definitely helpful.
P.S. In case of doubts, please look at the left side of this post.
MortenMacFly:
--- Quote from: thedmd on February 18, 2010, 08:12:05 am ---I had asked Morten if he is willing to implement this feature, because I believe he is best for this job.
--- End quote ---
I don't exactly recall this question, but I guess it'll take time then. I am quite busy atm and in addition I won't start with work on something that works but doesn't look nice. Other things that really don't work have a higher priority for me.
I think this discussion lead to a proposal how to do it. Now it's time to get the hands on. But this is really nothing hard to do, most work comes with testing every combination I guess. So I am hereby asking for volunteers - it's a nice and easy job to do, just right for people that want to help with C::B development and are just at the beginning.
Just start in compilercommandgenerator.cpp, method:
--- Code: ---wxString CompilerCommandGenerator::SetupOutputFilenames(Compiler* compiler, ProjectBuildTarget* target)
--- End code ---
The other places should not be of interest.
thedmd:
My earlier question may be misinterpreted. I see that it can be missed.
In my opinion we have a problem and we need to solve it, not just discuss. Now we know what each other thinking about this. We finally agreed to solve the issue and topic is going to be closed. Nice and smooth.
I will try to prepare appropriate patch soon. Thanks for hint, it will be helpful.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version