[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is OCTINTERP_API still relevant?
|
From: |
Jordi Gutiérrez Hermoso |
|
Subject: |
Re: Is OCTINTERP_API still relevant? |
|
Date: |
Wed, 23 Feb 2011 09:48:58 -0600 |
On 23 February 2011 06:05, Benjamin Lindner <address@hidden> wrote:
>> For the record, I still compile octave with MSVC. It is required because
>> it defines what are the exported symbols (MSVC does not auto-export
>> symbols). But besides its use with MSVC, I can (should?) also be
>> used under GCC to defines what are the exported symbols and part
>> of the octave API, by using the visibility attribute.
>
> And since gcc 4.5.0 changed it's behaviour on which-symbols-to-export
> it's even more relevant also for gcc code, so it should be used
> anyway.
What compiler directive or attribute should OCTINTERP_API define for gcc 4.5?
- Jordi G. H.