Quantcast
Channel: Recent Topics - Forum - Embarcadero Community - Embarcadero Community
Viewing all articles
Browse latest Browse all 3677

[ilink32 Error] Fatal: Unable to open file 'FIREDAC.CONSOLEUI.WAIT.OBJ' - by: Fred

$
0
0
Hi,

I'm trying to build an EMS package in C++Builder 10.2.3 with the tutorial in the following URL:

- docwiki.embarcadero.com/RADStudio/Tokyo/...FireDAC_EMS_Resource

After using the wizard an empty BPL-project is created. The second step is putting an FDConnection on the design form. Next I save the project and unit files. In the unit header the following includes are created automatically:

#include <System.Classes.hpp>
#include <System.SysUtils.hpp>
#include <EMS.Services.hpp>
#include <EMS.ResourceAPI.hpp>
#include <EMS.ResourceTypes.hpp>
#include <Data.DB.hpp>
#include <FireDAC.Comp.Client.hpp>
#include <FireDAC.ConsoleUI.Wait.hpp>
#include <FireDAC.Phys.hpp>
#include <FireDAC.Phys.Intf.hpp>
#include <FireDAC.Stan.Async.hpp>
#include <FireDAC.Stan.Def.hpp>
#include <FireDAC.Stan.Error.hpp>
#include <FireDAC.Stan.Intf.hpp>
#include <FireDAC.Stan.Option.hpp>
#include <FireDAC.Stan.Pool.hpp>
#include <FireDAC.UI.Intf.hpp>

Then I compile and link my BPL-project and I received the following error:

- [ilink32 Error] Fatal: Unable to open file 'FIREDAC.CONSOLEUI.WAIT.OBJ'

All my directory locations for INCLUDE and LIB files are correct. What is going wrong?

Tools -> Options -> 32-bit Windows -> Classic Compiler -> Library path:

$(BDSLIB)\win32\release
$(BDSLIB)\win32\release\psdk

If I do the same with an MultiDevice application the includes are also created automatically and then the compile and link process have no errors. What is the difference between an application and package compile/link.

Thanks to everybody who can help me.

Best Regards,
Fred

Viewing all articles
Browse latest Browse all 3677

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>