Are there any plans to support the QT libs anytime soon? I asked this about a year ago and there weren't any plans to do so because they are written in C++ and not C (like GTK). Has anything changed??
- matt

Mailing lists / fpc-pascal / 2002-04
16 messages · 6 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Are there any plans to support the QT libs anytime soon? I asked this about a year ago and there weren't any plans to do so because they are written in C++ and not C (like GTK). Has anything changed??
- matt
Are there any plans to support the QT libs anytime soon? I asked this about a year ago and there weren't any plans to do so because they are written in C++ and not C (like GTK). Has anything changed??
Afaik they are still written in C++ ( :-) )
Are there any plans to support the QT libs anytime soon? I asked this about a year ago…
Are there any plans to support the QT libs anytime soon? I asked this about a year ago and there weren't any plans to do so because they are written in C++ and not C (like GTK). Has anything changed??
No. What could be done, however, is to use the qtintf library that comes with Kylix; it is a C wrapper around the QT library, and could be used by FPC.
Maybe Qt 3 now also has a C wrapper natively, KDE 3 has one, so I suppose that a QT version would also exist.
Michael.
We would force GPL on our users that way.
Maybe Qt 3 now also has a C wrapper natively, KDE 3 has one, so I suppose that a QT version would also exist.
That would be better, since we could argue that QT is a sys library. (in all major distro's)
Hello
I'm Christophe a french Object Pascal developper.
I'm writing a wrapper for Sablotron named Sablopas. I've just release the 0.5. The current version compiles with Free Pascal for Windows, Kylix and Delphi. Sablopas is Open Source.
http://www.tekool.com/sablopas
I'm currently porting to Free Pascal for Linux. I can compile, link libraries and run the demo but only in a strange way :
1/ I use the -Xt switch and I don't know what it is. I've forgot where I've found it. It is the only way for linker to link Sablotron and Expat.
2/ My executable is now 1.2Mb . Under Windows it's 90Kb.
Configuration used :
I've used declarations like : procedure procname;cdecl; external SAB_LIB;I've declared dlopen and dlclose the same way. I use them to load and unload Expat in the initialization / finalization sections of the first unit load.
I use the {$LINKLIB} directive for Expat and the c library.
I'm a newbie in loading libraries with FPC under Linux. I haven't found a libc unit like in the CLX. I can provide the Sablopas 0.6 beta if need.
Thanks.
Christophe
That would be better, since we could argue that QT is a sys library. (in all major distro's)
Does it mean that if you are writing a wrapper under GPL upon a sys library you can
let the user choose another license ? Do you think Sablotron can be viewed like a sys
library. It is only a library and it is used by Apache, Python and several others software.
I can release Sablopas under dual license to include it under GPL with Free Pascal
if some of you think it will be useful.
Christophe
As far as binding the users to the GPL, who cares? Besides, they would only be bound to it if they develop with QT. If they don't like the GPL then they can either make a new lib for it that isn't bound under GPL -or- they can simply use GTK.
Personally.. I just like QT better. :-)
How exactly could I go about using that Kylix lib?
- Matt
Hello I'm Christophe a french Object Pascal developper. I'm writing a wrapper for…
It means 'link statically' - the linker will use static libraries. I just discovered that this is not documented :/
2/ My executable is now 1.2Mb . Under Windows it's 90Kb.
This is because you link statically: All libraries are in the executable!
But then expat will already be linked in and there is no need to reload them with dlopen/dlclose ?
Michael.
As far as binding the users to the GPL, who cares? Besides, they would only be bound to…
In short:
1. install Kylix open edition.
2. Get the qtintf.pas file from source/clx, compile, and use :)
Michael.
Then I would have to recompile and enable Linux compability :-)
Isn't there a way to get it from sourceforge?
Then I would have to recompile and enable Linux compability :-) Isn't there a way to get it from sourceforge?
If it's part of the FreeCLX distro, then it will be in the FreeCLX CVS can certainly get the Libraries needed, but as
to whether you can get the pas files - Well I couldn't see them after a quick browse.
Matt
freeclx/clx/Qt.pas is the pascal interface file.
freeclx/qt contains all that is needed to build libqtintf
Michael.
Isn't there a way to get it from sourceforge?
Hello,
First I'm sorry for this announce in a thread on QT. I push reply without changing the subject.
It means 'link statically' - the linker will use static libraries. I just discovered that this is not documented :/
Why when I don't use it the linker fails ?
> 2/ My executable is now 1.2Mb . Under Windows it's 90Kb. This is because you link statically: All libraries are in the
executable!
How can I do it in a different way ? Is smartlinking is candidate for ? How can I include only the symbols I used ?
But then expat will already be linked in and there is no need to reload them with dlopen/dlclose ?
Yes I know that. In fact I've solved a bug with that technique under Kylix. Under Kylix
I must load Expat like this in the initialization function otherwise everthing fails.
Thanks a lot
Do you have all the dynamic libraries installed ?
(.so files of all libs must be present)
First link dynamically. This will drastically reduce the size of the executable.
But it IS linked in already since you use -Xt !!
Michael.
Thanks, Michael.
I will try to link dynamically this afternoon.
Bye
Christophe