🚀 go-pugleaf

This is similar to entry posted by "401kPensionGuru" on Jan 1, 2008
titled "Console Indy10 App can't find OBJ files".  But in this
instance, we do have under the Project Options for Release under
"Paths and Defines" in the list of directories for "Library Path" the
entry:

  $(BDS)\lib\release

Which in this directory are the lib files:

   IndyCore.lib
   IndyProtocols.lib
   IndySystem.lib

But this configuration/setup does not seem to be able to resolve the
various entries within the library files that are in the directories
listed for "Library Path"s.  To resolve this as was suggested in the
previous discussion referenced "You do not have Indy's library files
added to your project."  Thus I went to the Project drop down, "Add to
Project" and browsed to the lib\release directory and selected the
three lib files and added these to the project so they appear in the
"Project Manager".   Now when I  "Build all projects" a working exe
file results that can now be transported from machine to machine
without carrying the baggage (e.g. RTLs and DLL).

So bottom line:  We want to be able to compile to an EXE with the
linking option "Dynamic RTL" unselected and the Packages option "Build
with runtime packages" also deselected as well.  Thus in order to use
the Indy tools we need to specifically add to the project the three
individual files for each project.  Is this correct or is there a
Linker issue which fails to use the library entries specd in the
project/default  "Paths and Defines" library path list?