If you just "Add" then the source file will be copied to the project (so a new copy can then have local edits) but if you want to keep a central copy that will be used in multiple projects in future and they should all "see" the same version then use the "Add as link" option instead. You need to right click the project name then use "add existing item." to tell it where the other. PS in the picture you attached (why attach when you can inline?) the problem is clear at the top right - in the Solution you only have main.cpp listed and not the other file. o file that the linker is interested in using. How could it know from the name "adc.h" which of those sources was the one to be built in? Also it is not the LINKER that has to see the sources it is the PREPROCESSOR and COMPILER. Also just because you have an adc.h you might have the code in adc_old_version.cpp and adc_new_version.cpp. h in "include") so how could it possibly know where the.
cpp/.c that it documents (often project have. You can create a directory using the Windows File Manager Program or by typing the. h isn't necessarily in the same directory as the. Create a directory called HELLO to hold the files for our hello program.
If there are manual steps required, write the details down into a text file (for example, readmebuild.txt) and put that under source control as well. h file.Then you are wrong on a couple of things. Use scripts, makefiles, or files of your favorite build tools. Itisalright wrote: I thought linker would automatically find.
0 kommentar(er)
