I cannot see this BDERTL dependency with TMS Component Pack v6.9.3.0
Are you 100% sure you are using the latest version.
Yes. The uninstall file unins000.exe has digital timestamp
Monday, June 10, 2013 3:41:38 PM
So, I guess, I cannot have this one wrong ...
Do you see in TMSDXE4.DPROJ in the requires list a reference to BDERTL ? It shouldn't be there. Remove it if it is so on your machine.
Hello Bruno
Well, there is good news and bad news …
BTW I had previously removed all references to BDERTL in TMSDXE4.dpk and TMSDXE4.dproj.
Lets go. I create a new C++builder Project add a form, a button and a TMS TfolderDialog Set Win64 default Platform. Save all the project files.
Then with NOTEPAD open the project.cbproj remove all the references to bdertl by hand save it.
With Msbuild I compile and link. It works, TMS under C++ 64 bits. HOOOAAW
With C++Builder XE4 Update 1, I open the same project that worked with Msbuild, and no matter what I do, I always get and error of “Unable to open file 'BDERTL.A'”.
If I save the project (change the size of the form ), in the project.cbproj a dependency on BDERTL.lib appears under the <PropertyGroup Condition="'$(Cfg_1_Win64)'!=''"> section.
So, TMS does NOT work with C++BuilderXE4, but it DOES work with bcc64 … ;-)
I have no idea from where the problem comes. Neither if it’s TMS or EMBT faults. ( BTW I do not have any problem with other third party components in 64 … )
To finalize, the bad news is: that I will continue to ‘hassle’ TMS to get C++Builder working in 64 bits.
Regards
We have tested this today on XE4 update 1 and can confirm this problem. In XE4 it works fine though.
We'll contact Embarcadero to investigate this.
First feedback from Embarcadero is that it might be an issue with their patch mechanism and the suggestion to install update 1 via the ISO and not the patch. We have not tested/tried this yet though.
Not related to Update 1. Old problem
http://qc.embarcadero.com/wc/qcmain.aspx?d=114447
Work around:
Copy any .a lib to BDERTL.a or create a static lib BDERTL.a with void foo() {} and put it somewhere in the compiler path ex: $(BDSCOMMONDIR)\DCP\Win64 or TMS\Win64
C++Builder XE4 will be happy and can compile and link TMS in 64.
So, let’s wait for next TMS release to see if we get 32 and 64 headers and dcu from the TMS install (Different folders are required ex. BuilderXE4.Win32 and BuilderXE4.Win64)
Thanks and Regards
It's rather wait for a fix from Embarcadero. They are notified.
We got acknowledgement from Embarcadero this is a bug in their Win64 C++ package analysis.
The workaround they propose at this time is to create an empty BDERTL.a file.
So is there a work around ? Maybe I missed a step.< id="adlesse_unifier_magic_element_id" style="display:none;">
1) Add 64bit platform to tmsdXE4.dproj, compile, remove link to bdertl
2) Create static lib bdertl.a
3) Create CPP project with AdvPanel on it, compile 32 bit works
4) Add 64 bit platform, found I had to add "pragma link "shlwapi.a" to get around AdvGrid.o error
5) Compile success
6) Run the application and get "The application was unable to start correctly (0xc000007b)
Any recommended steps that I missed ?
With C++ XE4 Update 1, unless we do this workaround with BDERTL.a, we cannot get this working. It is clear that Update 1 broke something.
With C++ XE4 without update 1, we do not have an issue. We cannot reproduce the problem you mention with shlwapi.a
Yes I get the following error if I don't have the pragma set :-< id="adlesse_unifier_magic_element_id" style="display:none;">
[ilink64 Error] Error: Unresolved external 'StrCmpLogicalW' referenced from C:\USERS\PUBLIC\DOCUMENTS\RAD STUDIO\11.0\DCP\WIN64\TMSDXE4.A|AdvGrid.o
However, I managed to get it to run under CPP 64. I re-checked the project setup and found I hadn't turned "link with runtime packages" to off.
The the pragma and that set it works. WOW.