Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i am writting a delphi ide expert, with some third party dependencies (visual controls), my question is when this expert will be installed in a target machine , this pc will be requires have installed these third party components too? or the componentes are embeded inside of the bpl generated?
About BPL experts:
If you can avoid linking to the design-time versions of the 3rd party controls, stick to runtime BPL’s only, you can legally ship those with your expert as your expert.
Unfortunately I can’t say you can safely ship them because you’re dealing with other Delphi developers: they might have the same 3rd party packages but in a different version! With a normal application you can simply install your version of BPL’s to your application’s directory, but this is not going to work for a Delphi IDE because the the application is the IDE: the IDE is the one loading and linking the BPL’s, and it can’t load two versions of the same BPL. And you can’t replace your user’s version because they need to keep the version they licensed, not even if your version is newer!
The solution: DLL experts:
One possible solution is to compile your expert as a DLL, not as a package, and statically link all dependencies. That way you’re no longer dependent on your user’s version of the 3rd party controls.