User forums > Help
CC3250MT.DLL missing
stahta01:
Did you check both CB locations?
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28general%29#Q:_I_would_like_to_compile_a_project_using_some_non-standard_libraries._How_can_I_indicate_to_CodeBlocks_that_these_libraries_and_include_files_exist.3F
Tim S.
niblettr:
lol, I did and got in a right muddle, so I ignored the global compiler settings and decided to stick to project compiler specific setting.
I did this by right clicking the my project Build Options->Policy and selected "Use project options only" (done for the root project, and Debug and Release)
niblettr:
interesting, I still get :-
ilink32.exe -q -aa -LC:\Borland\BCC55\lib -LC:\Borland\BCC55\lib\psdk c0w32 obj\Release\HexMain.obj obj\Release\HexNobbler.obj obj\Release\HexMain.auto.obj ,bin\Release\Hex_project.exe,,gdi32.lib user32.lib kernel32.lib cw32.lib comdlg32.lib cw32i.lib ,,obj\Release\HexMain.res
and .exe in the \bin\Debug\ works! without moaning about the .dll
BUT
the .exe \bin\Release\ does NOT.
I did rebuild with buid target:Debug and then build target:release.
MortenMacFly:
--- Quote from: niblettr on August 09, 2012, 02:58:31 pm ---interesting, I still get :-
--- End quote ---
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. But you should know best, where you started adding flags... ???
niblettr:
does
Build Options->Policy and selected "Use project options only"
linker Options->Policy and selected "Use project options only"
under project property settings basically ignore global compiler settings?
if so, i shouldnt need to change global build and linker setting..no?
whats a build script? (is this auto generated?) If its a manual thing, then no, I don't have one.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version