Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
From: Patricia Shanahan <pats@acm.org>
Subject: Re: Exporting symbols from AOO shared libraries
To: dev@openoffice.apache.org
References: 
 <CAJm2B-k8Y9cPFqFCQCTTNotWuZ18mbPNzEzPu_DpOT63W2GsTw@mail.gmail.com>
Message-ID: <57003E76.8020401@acm.org>
Date: Sat, 2 Apr 2016 14:49:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: 
 <CAJm2B-k8Y9cPFqFCQCTTNotWuZ18mbPNzEzPu_DpOT63W2GsTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

A difficult one.

I don't like making things public just to support testing, because later 
on, when someone wants to make changes, it is impossible to tell whether 
they can or not.

In a simpler project, I might suggest doing separate builds for testing, 
but I hesitate to add to the AOO build complexity.

How about a unit test stub class, clearly named as such, wrapping the 
class you want to test and itself exported?

On 4/2/2016 9:44 AM, Damjan Jovanovic wrote:
> Hi
>
> I am trying to add a unit test to Calc, and the C++ class I want to
> test (ScStringUtil) isn't exported from its library (with
> SC_DLLPUBLIC), so my test is failing to link.
>
> Can I export that class? What determines when we can/should?
>
> Thank you
> Damjan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org