GE1956

The build didn't produce any lib files, only obj files. Now I helped myself using tlib.exe to create the appropriate lib files: - tlib IcsCommonCB103Run.lib +IcsCommonCB103Run.obj - tlib IcsVclCB103Run.lib +IcsVclCB103Run.obj

Now I have another issue, when I try to use a TPop3Cli component. The following files cannot be found: - IcsCommonCB103Run.lib - IcsVclCB10Run.lib Where are those files located? Is it missing because I was not able to install the component set correctly?

Thanks for the clarification. I tried to compile OverbyteIcsCBXe3Run.cbproj, as you did recommend, but unfortunately the IDE displays a compiler error: [DCC Fatal Error] pasall.tmp(1): F2048 Bad unit format: 'c:\borland\rad studio\20.0\lib\obj\system.dcu' - Expected Version: 33.0, Windows Unicode(x86) Found Version: 14.0, Windows Ansi(x86) My C++ Builder 10.3 version does not seem to be compatible with the CBXe3 project.

Sorry for the late reply, but I was finally able to give it a try. The file you did Mention does not exist, the closest I could find was D101Install.groupproj, but trying to open the groupproj file,an error message informs about a required Personality Delphi.Personality not being available.Might this happen due to the fact that I am using Embarcadero C++ Builder? Thus, I wasn't able to install the component set, but found out, that the required .obj and .hpp files were generated during the earlier compilation of the 103FmxVcl runtime Project, which is sufficient for the use case I need, but nonetheless I would be interested in a solution to the problem described above.

I am trying to install the IcsCommonCB103Design component in Embarcadero XE10.3 (C++), I have already followed the instructions described in another thread: https://en.delphipraxis.net/topic/763-trying-to-install-ics-858-on-c-builder-rio-1031/ I was able to install these two components: IcsFmxCB103Design.cbproj IcsVclCB103Design.cbproj ...unfortunately, the install process failed on IcsCommonCB103Design.cbproj, while the compilation of the corresponding run Project (IcsCommonCB103Run.cbproj) has been successful. The linker exits with the error message: c:\borland\rad studio\20.0\Bin\CodeGear.Cpp.Targets(3799,5): error : Fatal: Datei 'WINAPI.WINDOWS.OBJ' cannot be opened I am working on a Windows 10 System, and I can't find any WINAPI.WINDOWS.OBJ file, only the pascal and dcu files do exist: C:\Borland\RAD Studio\20.0\source\rtl\win\Winapi.Windows.pas C:\Borland\RAD Studio\20.0\lib\win32\release\Winapi.Windows.dcu Now I do wonder, where this file should be located and how I am able to find/download/compile the needed file? Due to the fact that I only work with the helper component TMimeDecode, I might consider to use the class without any component at all, if this shouldn't work, would this be possible? In case, there is no possible soluation at reach, I need to find another library for my mime decode use case.

I have a problem using the new v8 version of OverbyteICS with MimeDecode in my C++ project with Embarcadero XE10.3. In my old studio I was able to work with v5 using the TMimeDecode component after including MimeDec.hpp in the unit header file. In the unit cpp file I used #pragma link "MimeDec" to load the library., but in V8 I am not able to find the cpp header file in the extracted Source folder, only the delphi version (OverbyteIcsMimeDec.pas). Is it still possible to use the old methods connected to MimeDecode v5 (Method 'DecodeFile', field 'CurrentData', etc.) in the new Embarcadero XE10.3 (with OverbyteIcs v8)? Or is it maybe possible to use v5 with XE10.3? Whenever I click on the unit file in the project tree, I get a message signaling that the TMimeDecode component couldn't be found. I even tried to add the OverbyteIcsMimeDec.pas file as well as further needed *.pas files, but still the same error is shown. Is there anything else I need to do? The delphi compiler did generate the appropriate *.hpp files in my Embarcadero directory, which I did include in my project. I did also add include "OverbyteIcsMimeDec" to my unit header file, but without success. I would really apprecaite some help regarding my efforts to implement MimeDecodc during the migration process.