Dear mentors,
I am looking for a sponsor for my package "libqtintf4".
* Package name: libqtintf4
Version : 1.72Qt4.5.2-1
Upstream Author : (C) 2009 Jan Van Hijfte
* URL :
http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html
* License : GPL
Section
On 2009-11-07, Matthias Klumpp wrote:
> http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html
> * License : GPL
Looks like lgpl
> It builds these binary packages:
> libqt4intf-dev - Qt4 interface bindings
> libqt4intf5 - Qt4 interface bindings
For which language?
> - dget
> http:
On Sat, 7 Nov 2009 11:59:10 + (UTC), Sune Vuorela
wrote:
> Looks like lgpl
Oops, misstyped! The debian/copyright file is correct
>> It builds these binary packages:
>> libqt4intf-dev - Qt4 interface bindings
>> libqt4intf5 - Qt4 interface bindings
>
> For which language?
For Pascal, but a
On Sat, Nov 7, 2009 at 8:37 PM, Matthias Klumpp wrote:
>> I'm not sure I like this way of creating qt bindings, I_think doing what
>> the kdebindigs people, by using the 'smoke' intermediate library is a
>> better way ahead.
> The libqt4intf is also available for Windows and MacOS-X. I dont't thi
Hello again!
I got the following reply on your comments for the libqt4intf interface
library from Den Jean, a Qt4-Intf developer:
Original Message
From: Den Jean
To: Items specific to the Qt widget set
On Sunday 8 November 2009 17:22:36 Matthias Klumpp wrote:
> Off-topic but
Hello again!
I got this reply from Den Jean about the sources as statement:
[...]
Makefiles just serve to finally create calls to gcc,
these calls I wrote by hand (there was no qmake in qt2)
to more easily configure which Qt to use on the system.
- 2 different Qt's on a s
On 2009-11-10, Matthias Klumpp wrote:
> Makefiles just serve to finally create calls to gcc,
And I think the way the gcc calls are made requires a amazing amount of
RAM for no apparant reason.
> these calls I wrote by hand (there was no qmake in qt2)
> to more easily configure which Qt to use o
On Wed, 11 Nov 2009 00:15:18 + (UTC), Sune Vuorela
wrote:
> [...]
>
> I haven't gotten to the packaging yet, because there is two things from
> upstream that *needs* to be fixed.
> 1) The moc gerenated files *needs* to be generated on build, else the
> build might break on each new qt versio
Dear mentors,
I am looking for a sponsor for my package "libqtintf4".
* Package name: libqtintf4
Version : 1.72Qt4.5.2-1
Upstream Author : (C) 2009 Jan Van Hijfte
* URL :
http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html
* License : GPL
Section
On 2009-12-18, Matthias Klumpp wrote:
> The package is lintian-clean. There were some concerns about the
> build-script, but because it's a really small lib there should be no
> problem in building this.
The way it is built, it takes around 1G of memory to build. This *needs*
to be fixed. it mig
Hello again!
After some work with upstream, all problems seem to be fixed now.
The project contains a qmake-file, moc-files are generated automatically
and buildscript fails on error.
If upstream publishes the qmake-version of libqt4intf in a tarball with
upstream-version in name I will fix the wat
Hello again!
After some work with upstream, all problems seem to be fixed now.
The project contains a qmake-file, moc-files are generated automatically
and buildscript fails on error.
If upstream publishes the qmake-version of libqt4intf in a tarball with
upstream-version in name I will fix the wat
12 matches
Mail list logo
