A win64 project, finished quickly, the debug mode to compile a release version this morning, each unit compiled through, finally links, pop up a error:
Out of memory, code2

A search on the net, the heart is cool,,,,

Refer to instructions to run the official web site, and note that the show is on the inside of the 10.4.2, that is to say, even if is the latest version, will also have this problem:
The 64 - bit Windows c + + Application with a FireDAC Component took Raise Error
The following error is raised when attempting to compile an application using a single FireDAC component, The when The platform is Windows x64 with static linking:

C: \ program files \ (x86) embarcadero \ studio \ & lt; N.n & gt; \ Bin \ CodeGear. Cpp. The Targets: warning: warning: Out of memory
C: \ program files \ (x86) embarcadero \ studio \ & lt; N.n & gt; \ Bin \ CodeGear. Cpp. The Targets (2751, 5) : error MSB6006: "ilink32 exited with code 2.
The workaround is not to link FireDAC statically Win64 in c + + apps.

Means, if your win64 project, using The FireDAC component, then compiled into a static Release version, it absolutely will pop up The error, The official also gives The solution: The workaround is not to link FireDAC statically win64 in c + + apps.
Means: flexible methods, it is the program compiled into a static,,,, this is not equal to didn't say,,,

So get along while, finally compiled a version, with a lot of BPL and DLL files, specific as follows:



Is there a better way, can be less dependent on file?? It is no use to any third party controls,,,

CodePudding user response:

The workaround is not to link FireDAC statically Win64 in c + + apps.
I understand this sentence is wrong?

How can I not to link FireDAC statically Win64 in c + + apps???????

Even if released, less BPL and DLL or ah,,

CodePudding user response:

RTL can static links, such as the FIREDAC * only use the runtime packages can

CodePudding user response:

I was so in the IDE Settings, then why so many extra BPL and DLL,,,

CodePudding user response:

The options - & gt; Packages - & gt; The runtime packages, runtime package import libraries can be specified in the runtime package, don't need, remove

CodePudding user response:

Tried it once, have been streamlined to a minimum, but program dependency and I on the first floor of the BPL and DLL, one can't be little,,,
Set as shown in figure:


I drunk,,,,

CodePudding user response:

Do you have any alternative FireDAC??
UniDAC??

CodePudding user response:

You look at the project directory with the same name. Pdi file is a text file, listed in the actual depends on the runtime package, I said in front of the "RTL links can be static, such as" there is a problem, as long as you use the runtime package, RTL cannot be static link also invalid (set up), but there is no direct or indirect use of runtime package is not need

CodePudding user response:

The debug configuration under static link?

CodePudding user response:

refer to the eighth floor ooolinux response:

debug configuration under static link?

So, should will only depend on the first floor I capture the two DLL files, but the program is running speed will slow down a little, and then because the EXE file contains the DEBUG information, so less secure

CodePudding user response:

refer to 7th floor early play big play nuclear response:

you look at the project directory with the same name. Pdi file is a text file, listed in the actual depends on the runtime package, I said in front of the "RTL links can be static, such as" there is a problem, as long as you use the runtime package, RTL cannot be static link also invalid (set up), but there is no direct or indirect use of runtime package is not need

I saw, PDI file is not in the project directory, in the Release directory, and I rely on item listed on the first floor, compared to less two DLLS and BPL file, but I no matter how to set up, after compiling all need them,,,

CodePudding user response:

I want to know the debug version and release version exe respectively how old?

CodePudding user response:

I understand: the debug version, contain debugging information, not through the release of optimization, almost running speed, though I am the project for speed not too sensitive, but on some projects, the speed of the two patterns differences are still a little big, specific to baidu, the second is the debug version of the exe, contains the debugging information, this thing for code items requiring security is not safe,

Finally, the debug version of the even unchecking the RTL and runtime package, release, or to take me on the first floor of the two DLL,,,