Hi all,
I am working on trying to revive PyKDE4 as PyKF5 and more [1]. The procedure is:
1. create SIP file from the relevant KF5 .h file(s)
2. run the SIP compiler to produce the actual binding C++ code
3. compile the binding C++ code
4. link the result into a .so file against the relevant KF5 l
Shaheed Haque wrote:
> I'm hoping that CMake could
> help, but in the worst case, it is trivial to specify this amount of data
> by hand on a platform basis if needed.
To keep this mailing list in the loop, I posted a CMake based (portable to
differing library suffixes, precise in terms of what
Hi David,
On 23 April 2016 at 09:56, David Faure wrote:
> Shaheed !!!
> Long time no see ;)
>
Indeed, I think it is about 10 years since I last did anything here!
> On Wednesday 20 April 2016 19:48:30 Shaheed Haque wrote:
> > The whole point of what I am doing is to automate as much as possib
Shaheed !!!
Long time no see ;)
On Wednesday 20 April 2016 19:48:30 Shaheed Haque wrote:
> The whole point of what I am doing is to automate as much as possible
> of steps 1-4, and this question centres on step 4. How can I automate
> identifying the correct KF5 library .so file? For example, on m
Shaheed Haque wrote:
> [ resend now I am subscribed, apologies for any dupes ]
>
> Hi all,
>
> I am working on trying to revive PyKDE4 as PyKF5 and more [1]. The
> procedure is:
>
> 1. create SIP file from the relevant KF5 .h file(s)
> 2. run the SIP compiler to produce the actual binding C++ c
Shaheed Haque wrote:
> [ resend now I am subscribed, apologies for any dupes ]
>
> Hi all,
>
> I am working on trying to revive PyKDE4 as PyKF5 and more [1]. The
> procedure is:
>
> 1. create SIP file from the relevant KF5 .h file(s)
> 2. run the SIP compiler to produce the actual binding C++ c
Shaheed Haque wrote:
> [ resend now I am subscribed, apologies for any dupes ]
>
> Hi all,
>
> I am working on trying to revive PyKDE4 as PyKF5 and more [1]. The
> procedure is:
>
> 1. create SIP file from the relevant KF5 .h file(s)
> 2. run the SIP compiler to produce the actual binding C++ c
[ resend now I am subscribed, apologies for any dupes ]
Hi all,
I am working on trying to revive PyKDE4 as PyKF5 and more [1]. The procedure is:
1. create SIP file from the relevant KF5 .h file(s)
2. run the SIP compiler to produce the actual binding C++ code
3. compile the binding C++ code
4. l
