trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] undefined symbols in all builds

From: "David C. Rankin" <drankinatty@...>
Date: Mon, 10 Feb 2014 10:47:49 -0600
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.