Re: [AD] _al_file_size removal |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Thursday 15 June 2006 01:10, Elias Pschernig wrote:
> I had assumed, since it can only be called internally, there should be
> no real problem.
Because it's an exported symbol, Windows will need to resolve it when the
program loads, regardless if the program itself calls it or not. The 4.2.0
import lib says the function is there, and loading a lib that doesn't have it
will cause a load-time error.
For 4.3, it may be good to have all symbols hidden by default and marking the
public API/proper symbols as exported (both MSVC and current MinGW can do
this, and GCC 4 can do this for other platforms as well).