Board index » kylix » Kylix External Dependencies

Kylix External Dependencies


2003-08-23 03:20:11 AM
kylix2
This is just a quick question, but is it possible to bound the external qt
dependancies needed for a kylix appliction so that you only need to deploy a
single file, like for many delphi applications? and if not, why not?
Kind regards,
Sigmund
 
 

Re:Kylix External Dependencies

Dr Sigmund Mohammad wrote:
Quote
This is just a quick question, but is it possible to bound the
external qt dependancies needed for a kylix appliction so that you
only need to deploy a single file, like for many delphi applications?
It is possible but not that way Delphi does. You can make a self
extractor.
Quote
and if not, why not?
The reason is the differences in the ABIs (Application Binary
Interface). g++ compiled functions have different export names than
Kylix's. Furthermore the classes are not compatible. So you need a
wrapper and this wrapper is a gcc compiled shared object (libqtintf.so,
libborqt.so). Kylix applications call the wrapper functions that call
the Qt methods.
--
Regards
Andreas Hausladen
(www.kylix-patch.de.vu unofficial VisualCLX patches)
 

Re:Kylix External Dependencies

Dr Sigmund Mohammad wrote:
Quote
But why are Kylix's binarys different?
They aren't.
Quote
why were they designed to require such a wrapper?
You can write Kylix applications without a wrapper. But if your program
uses any VisualCLX component the wrapper .so is necessary. As I've
wrote VisualCLX application are based on Qt 2.3. And Qt is a C++
class/component library. Both Kylix compilers bc++ and dcc cannot link
against a C++ shared object.
--
Regards
Andreas Hausladen
(www.kylix-patch.de.vu unofficial VisualCLX patches)
 

{smallsort}