using setupapi.dll without libimp*.a file

[josip]

Program in FPC is executed from cmd prompt on Win. Some functions from setupapi.dll are used. In source code there are defined like this...

Code: Pascal  [Select][+][-]

1. function SetupDiGetClassDevsA(ClassGuid: PGUID; const Enumerator: PAnsiChar;
2.   hwndParent: HWND; Flags: DWORD): HDEVINFO; stdcall; external 'setupapi.dll';
3.  
4. function SetupDiEnumDeviceInfo(DeviceInfoSet: HDEVINFO; MemberIndex: DWORD;
5.   var DeviceInfoData: TSPDevInfoData): LongBool; stdcall; external 'setupapi.dll';
6.  
7. ...

Everything is working fine, but using dll functions generate libimp*.a file, that I don't want to have in program directory. Is there are any way to use or release dll without generating / leaving libimp*.a file.

[Cyrax]

Are you using Lazarus to develop your app? Check out in Project->Project Options...->Compiler Options->Paths that Unit output directory have different value than Target file name text field have.

[josip]

No Lazarus, just FPC. After program is compiled, every time when exe is started, libimp*.a file is generated (if it is erased before).

[Thaddy]

No Lazarus, just FPC. After program is compiled, every time when exe is started, libimp*.a file is generated (if it is erased before).

???? That would be a - hidden? - feature.
I don't think that is what you mean to tell us. 
After compilation and linking your project the dependecies are resolved in the binary, the libimp for that executable is linked in and will never regenerate itself when you start that executable. .

[marcov]

Thaddy is right.

I think you somehow trigger recompilation when starting the exe and that that regeneration triggers the .a generation.

[josip]

Thank you very much for clarification. I was wrong. libimp*.a and dummy.$$$ are generated during compiling, and not by executing generated exe file. Problem solved.