10 Feb
2014
10 Feb
'14
4:35 p.m.
Any other methods?
You can send a list?
No, because each time I copy what you did in your patch to add
Q_EXPORT to a different location, yet another new 'undefined
symbols' message appears. The messages do not all appear at the
same time in one nice dump.
Reversing commit 2ee14b64 resolves the problem.
Darrell
10 Feb
10 Feb
4:47 p.m.
New subject: [trinity-devel] undefined symbols in all builds
On 02/10/2014 10:35 AM, Darrell Anderson wrote:
No, because each time I copy what you did in your
patch to add
Q_EXPORT to a different location, yet another new 'undefined
symbols' message appears. The messages do not all appear at the
same time in one nice dump.
Reversing commit 2ee14b64 resolves the problem.
Darrell
Can I pose a question?
Why are we looking to add Q_EXPORT calls, and we are we making commits
containing them until they are tested?
--
David C. Rankin, J.D.,P.E.
4:57 p.m.
New subject: [trinity-devel] undefined symbols in all builds
Dne po 10. února 2014 David C. Rankin napsal(a):
On 02/10/2014 10:35 AM, Darrell Anderson wrote:
It did not change Q_EXPORT, but the libraries libtqteditor,
libtqtdesignercore and libtqassistantclient were built as static, whereas
now they are by default built as shared.
--
Slavek
No, because each time I copy what you did in your
patch to add
Q_EXPORT to a different location, yet another new 'undefined
symbols' message appears. The messages do not all appear at the
same time in one nice dump.
Reversing commit 2ee14b64 resolves the problem.
Darrell
Can I pose a question?
Why are we looking to add Q_EXPORT calls, and we are we making
commits containing them until they are tested?
5:04 p.m.
New subject: [trinity-devel] undefined symbols in all builds
On 02/10/2014 10:57 AM, Slávek Banko wrote:
It did not change Q_EXPORT, but the libraries
libtqteditor,
libtqtdesignercore and libtqassistantclient were built as static, whereas
now they are by default built as shared.
Good. Moving away from the static libraries seem like the way to go. Could
Darrell's issue be that he still has some components of TDE built that are
looking for the static libs when now only the shared libs exist?
I bet that is it...
In my build run I kicked off last night, (and restarted this am due to htdig),
is now through the 33rd package (tdeedu) and I do not see any of the output
Darrell is talking about.
However, I did see that kind of output when my build scripts were stripping the
static libs.
--
David C. Rankin, J.D.,P.E.
4016
days inactive
4016
days old
3 comments
3 participants
participants (3)
-
Darrell Anderson -
David C. Rankin -
Slávek Banko