No. Binary executables are low-level and procedural while C++ source code is high-level and structured. Low-level means there is little or no abstraction between the source code and the machine code (since binary executables are machine code there is no abstraction whatsoever). High-level means there is a high level of abstraction. At best you can disassemble the machine code to produce low-level disassembly which will approximate the original assembly instructions, but without any comments and user-defined names, which must be manually reproduced. Even so, assembly is low-level and there's simply no way to reproduce a high-level language from a low-level source.
Note that although it is possible to produce C++ instructions from low-level assembly, the C++ source will bear no relation whatsoever to the original C++ source code, because you'd simply be translating the procedural code into the equivalent C++ procedural code. In other words, the result would be spaghetti code built entirely from primitive data types (with no object classes or other user-defined types), and no function calls whatsoever (the main function will be the only function). All abstraction is completely stripped out during compilation, and there's simply no way to reproduce even an approximation of that abstraction once a program is compiled and linked.
A source file is typically a readable, Ascii file, that is not the result of a compiler or translator to binary machine code.
A .vb6 file is visual basic 6 source code, sometimes with it are .frm files that you would need. A .dmg is a Macintosh binary. you would have to find a program to compile the vb6 code to a Macintosh binary.
Usually the cases are that the source code versions are newer than what is provided by the repositories. Also, you can't readily tell what is in the binary-only builds as everything's done for you. In most cases is that the specific software package may not be available in the repositories that warrants a "build from source".
Usually the cases are that the source code versions are newer than what is provided by the repositories. Also, you can't readily tell what is in the binary-only builds as everything's done for you. In most cases is that the specific software package may not be available in the repositories that warrants a "build from source".
A makefile is a simple configuration file to instruct a compiler into creating a binary from the source code. Most users do not need to use a makefile; they can just download a pre-compiled binary from the program's website.
Source code consists of one or more plain text files. Saving those files to disk saves the source code. Source code may also include binary files such as image resources (bitmaps, icons, etc), but does not include external dependencies, executable files or libraries (such as EXE and DLL files). There will normally be a project file associated with the source code files, allowing the source code to be organised, loaded and saved as a single unit within the development software (IDE). Saving the project saves all the changes within the source code. The IDE may also generate some source code files for you, depending on the options you select when you start a new project. Multiple projects are often managed by a solution file. Again, this is a plain text file specific to the IDE. The IDE may also generate databases and cache files to assist in the development of your projects, but these are not considered source files -- they are generated and maintained by the IDE. Similarly with intermediate files created during compilation of your project. Source code is simply the code you write (or is generated for you), and the resource files you create for your project.
All C++ source code is is a text file with the .cpp extension. So if you save your code as *****.cpp then it is automatically C++ source code.
To convert source code (.c file) to an executable (.exe) file you have to use a compiler, which is a translator of source code to machine code.
A source code file is a plain-text file containing C++ instructions. The instructions must be compiled and linked to create a native machine code executable.
DLL - Dynamic-link library is the compiled project code. Computer work in binary code. Programmers write code in English. The complier transforms the English written code into binary. All of the pages of code the programmer writes are transformed into one file. This file is named XXXXX.dll
binary file
digital certificate A code used to authenticatethe source of a file or document or to identify and authenticate