Sign in to follow this  

Borland 5.5 Question

This topic is 4305 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Not a programming question at all. What is the newest (free) Borland C++ compiler? Also, are Borland C++ Compilers compatible with things like DirectX 10? I would assume yes, but assumptions aren't worth anything. Thanks for helping me out here.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
I've been pondering the exact same question for a few days now. Borland seems to be excellent and filled with tons of potential if only we could have this one question answered. Thanks !

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
The newest free Borland compiler is the 5.5.1, released in 2000 which is a minor update to the 5.5.0 released in 1999.

I've used Borland C++ 5.0 with DX6 (that's the 5.0 compiler I guess), haven't tried any later combinations.
That took some work to get the correct lib files and convert some headers to work (everything shipped in the distro is for Visual C++ only, Borland's compiler and linker didn't like it out of the box).

I guess you can do the same with later compiler and DX versions, but I seriously doubt you're going to get DX10 to work with a compiler dated 1999 (DX10 btw isn't even released yet, AFAIK it's not even feature complete).
I do know DX10 will require Windows Vista to work at all, as well as being incompatible with existing video hardware (that was confirmed by one of the leads on the Microsoft FSX team earlier this year when he discussed rumours that FSX would require Vista and DX10 (it won't)).

I'd guess your best bet with free compilers right now would be Visual C++ 2005 Express, coupled with the PSDK and DX 9.0c SDK.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
I'm using Borland 5.5 to make DirectDraw apps which run fine on my 98 machine with an old graphics card but slow to a crawl on newer XP and 2000 machines with newer cards.

I've got DirectDraw7 to work with it by using implib on ddraw.dll (the ddraw.lib that ships with Borland 5.5 does not seem to have DirectDrawCreateEx in it for some reason) but doesn't improve the speed on newer cards.

It is only a small number of rectangular blits, some transparent and some not. Is the lag on the newer cards because they don't support 2D operations properly anymore and do I need to upgrade my brain to Direct3D to get decent performance? If I compile and run with DDCREATE_EMULATIONONLY or disable DirectDraw acceleration in dxdiag, the game speeds up to very quick but the graphics go a bit flickery and naff.

Anyone got any thoughts on this? Ta.

Share this post


Link to post
Share on other sites
Ok, Visual C++ 2005 it is, but where can I find some decent resources for it? All I ever find are resources for C++6. Also, does Visual C++ 2005 use managed DirectX or just normal? Thanks.

Share this post


Link to post
Share on other sites
VC6 is extremely old, no longer supported, and not standards compliant.
Most code for it should work with newer versions too though, though you may have to correct errors that were required to make it work with VC6.
So if you know standard (ISO) C++ you should have no trouble with VC2005.

All it takes is getting used to a different editor.

Share this post


Link to post
Share on other sites
One other thing, theres something up with my Visual C++ 2005 linker. Whenever I try to compile anything, I get this report of errors from the linker:
Linking...
0.obj : error LNK2019: unresolved external symbol __imp__PostQuitMessage@4 referenced in function "long __stdcall WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YGJPAUHWND__@@IIJ@Z)
0.obj : error LNK2019: unresolved external symbol __imp__DestroyWindow@4 referenced in function "long __stdcall WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YGJPAUHWND__@@IIJ@Z)
0.obj : error LNK2019: unresolved external symbol __imp__DefWindowProcA@16 referenced in function "long __stdcall WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YGJPAUHWND__@@IIJ@Z)
0.obj : error LNK2019: unresolved external symbol __imp__DispatchMessageA@4 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__TranslateMessage@4 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__GetMessageA@16 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__UpdateWindow@4 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__ShowWindow@8 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__CreateWindowExA@48 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__MessageBoxA@16 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__RegisterClassExA@4 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__LoadCursorA@8 referenced in function _WinMain@16
0.obj : error LNK2019: unresolved external symbol __imp__LoadIconA@8 referenced in function _WinMain@16

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
you will have to install the PSDK (platform SDK) as well to create Win32 applications (rather than .NET applications).
More information and instructions on the VC2005 site.

Share this post


Link to post
Share on other sites
Thanks, so much. I've been freakin' pissed off at my linker since I found this bug, but now that I have a solution, I'm good. Thanks again.

Share this post


Link to post
Share on other sites
Just a little note I've herd rumors/news that Borland is leaving the IDE industry and getting into the Application Lifetime Management market. Mainly because of free tools like Eclipse and others they feel that making commercial tools will no longer be profitable r necissary. Not sure if this means all Compilers or just the IDE Tools themselves it wouldn't really make sense if it was only the IDE's and not the compilers as well. I know they are currently looking for someone to buy the tools, maybe it will be for the better?

Anyways here is a link
http://www.eweek.com/article2/0%2C1895%2C1926073%2C00.asp

Share this post


Link to post
Share on other sites
The reason Borland is getting out of the IDE market has nothing to do with the economic success of the division and everything with a misguided idea that Borland should aim at "enterprise" customers only, and the core customer base of the IDE division (which still generates something like 80% of the company revenue...) are small and independent developers.

It's the old Inprise fiasco all over again, except this time there will be no IDE division left to cover the losses of the rest of the company.

Share this post


Link to post
Share on other sites

This topic is 4305 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this