Board index » delphi » VCLxx directories?

2006-12-07 07:27:17 PM
delphi17
Hi All,
When one is using one of the international versions of BDS, there are a
VCLUS and a VCLxx on CD4 allowing to switch the whole VCL binaries to
the US or xx versions. Useful when developping a US-only app from a
French BDS, for instance.
But when one is using the US BDS packaging, how does one get the VCLxx
for one of the international versions?
TIA, /Ph.
 

Philippe Auphelle writes:
editions has always confused IDE languages with deployment languages. I
hope CodeGear will fix this.
--
Craig Stuntz [TeamB] ?Vertex Systems Corp. ?Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
Useful articles about InterBase development:
blogs.teamb.com/craigstuntz/category/21.aspx
 

Bummer.
Strange they take care of it one way (I can develop US-VCL apps from a
French BDS IDE, because they stuff the VCLUS dir tree on the
distribution CDs) but not the other way.
Someone somewhere must have assumed that US citizens would never want to
develop applications natively in any language but ENU ;-)
I'm in the process of upgrading our Dx licenses to BDS, and I was
wondering whether we would order US or FR versions.
- We mostly develop native US native apps, but want to be able to
develop French native-apps too.
- We are considering the US IDE because using the US IDE makes it easier
to communicate with support, on newsgroups, etc.
- But the US IDE doesn't give us access to the VCLFR dir tree.
- Add to this that the Small Team license doesn't allow getting one US
and one FR license, and that buying two separate licenses cost an extra
180 euros...
Nick? that is one for the ToDo list!
"Make all VCLxx for the various countries available for download to
Delphi Developers! (and keep them updated and hotfixed, too)"
Thanks for the info, Craig. /Ph.
Craig Stuntz [TeamB] writes: