Well, i had almost a two hours' tryst with BC 5.5 command line tools, integrated and run from within the code::blocks C++ ide.
(Had had to workout my MSc.IT lab exercises).

at first i got the DevC++ ide with the GCC compiler but saw that the recommendations for writing sources was in borland c++.
it is always better that i follow what has been prescribed as far as the educational curriculum is concerned.
Thus begun the tryst with BC++.

All was fine - the compilation was smooth but alas, the linking process failed for no reason.
ended up getting a list of unresolved externals such as this :
"Unresolved external '___CRTL_VCL_Init' referenced from C:\BORLAND\BCC55\LIB\C0X32.OBJ", from the linker.

ended up breaking my head to no end. all the library/include paths were specified appropriately!
all the compiler/linker directives were correct. but still the problems persisted.
tried out creating a bcc32.cfg & ilink32.cfg with no avail.

finally, finally, bumped onto the usage of the .lib files in the ilink32 command line. tried including the cw32.lib by hand but in vain.
this time though the list of unresolved externals were reduced. and finally, found an option under code::blocks ide->Settings->Compiler & Debugger->Linker->Link Libraries.

Manually added cw32.lib, cw32i.lib, cw32mt.lib, cw32mti.lib and import32.lib to the Link Libraries.

and That did the magic! whew! my program compiled like a beauty!
dunno if i have to say this as my stupidity or was it a missing step in code::blocks ide's automatic detect & config of the BC 5.5 command line tools.

anyways, am happy i got the problem solved.

---

Windowz :: Development :: Tools
Sivaramasundar