TotteKarlsson 1 Posted March 19, 2021 (edited) I am restructuring a project (a VCL Forms application) to use bcc32c instead of the classic compiler. I'm stuck at this linker error: [ilink32 Error] Fatal: Unable to open file 'DATA.OBJ' Anyone knowing what library I should/could add in the following pragma. #pragma comment(lib, "the-import-lib") Or if there is another way to find out where the linker error comes from. Edited March 19, 2021 by TotteKarlsson Share this post Link to post
hansw 4 Posted March 19, 2021 I would assume that the library paths for bcc32c are different from the paths for the classic compiler. You could compare the arguments passed to ilink32 in both settings. HTH, Hans Share this post Link to post
weirdo12 21 Posted March 23, 2021 Did you search your code for #pragma link "Data"? Share this post Link to post
TotteKarlsson 1 Posted March 25, 2021 On 3/23/2021 at 11:03 AM, weirdo12 said: Did you search your code for #pragma link "Data"? I did. Not to be found anywhere. This problem popped up while reorganizing code into several individual packages. I do believe I got this fixed by changing my own pragmas. This 'type' ( no lib extension, #pragma comment(lib, "bindcomp") into this #pragma comment(lib, "bindcomp.bpi") I suspect using the first #pragma links static libs into the package, which could be fine. But then, when a package links to a package that have statically linked packages, I get linker errors. Wonder why the linker can't reveal the reference? Share this post Link to post