compileing

It depends on how you compile your application. If you compile your application with runtime packages, then you''ll need to ship the relevant .bpl files with your application. However you can generally statically link the packages. Worse comes to worse, you can look at the import table on the executable. One way to do it, is use Quick View. Right click on the application from explorer and select Quick View. Scroll down a little and it will tell you all the DLLs it loads and the functions it uses from them. For example it might use borlndmm.dll, kernel32.dll and comctl32.dll. kernel32.dll and comctl32.dll the end user should already have on their computer. borlndmm.dll is something they probably don''t, so you should ship it with your executable. Generally just leaving the dlls/packages in the same directory as the executable is sufficient.