Displaying 2 results from an estimated 2 matches for "c_keyring_macos_set".
Did you mean:
c_keyring_macos_get
2017 Mar 07
2
Platform dependent native routine registration
...et: no visible binding for global variable
?c_keyring_macos_get?
[...]
Undefined global functions or variables:
c_keyring_macos_create c_keyring_macos_delete
c_keyring_macos_delete_keyring c_keyring_macos_get
c_keyring_macos_list c_keyring_macos_list_keyring
c_keyring_macos_lock_keyring c_keyring_macos_set
c_keyring_macos_unlock_keyring
If possible, I would like to avoid defining dummy functions for all functions
that are not available on a certain platform, simply because I have a lot of
them. Is it possible?
Thanks,
Gabor
2017 Mar 07
0
Platform dependent native routine registration
...ding for global variable
| ?c_keyring_macos_get?
|
| [...]
|
| Undefined global functions or variables:
| c_keyring_macos_create c_keyring_macos_delete
| c_keyring_macos_delete_keyring c_keyring_macos_get
| c_keyring_macos_list c_keyring_macos_list_keyring
| c_keyring_macos_lock_keyring c_keyring_macos_set
| c_keyring_macos_unlock_keyring
|
| If possible, I would like to avoid defining dummy functions for all functions
| that are not available on a certain platform, simply because I have a lot of
| them. Is it possible?
Could you resort to preprocessor conditioning to only compile the code
releva...