On Wed, 10 Feb 2010, Szak�ts Viktor wrote:
Hi,
> >> Isn't it a solution if we move HB_LIBLOAD() to a separate
> >> .c file along with above trigger code, and in this way,
> >> if an executable uses this functionality, above stub is
> >> always included?
> > No because it will disable autoexport functionality in MinGW
> > builds.
> Hm, even if it's not linked, just present in the static lib?
Are you planing to remove HB_LIBLOAD()/HB_LIBFREE() from harbour*.dll?
If yes then it can be done in such case.
> That could have been hugely elegant, I find the switch not
> very much so :(
OK, I'll document:
#pragma begindump
#include "hbapi.h"
HB_EXPORT_ATTR PHB_FUNC dll_hb_vmProcAddress( const char * szFuncName )
{
return hb_vmProcAddress( szFuncName );
}
#pragma enddump
best regards,
Przemek
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
