CC3250MT.DLL missing

[niblettr]

Hi, Im trying to build a standalone win32 gui program using the Borland 5.5 compler and C:B 10.05 rev 6283
Every time I run the .exe I get System error CC3250MT.DLL missing.
The project compiles and runs fine under C:B

I've googled this and found that I should do the following:-

Packages - turn off 'Build with Runtime Packages'
Linker - turn off 'Use Dynamic RTL'

You have to link with one of BCC's cw32*.lib runtime library files :

cw32.lib = Single Threaded / Static Link
cw32i.lib = Single Threaded / Dynamic Link (cc3250.dll)
cw32mt.lib = Multi Threaded / Static Link
cw32mti.lib = Multi Threaded / Dynamic Link (cc3250mt.dll)

So I tried cw32.lib and then cw32i.lib (I suspects its cw32i.lib that  need)
Built the project in release mode and still cant get the .exe located in \bin\release\ to run without that dll???

here is the Build log:-


-------------- Clean: Release in test ---------------

Cleaned "test - Release"

-------------- Build: Release in test ---------------

bcc32.exe -q -w  -O2  -w   -IC:\Borland\BCC55\include  -oobj\Release\main.obj -c main.cpp
main.cpp:
Warning W8057 main.cpp 69: Parameter 'hPrevInstance' is never used in function __stdcall WinMain(HINSTANCE__ *,HINSTANCE__ *,char *,int)
Warning W8057 main.cpp 69: Parameter 'lpszArgument' is never used in function __stdcall WinMain(HINSTANCE__ *,HINSTANCE__ *,char *,int)
ilink32.exe -q -aa   -LC:\Borland\BCC55\lib -LC:\Borland\BCC55\lib\psdk  c0w32 obj\Release\main.obj ,bin\Release\test.exe,,gdi32.lib user32.lib kernel32.lib cw32mti.lib cw32i.lib comdlg32.lib cw32i.lib ,,
Output size is 7.50 KB
Process terminated with status 0 (0 minutes, 0 seconds)
0 errors, 2 warnings


One thing,(Packages - turn off 'Build with Runtime Packages') where is this pachages option? I can't find it anywhere??

[MortenMacFly]

ilink32.exe -q -aa   -LC:\Borland\BCC55\lib -LC:\Borland\BCC55\lib\psdk  c0w32 obj\Release\main.obj ,bin\Release\test.exe,,gdi32.lib user32.lib kernel32.lib cw32mti.lib cw32.lib comdlg32.lib cw32.lib ,,

Well maybe yo should read your logs more carefully. The highlighted lib in red is the first the linker picks up and is the DYNAMIC version.
Also, you link 3 times against a version of cw32XXX (all bold) why? Clean up your project / compiler settings!

And also, please don't let us do your homework.

[niblettr]

WOW, friendly bunch here GOODBYE!

[Jenna]

WOW, friendly bunch here GOODBYE!

Your post violates our forum rules in many ways.
One is, that syou show, you did not even read them or you do not care.
See for example this:

2. Compiler/Linker errors are NOT Code::Blocks errors. Usually, C++ newcomers tend to confuse the Editor/IDE (Code::Blocks) with the Compiler (MINGW / GCC). You may see some errors in the compiler output because you missed to do something right in your code. But that's not Code::Blocks troubleshooting, that's C++ troubleshooting and does not belong in here. If your program doesn't compile, READ THE C++ MANUAL.

3. Is your problem library, framework specific? There are appropriate forums for it, not the Code::Blocks forum.

And MortenMacFly gave you some hints in his answers instead of just silently removing or locking your thread.
He was neither unfriendly nor insulting.

What do you expect more ?

[niblettr]

No, I didn't expect anymore apart from the condecending manner in which he finished off the post.
Thank you MortenMcFly.

I am a complete novice at i386 programming so bear with me.

I suspected that my problems are related to the settings I have selected within C:B which is why I feel I have posted in the correct place. Help?

Anyway, I've cleaned up some of the options with C:B and I 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

where is cw32i.lib comming from? I have only added cw32.lib in the link libraries section.

[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]

interesting, I still get :-

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.

[niblettr]

ok, I created a new blank win32 project, added my code and made all the necessary changes to the build options including
 Build Options->Policy and selected "Use project options only"
linker Options->Policy and selected "Use project options only" and then did a rebuild.
Result:-

-------------- Build: Release in hexsource ---------------
bcc32.exe -q -tW  -w   -IC:\Borland\BCC55\include  -oobj\Release\HexMain.obj -c ..\HexMain.cpp
..\HexMain.cpp:
brcc32.exe -32 -foobj\Release\HexMain.res  ..\HexMain.rc
Borland Resource Compiler  Version 5.40
Copyright (c) 1990, 1999 Inprise Corporation.  All rights reserved.
bcc32.exe -q -tW  -w   -IC:\Borland\BCC55\include  -oobj\Release\HexNobbler.obj -c ..\HexNobbler.c
..\HexNobbler.c:
..\HexMain.auto.cpp:
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\hexsource.exe,,gdi32.lib user32.lib kernel32.lib cw32.lib comdlg32.lib cw32i.lib ,,obj\Release\HexMain.res  
Output size is 74.00 KB
Process terminated with status 0 (0 minutes, 1 seconds)
0 errors, 0 warnings

(where is cw32i.lib coming from?)
It all worked as it should (the .exe in the \release folder runs without the dll which is good)
I checked the settings from yesterdays project and compaired then  to the new project and they are the same (as far as I can tell)
So not sure quite whats going on.

[MortenMacFly]

(where is cw32i.lib coming from?)

I can't tell you. You must have setup that anywhere, because if you search over the entire code base of Code::Blocks there is no such thing, we don't do any magic. You can also try to remove your default.conf file which stores all settings you did for C::B to see if it is gone then. Also, you can post a minimal zipped sample project here for convenience.

[oBFusCATed]

I can't tell you. You must have setup that anywhere, because if you search over the entire code base of Code::Blocks there is no such thing, we don't do any magic. You can also try to remove your default.conf file which stores all settings you did for C::B to see if it is gone then. Also, you can post a minimal zipped sample project here for convenience.

Another option is to search the default.conf for this string, to see if it is there.

[MortenMacFly]

Another option is to search the default.conf for this string, to see if it is there.

Yes - I was about to mention the same... well if you did - then also search inside your project files (meaning source, header, C::B files).

[niblettr]

ok, I found this in the default.conf file :-

<bcc>
            <NAME>
               <str>
                  <![CDATA[Borland C++ Compiler (5.5, 5.82)]]>
               </str>
            </NAME>
            <COMPILER_OPTIONS>
               <str>
                  <![CDATA[-w;]]>
               </str>
            </COMPILER_OPTIONS>
            <INCLUDE_DIRS>
               <str>
                  <![CDATA[C:\Borland\BCC55\include;]]>
               </str>
            </INCLUDE_DIRS>
            <LIBRARY_DIRS>
               <str>
                  <![CDATA[C:\Borland\BCC55\lib;C:\Borland\BCC55\lib\psdk;]]>
               </str>
            </LIBRARY_DIRS>
            <LIBRARIES>
               <str>
                  <![CDATA[comdlg32.lib;cw32i.lib;]]>
               </str>
            </LIBRARIES>
            <MASTER_PATH>
               <str>
                  <![CDATA[C:\Borland\BCC55]]>
               </str>
            </MASTER_PATH>
            <macros>


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.)