On 11/17/09 19:06, Mathias Bauer wrote:
Frank Schoenheit, Sun Microsystems Germany wrote:
Hi Bjoern
- map files
- explicitly setting a compiler flag in the make file
- XX_DLL_EXPORT/XX_DLL_IMPORT/XX_DLL_PRIVATE and friends
However, using the XX_DLL_PRIVATE and friends should be "enough for
e
On 11/19/09 14:45, Eike Rathke wrote:
On Monday, 2009-11-16 15:11:16 +0100, Bjoern Michaelsen wrote:
- map files
AFAIK they are needed because they provide versioning information that
is crucial for the SDK libraries. Stephan Bergmann probably knows all
details.
Yes, the one important differ
Hi Bjoern,
On Monday, 2009-11-16 15:11:16 +0100, Bjoern Michaelsen wrote:
> - map files
AFAIK they are needed because they provide versioning information that
is crucial for the SDK libraries. Stephan Bergmann probably knows all
details.
Eike
--
OOo/SO Calc core developer. Number formatter
Frank Schoenheit, Sun Microsystems Germany wrote:
> Hi Bjoern
>
>> - map files
>> - explicitly setting a compiler flag in the make file
>> - XX_DLL_EXPORT/XX_DLL_IMPORT/XX_DLL_PRIVATE and friends
>>
>> However, using the XX_DLL_PRIVATE and friends should be "enough for
>> everyone", right?
>
>
The only caveat that comes to mind is that you would require a
private/public mechanism of every compiler. That holds true for all the
major platforms, though. For UNO libraries the export of only basically
three symbols (plus a plethora of compiler details) is essential because
there are likel
On Tue, 17 Nov 2009 10:32:21 +0100
"Frank Schoenheit, Sun Microsystems Germany"
wrote:
> At least we'd need a makefile-clause for setting a default, /me
> thinks.
>
> For instance, for libs exporting the usual three UNO entry points
> component_*, I would like to have a "make everything private"
Hi Bjoern
> - map files
> - explicitly setting a compiler flag in the make file
> - XX_DLL_EXPORT/XX_DLL_IMPORT/XX_DLL_PRIVATE and friends
>
> However, using the XX_DLL_PRIVATE and friends should be "enough for
> everyone", right?
At least we'd need a makefile-clause for setting a default, /me t
Hi List,
again some stuff from the Build Environment Effort(1). While figuring
out the way we build libraries with the OpenOffice.org build system it
became apparent that we seem to have way to many redundant ways to set
the visibility of functions. From the top of my head:
- map files
- explicit
