CC3250MT.DLL missing

[MortenMacFly]

Should I just change cw32i.lib to cw32.lib and save or just delete the entry (means I have to manually add to project which I have been doing anyway.)

No, just go to the global compiler options -> Settings -> Compiler and remove the libraries under the tab "linker settings"!

BTW: Never edit the config file manually! This can seriously break C::B and even lead to crashes. Only C::B is allowed to edit this file though the settings UI interface.

BTW: This also shows me that you were too lazy to do what I told you:

The linker settings are constructed form:
1.) global compiler settings - linker libs and "other linker options"
2.) project linker settings -> same thing
3.) target linker settings -> same thing
4.) Attached build scripts (which I doubt you have)
So you need to check at least 6 places.

...because otherwise you would have found yourself. So don't expect any more help.

Edit: Topic locked.

[Jenna]

Build Options->Policy and selected "Use project options only"
linker Options->Policy and selected "Use project options only"

Global compiler settings are used in any case, as long as you use the compiler they belong to, that's wha they are called global.

The policy you use is to specify, whether to use only target or project options and (if you use both) in which order they should be applied.

EDIT:

There are only a few cases where global options need to be used.

[niblettr]

MortenMacFly, what is you problem?? Why are you are so rude and arrogant?
I asked the question first whether :-
 Build Options->Policy and selected "Use project options only"
linker Options->Policy and selected "Use project options only"

ignores the global setting but I didnt get a reply so I patiantly waited until I got an answer THEN I would have done the steps you asked?
I didn't ask for YOUR help specifically so If you didn't want to help then don't rather than just being rude!

Ok

[niblettr]

Thankyou Jens, that makes sense now. I will always keep an eye on the global settings

[MortenMacFly]

MortenMacFly, what is you problem?? Why are you are so rude and arrogant?

Look, the thing is very simple: I don't act arrogant, but eager you to respect our forum rules you agreed to when registering with the forums. Obviously you didn't even bother to read those and you don't bother to read carefully any help given.

If all people are always asking the same question and don't read the help we provide in advance we answer over an over again and again the same questions. In your case its a compiler/project library setup which has been answered roughly a million times now. I am just sick of over-and-over repeating what's written in the comprehensive FAQ because people don't want to read.

We are responsible for the content of the forum BY LAW, so I cannot just ignore what you write. And I also can't ignore what others answer. If you are running a forum yourself you'll understand my frustration, I promise.

If that sounds rude to you - I am sorry, but thats the world we live in. And I'd love to improve Code::Blocks instead of listening to forum noise.

[niblettr]

I did a forum search and could not find anything related to my problem.
I posted in the help (I think its in the right location)
so what did I do wrong exactly?

[MortenMacFly]

so what did I do wrong exactly?

Well you should first try to understand your problem. If you don't understand how a compiler work/linker works, this forum is of no help. For example: If your app has a dependency on a DLL its your fault, because you link against dynamic libs. Its not C::B's fault and it will never be. Then inspect the build log precisely and try on the command line if unsure. If you get the same error on the command line again its not a C::B issue. Finally don't expect compiler specific support here - C::B can manage very many compilers and we don't even know all of them so we cannot provide full support.

This all is written in the FAQ which besides these hints also gives a lot really helpful advise in general to understand and fix such issues yourself. So I strongly suggest you read it, besides the C::B manual / WiKi where is written exactly, how the C::B compiler front-end works. It is not only to know C::B but also to gather more general understanding and I am sure you will learn many things, maybe even for your live:

http://forums.codeblocks.org/index.php/topic,9996.0.html

http://wiki.codeblocks.org/index.php?title=Creating_a_new_project

http://wiki.codeblocks.org/index.php?title=A_short_overview_about_Code::Blocks_architecture

http://wiki.codeblocks.org/index.php?title=FAQ

...more precisely:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)

...even more:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28general%29#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

http://www.codeblocks.org/docs/main_codeblocks_en.html

Try to capture the general story behind these:
http://wiki.codeblocks.org/index.php?title=User_documentation#Third-party_libraries

So... to sum up: If you want to do all of us a favour, read what we provide out of our experience. Note that this is not meant offending, I seriously believe it will help and would have helped in the first place.

[niblettr]

Not once did I say the its was C:B fault! It did do a lot of reading up prior to posting my problem (i even hinted and posted my google findings on the matter in my very first post. So, its not good carma calling people who you don't etc. lazy etc (im pretty sure that does not follow the code of practice for MODs etc.)
Anyway, I think we've established that the problem was, I've mixed up the settings within C:B which is why I sought so seek help on a C:B forum.

Thank you for all your help, problem got solved.