64 bit?
Re: 64 bit?
The dcldacsbridgeXX.dpk package should be compiled only for Win32, since the IDE is a 32-bit application.
If you mean something else, please write us in more detail.
If you mean something else, please write us in more detail.
Re: 64 bit?
Victor, i don't understand. I'm not compiling the IDE, i am compiling my own 64 bit program. The CRSSHIOHandler and the CRSSLIOHandler cant be moved from the tool palette to a 64 bit form, only to a 32 bit form. Its grayed out if I work in 64 bits.
Regards, Pär
Regards, Pär
Re: 64 bit?
I also tried to follow your instruction from a year ago:
"Thank you for the information.
To solve the issue, please try specifying an exact absolute path to the %UniDACDemos%\TechnologySpecific\SecureBridge directory in the "Library path" for all supported platforms using the menu Tools-Environment Options-Delphi Options-Library. %UniDACDemos% is the UniDAC Demo projects installation path on your computer.
We will change this information into correct one in the readme.html file."
So i put this path:
"C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge"
In tools : library :lobrary path for both 64 and 32 bit version.
I also followed this instruction:
Click Tools > Options > Environment Options > Delphi Options > Library. In the Library path field, specify the path to the directory containing the compiled packages.
and I have:
C:\Program Files (x86)\Embarcadero\Studio\19.0\lib\win64\debug
In my Library path for 64 bit.
That's where my CRSSHIOHandler.dcu and CRSSHIOHandler.dcu is located. I hope that is what you are referring to with "the compiled packages".
"Thank you for the information.
To solve the issue, please try specifying an exact absolute path to the %UniDACDemos%\TechnologySpecific\SecureBridge directory in the "Library path" for all supported platforms using the menu Tools-Environment Options-Delphi Options-Library. %UniDACDemos% is the UniDAC Demo projects installation path on your computer.
We will change this information into correct one in the readme.html file."
So i put this path:
"C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge"
In tools : library :lobrary path for both 64 and 32 bit version.
I also followed this instruction:
Click Tools > Options > Environment Options > Delphi Options > Library. In the Library path field, specify the path to the directory containing the compiled packages.
and I have:
C:\Program Files (x86)\Embarcadero\Studio\19.0\lib\win64\debug
In my Library path for 64 bit.
That's where my CRSSHIOHandler.dcu and CRSSHIOHandler.dcu is located. I hope that is what you are referring to with "the compiled packages".
Re: 64 bit?
AND
The path
C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge\Delphi25
Is also there, whats wrong?
The path
C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge\Delphi25
Is also there, whats wrong?
Re: 64 bit?
As indicated earlier, the 32-bit package must be installed in the IDE for design-time development. For successfull compilation, your project has to contain paths to Securebridge libraries and compiled modules of the bitness matching the "Target Platform" option in the project settings, i.e. if Windows 64-bit is chosen, your project requires the following dependencies:
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Bin\Win64\
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Lib\Win64\
C:\Users\ParMacPC\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge\
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Bin\Win64\
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Lib\Win64\
C:\Users\ParMacPC\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge\
Re: 64 bit?
Hello Stellar:
Here is a screenshot. Those paths are in my Tools:Options:Enviromet Optins:Delphi Options:Library
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Lib\Win64
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Bin\Win64
C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge
But still only the 32 bit version is available. I got it right last year, but had to reinstall but unfortunately i did not document how i did it. I thought the problem would be gone in later versions, but alas no.
https://www.dropbox.com/s/e3i22a8k9wjrf ... r.jpg?dl=0
Here is a screenshot. Those paths are in my Tools:Options:Enviromet Optins:Delphi Options:Library
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Lib\Win64
C:\Program Files (x86)\Devart\SecureBridge for RAD Studio 10.2\Bin\Win64
C:\Users\info\Documents\Devart\UniDAC for RAD Studio 10.2\Demos\TechnologySpecific\SecureBridge
But still only the 32 bit version is available. I got it right last year, but had to reinstall but unfortunately i did not document how i did it. I thought the problem would be gone in later versions, but alas no.
https://www.dropbox.com/s/e3i22a8k9wjrf ... r.jpg?dl=0
Re: 64 bit?
Problem solved after i reinstalled. Perhaps its was the same bug that i found one year ago?
"...Also this is wrong in documentation (on many levels)
5. Compile and install the package.
6. Call the Environment Options dialog from the Tools menu of your IDE, and add the patch to the directory containing the compiled packages to the Library path on the Library tab.
Step 6 must be done first or the package cant be compiled, also "compiled packages" is vague for someone not familiar with tool making, and "the Library tab" is as i just described not correct.
Victor acknowledged the problem and stated he would correct the documentation.
"We will change this information into correct one in the readme.html file."
But what i can se its still the same flawed information. "
viewtopic.php?t=37151
"...Also this is wrong in documentation (on many levels)
5. Compile and install the package.
6. Call the Environment Options dialog from the Tools menu of your IDE, and add the patch to the directory containing the compiled packages to the Library path on the Library tab.
Step 6 must be done first or the package cant be compiled, also "compiled packages" is vague for someone not familiar with tool making, and "the Library tab" is as i just described not correct.
Victor acknowledged the problem and stated he would correct the documentation.
"We will change this information into correct one in the readme.html file."
But what i can se its still the same flawed information. "
viewtopic.php?t=37151