WIN32: fix calling conventions for 32-bit builds

On 32-bit Windows Intel builds the __cdecl and __stdcall calling
conventions are different so labeling the functions that are
exported or assigned to function pointers matters.

Change-Id: I03b6f34baeb9ffb2e683fd979f12f27a5078a4da
This commit is contained in:
Jeffrey Altman
2019-01-08 12:58:50 -05:00
parent dcfcdd00d8
commit 387684aa93
21 changed files with 30 additions and 30 deletions

View File

@@ -1,5 +1,5 @@
/*
* Copyright (c) 2018, AuriStor, Inc.
* Copyright (c) 2018-2019, AuriStor, Inc.
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
@@ -261,7 +261,7 @@ kadm5_hook_plugin_load(krb5_context context,
size_t *num_hooks,
const kadm5_hook_ftable *const **hooks);
static uintptr_t
static uintptr_t KRB5_LIB_CALL
sample_hook_get_instance(const char *libname)
{
if (strcmp(libname, "kadm5") == 0)