Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libiconv issues. #19

Open
Blady-Com opened this issue Jun 10, 2024 · 2 comments
Open

Libiconv issues. #19

Blady-Com opened this issue Jun 10, 2024 · 2 comments

Comments

@Blady-Com
Copy link

Some Libiconv implementions define symbols such as iconv_open whereas others define libiconv_open.
Currently GNATColl-iconv use iconv_open style in binding support, for instance:

void *gnatcoll_iconv_open(char *tocode, char *fromcode){
  iconv_t res = iconv_open(tocode, fromcode);
  return (res == (iconv_t) -1) ? NULL : res;
}

As it was formerly explained in documentation:

If your application depends on having a working libiconv, you can specify –with-iconv or –with-iconv=PATH to GNATCOLL’s configure.

But configure is no more present.

How can I use Libiconv library with libiconv_open style?

@Nikokrock
Copy link
Collaborator

Hi,

On which OS (and distribution) are you ? Which libiconv version are you trying to use ?

Thanks in advance

@Blady-Com
Copy link
Author

Hi, my configuration: macOS 13.6, Xcode 14.3, GNAT FSF 13.2 (from Alire).
libiconv-1.17 comes from GTK-OSX distribution.
I link GNATColl against this version to be compatible with GTKAda which is linked against GTK-OSX.
NB: it isn't the native macOS libiconv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants