Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8726753
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T08:18:41+00:00 2026-06-13T08:18:41+00:00

I am writing a cross-platform OpenGL function loading library. On Windows, the compiler (oddly

  • 0

I am writing a cross-platform OpenGL function loading library. On Windows, the compiler (oddly enough, both VS and GCC) seems fine with implicitly converting one kind of function pointer (the return type from wglGetProcAddress being a void(*)()) into another type of function pointer.

GCC on Linux however is not. glXGetProcAddress will return a void(*)(), but it will always issue a warning about it. And since OpenGL has literally thousands of these things, it adds up to a giant diagnostic spew that’s entirely irrelevant.

Is there some way to disable this particular warning? Either with a #pragma or some way of rearranging the code so GCC shuts up? I tried the whole #pragma diagnostic ignore -Wblahblah, but I couldn’t find a “blahblah” that matched the warning I was getting.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T08:18:41+00:00Added an answer on June 13, 2026 at 8:18 am

    I’m pretty sure you’re supposed to use the provided macros to get the correct types out. For example, taken from the gl3w OpenGL extension loader (you have to run the python script to get it to generate code like this), it has lines that look like:

    gl3wBindImageTexture = (PFNGLBINDIMAGETEXTUREPROC)get_proc("glBindImageTexture");
    

    That weird PFNGLBINDIMAGETEXTUREPROC in the middle is a macro for the correct function type of the glBindImageTexture function (you can see its name is actually Pointer FunctioN GLBINDIMAGETEXTURE PROC).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems ANSI C 89 is the best choise for writing a cross-platform library
I am writing a cross-platform library which, among other things, provides a socket interface,
I am writing a cross-platform compatible function in C++ that creates directories based on
I'm considering writing a cross-platform desktop app, initially for Mac/Windows, but eventually for Linux
What are the best practices on writing a cross platform library in C++? My
So I am writing a cross-platform (so far plans for Windows and Ubuntu) application
I'm writing an cross-platform renderer. I want to use it on Windows, Linux, Android,
I am writing a cross platform shared library ( .so in linux and .dll
I'm writing a cross-platform code, which should compile at linux, windows, Mac OS. On
I'm writing a library that is supposed to be cross-platform, but it needs different

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.