In an effort to resolve bug report 817 I converted qca to tqca. That small package never got converted to Trinity TQt.
One stumbling block. I am unable to figure out how to force the configure script to add /usr/include/tqt to the -I include list. If I could get past that then I suspect any remaining build problems will be superficial. The build log output is clear that the problem is not finding the tqt headers.
To anybody with those skills, here is the link to the converted files:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca/
The entire gzipped source tree is here:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca.tar.gz
Thanks!
Darrell
In an effort to resolve bug report 817 I converted qca to tqca. That small package never got converted to Trinity TQt.
One stumbling block. I am unable to figure out how to force the configure script to add /usr/include/tqt to the -I include list. If I could get past that then I suspect any remaining build problems will be superficial. The build log output is clear that the problem is not finding the tqt headers.
To anybody with those skills, here is the link to the converted files:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca/
The entire gzipped source tree is here:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca.tar.gz
Anybody?
Darrell
On 03/24/2012 03:37 PM, Darrell Anderson wrote:
Anybody?
Darrell
We need a list of members and skills. Eg:
Member Skills David BASH, Arch Build Serghei CMake Darrell BASH, c++, Slack Build <needed> autoconf, Makefiles, configure scripts
That way we would at least have a reference of who has the skills to help with what. There is no question that each of us, given enough time, could solve each of the problems presented. The question is one of efficiency. If it takes Darrell 10 days to search and learn the intricacies of configure tests to solve the include problem that someone else could solve in 5 minutes, then that is a wasted 9 days 23 hours and 55 minutes that could have been spent advancing other issues with R14. Knowing who to go to would go a long way to eliminating this type of issue.
We need a list of members and skills. Eg:
Member Skills David BASH, Arch Build Serghei CMake Darrell BASH, c++, Slack Build <needed> autoconf, Makefiles, configure scripts
That way we would at least have a reference of who has the skills to help with what. There is no question that each of us, given enough time, could solve each of the problems presented. The question is one of efficiency. If it takes Darrell 10 days to search and learn the intricacies of configure tests to solve the include problem that someone else could solve in 5 minutes, then that is a wasted 9 days 23 hours and 55 minutes that could have been spent advancing other issues with R14. Knowing who to go to would go a long way to eliminating this type of issue.
I'm no C++ expert! :) I'm just now teaching myself C++. Newbie! Except for some tip-of-the-iceberg basics, I get lost walking through the code. Even if I understood C++, I don't understand how the (T)Qt-T/KDE environment intertwines together.
I'll volunteer Calvin as a C++ person. He'll have to vouch for his skill level, but he's 10x better than anything I can dream of.
Tim is a C++ Gandalf White Wizard.
There are many others lurking in this list but I don't know their skill sets.
As you noted, many of the problems we encounter likely are trivial to an experienced person. Five minutes later the problem is solved --- and everybody learns too. :)
I'm not sure we need a list. If people are subscribing to this list then hopefully the experts step forward and help. :)
With respect to the tqca package, I need help ensuring the tqt headers are found. I'll keep doing whatever grunt work is required beyond that. I tried copying how tqca-tls works, but with no success. I tried modifying the build flags too.
Darrell
I'll take bait but if Tim is the white wizard then I am samwise gamgee.
Ill vouch myself at C++. My interests in Trinity are user experience and interface design and efficiency :-) so any questions regarding that I'd love to field. Application wise I'm interest in maintaining and enhancing Kate and Kicker so those should also be sent my way. I am also interested in adding advanced features into kwin. I have knowledge of the first two codebases and cursory knowledge of kwin. you should put me down for those.
Also all bugs on kicker and Kate can be assigned to me:)
Calvin On Mar 24, 2012 7:57 PM, "Darrell Anderson" humanreadable@yahoo.com wrote:
We need a list of members and skills. Eg:
Member Skills David BASH, Arch Build Serghei CMake Darrell BASH, c++, Slack Build <needed> autoconf, Makefiles, configure scripts
That way we would at least have a reference of who has the skills to help with what. There is no question that each of us, given
enough
time, could solve each of the problems presented. The question is one of efficiency. If it takes Darrell 10 days to search and learn the
intricacies of
configure tests to solve the include problem that someone else could
solve in 5
minutes, then that is a wasted 9 days 23 hours and 55 minutes that could
have been
spent advancing other issues with R14. Knowing who to go to would go a
long way to
eliminating this type of issue.
I'm no C++ expert! :) I'm just now teaching myself C++. Newbie! Except for some tip-of-the-iceberg basics, I get lost walking through the code. Even if I understood C++, I don't understand how the (T)Qt-T/KDE environment intertwines together.
I'll volunteer Calvin as a C++ person. He'll have to vouch for his skill level, but he's 10x better than anything I can dream of.
Tim is a C++ Gandalf White Wizard.
There are many others lurking in this list but I don't know their skill sets.
As you noted, many of the problems we encounter likely are trivial to an experienced person. Five minutes later the problem is solved --- and everybody learns too. :)
I'm not sure we need a list. If people are subscribing to this list then hopefully the experts step forward and help. :)
With respect to the tqca package, I need help ensuring the tqt headers are found. I'll keep doing whatever grunt work is required beyond that. I tried copying how tqca-tls works, but with no success. I tried modifying the build flags too.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le 20/03/2012 03:48, Darrell Anderson a écrit :
In an effort to resolve bug report 817 I converted qca to tqca. That small package never got converted to Trinity TQt.
One stumbling block. I am unable to figure out how to force the configure script to add /usr/include/tqt to the -I include list. If I could get past that then I suspect any remaining build problems will be superficial. The build log output is clear that the problem is not finding the tqt headers.
Hello, in file "qca.pro", add the following line : INCLUDEPATH += /usr/include/tqt just below the existing(s) "INCLUDEPATH" ...
BTW, I've made a patch to allow tqca-tls building with TQT3 (instead of QT3). It does not require any 'tqca' package. The patch is here: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/dependencies/tq...
I encourage you (and all others packagers) to browse the GIT repository 'tde-packaging', but in others distros directories, especially Ubuntu, which I consider being the reference distro (because it is maintained by Tim). When I get a build failure, I go there, and 99% of the time, I find the solution.
Francois
In an effort to resolve bug report 817 I converted qca
to tqca. That small package never got converted to Trinity TQt.
One stumbling block. I am unable to figure out how to
force the configure script to add /usr/include/tqt to the -I include list. If I could get past that then I suspect any remaining build problems will be superficial. The build log output is clear that the problem is not finding the tqt headers.
Hello, in file "qca.pro", add the following line : INCLUDEPATH += /usr/include/tqt just below the existing(s) "INCLUDEPATH" ...
Thank you much Francois! With that help I was able to finish the migration. I now can offer the team a tqca package. :)
Yet based upon your statement about your patch, has my time been wasted?
BTW, I've made a patch to allow tqca-tls building with TQT3 (instead of QT3). It does not require any 'tqca' package. The patch is here: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/dependencies/tq...
I don't pretend to understand the relationship of the original qca and qca-tls package, what other packages depended upon those two packages, or why qca never was converted to tqca. There are no change logs or records of these decisions. Perhaps converting qca was overlooked, or, is not needed. I am willing to update the wiki if only I knew what was going on and what to write. The lack of active participation in this list of late tends to leave one feeling like a mushroom --- in the dark.
I encourage you (and all others packagers) to browse the GIT repository 'tde-packaging', but in others distros directories, especially Ubuntu, which I consider being the reference distro (because it is maintained by Tim). When I get a build failure, I go there, and 99% of the time, I find the solution.
I am familiar with Tim's build scripts and I visit them often too. Although lately, I would not say I have a 99% success rate. Seems several build failures have slipped back into the fold with nobody offering solutions or help.
Thanks much for helping with such a simple fix!
Should the team want a tqca package I have the sources and basic build script ready to go.
Darrell
-
Calvin Morrison -
Darrell Anderson -
David C. Rankin -
Francois Andriot