problem when installing components for both delphi and cppbuilder bds 2006
je...@ironsinc.com
Well, I don't know if I can come up with a solution for this problem
or not, but I have experienced the dreaded "unable to view tool
palette" in cppbuilder when installing a new component for both delphi
and cppbuilder one too many times, so I will give it a shot to
identify or workaround this bug. The INDY 10 set of components is one
example, where you install the components as per guidelines suggested,
everything seems to install correctly, you get the dialog box pop up
saying "installed and registered", etc. ok. Pull up Delphi
personality, everything fine. Pull up Cppbuilder personality, no Indy
tool components. Look into "installed packages", and there sits Indy,
just fine. (I know you can add things via code if you need too, but I
want the tool palette!!! :-) ) I have also experienced this with
other vendors as well, just used Indy as it is popular.
So far I have been able to duplicate the issue, and also I have been
able to fix the issue, but can't get it narrowed down to a sequence of
events to nail it.
example: Create a new package for delphi, add a new component, say
TEDIT, build and install. I have consistently installed it in both
personalities just fine, (both tool palettes show the new component)
I have also consistently installed it, and have it only show up in
Delphi. So logic seems to dictate that there are a set of conditions
that exist causing it to "pass or fail". Played around with linker
options, IDE settings, personalities, etc, but no luck yet.
Anyhow, just throwing this out there. If anybody has any insight
please feel free to comment, especially if you have a fix, because I
can worry about something else then!
-Jerry
je...@ironsinc.com
Success!
I have identified a solution for packages that do not install properly
for both personalities. I tried it on my test package/component, and
it installed fine. Also loaded both personalities separately, wrote
test programs, compiled and ran just fine. In addition, I was able to
successfully install the Indy 10 components using a recent database
snapshot, everything shows up in the tool palette for both delphi and
cppbuilder just fine. I also wrote small test programs, dropped a
TIDSMTP component on the main form, and compiled and ran the programs
successfully. (I didn't actually do anything with it, just wanted to
see if I would error out anywhere, and I didn't)
So, here is the procedure I used:
1) Start up BDS with both personalities (Delphi, cppbuilder) loaded.
2) Create a new package project for Delphi Win 32. Add a new VCL
component, ie TEdit.
3) Compile, then install the package. Save project and exit BDS.
4) Start up BDS with both personalities again. Open up the package
project, change the linker options
to "Generate all C++ Builder Files".
5) Compile the project, BUT DO NOT INSTALL IT. Save project and exit
BDS. If you install it, it WILL NOT show up in the CPPBuilder tool
palette correctly. Nice!
You should now have both personalities showing the tool palette with
the installed package/component. Not sure how much this next part
matters, but the BPL files I let get compiled in the "my documents"
default location. The specific package and source code was located in
its own folder that I created.
OK, now specific to the Indy packages. You follow the exact same
install instructions that were given, except follow the guidelines
above. Inotherwords:
- start up BDS with both personalities
1) Open and compile .dpk files in the following order:
IndySystemX0.dpk (in Lib\System)
IndyCoreX0.dpk (in Lib\Core)
IndyProtocolsX0.dpk (in Lib\Protocols)
2) Now open these .dpk files and click install in the following order:
dclIndyCoreX0.dpk (in Lib\Core)
dclIndyProtocolsX0.dpk (in Lib\Protocols)
- Quit BDS and restart (this may not even be necessary, but it's what
I did, and it's too late for me to keep playing)
Now, for the 5 files you worked with above, in the same order, change
the linker options to "generate c++builder files", and Compile, BUT DO
NOT INSTALL.
I'm not sure how many people this will actually help, as I'm using BDS
2006, and 2007 stuff is out, maybe even 2008 due soon if not already.
But at least I don't have to deal with reinstalling packages specific
to the personality, or using components via code.
Time for a beer I think,
-Jerry Irons