Member Avatar for karan.rks

Hey...

I have created a prgoram in turbo c++, and i wanted it to export it as a separate file ... that is out of the bin file.. and out of all the other include file, so that it actually runs on every computer who even does not have a copiler installed to it!!

i know it is possible, but i dont knw how dis will happen

  • 2 Contributors
  • 2 Replies
  • 197 Views
  • 1 Hour Discussion Span
  • Latest Post Latest Post by karan.rks

Dani AI

Generated

Short answer: the “final file” is the compiled, linked executable (the .exe). , build your project in Turbo C++ (compile + link) and copy the produced .exe out of the IDE’s output folder — that file is what you can distribute. is right that simply sharing the .exe is the usual approach, but there are important compatibility and dependency details to check before handing that .exe to someone else.

Practical checklist:

  • Build (compile and link) in Turbo C++. The IDE writes an .exe to your project/output or BIN folder.
  • If your program uses external files (data files, images, config) copy those too and keep the same relative paths.
  • Test the .exe on a clean target machine (one without a compiler). Note any error messages — they tell you why it won’t run.

Troubleshooting and gotchas:

  • If the .exe shows “not a valid Win32 application” or “this app can’t run on your PC,” you’re probably using an old DOS/16-bit Turbo C++ executable; 16-bit programs won’t run on modern 64-bit Windows. Workarounds: run it under DOSBox, or recompile with a modern toolchain.
  • If the target machine reports a missing DLL or runtime error, the executable depends on external libraries. Fixes: rebuild with static linking (so the runtime is embedded), or bundle/install the required runtime on the target PC.
  • If your code uses Borland-specific headers (graphics.h/ BGI), those parts often won’t work with modern compilers and will need porting.

Recommendation: since your school requires Turbo C++ for submission, compile in Turbo C++ for that. For wider distribution, recompile the same source with a modern compiler (Code::Blocks/MinGW or Visual Studio) to produce a portable 32/64-bit executable, enable static linking if you want fewer external dependencies, and always test on a clean machine before sharing.

Recommended Answers

All 2 Replies

Member Avatar for NP-complete

for running an app you do not need a compiler. You can simply take out the .exe and share it.
It'll run, but given the fact that you're using "Turbo C++" it might not run as you would've expected it to, on a few machines.

A few advice:

  • Get rid of that turbo c. Immediately. Use Code::Blocks or Visual Studio 2010 express. You'll thank me later!
  • Read up on static linking of libraries. (it'll help for the issue at hand)
Edited by NP-complete
Member Avatar for karan.rks

thanks man... but this project dat i am making is for the school and they want it in turbo C++

yeah.. i have tried code::blocks...its great.. still!! thanks for the help

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.