From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: i686 ld couldn't resolve wglCreateContext from libopengl32.a on x86_64 system
Date: Fri, 03 Mar 2017 01:19:00 -0000 [thread overview]
Message-ID: <e7071e3e-d5ca-f5cb-e0c5-153b3dfdd190@cygwin.com> (raw)
In-Reply-To: <1488500089.994801791@f392.i.mail.ru>
On 2017-03-02 18:14, sorryforaskingthis.bk.ru via cygwin wrote:
>> On 2017-03-02 16:54, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
>>
>> This looks like a snippet of an autoconf AC_CHECK_LIB (or
>> AC_CHECK_FUNCTION) test. Such tests don't work with 32-bit Win32 APIs
>> -- on either Cygwin or MinGW -- because they don't take stdcall into
>> account. You'll need to modify the test to work around that.
>>
>> Also, if you're using Cygwin, do you *really* want to be using Win32
>> OpenGL and not X11?
>>
> Yes, you're right. It's autoconf test and it perfectly passed at 64-bit MinGW
> and 64-bit Cygwin, but not on 32-bit Cygwin.
It would fail on 32-bit MinGW too.
> And I don't understand why you're say that it is related to stdcall, while
> wglCreateContext exposed directly without any @0 @4 etc.
No, it's not, check the implib yourself. You have to use a proper
declaration to link stdcall functions, and the autoconf tests don't do
that. You need to change the test to avoid this; exactly how depends on
the intent of the test.
> Yes, I need to use Win32.
^^^^
> I want to port application that heavily POSIX-dependent, but also want to save
^^^^
> performance as much as possible.
Big difference.
> I think if w32api-runtime package is provided it supposed to work.
Maybe, maybe not. Mixing *NIX and Win32 APIs isn't so simple.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-03-03 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:14 sorryforaskingthis.bk.ru via cygwin
2017-03-03 1:19 ` Yaakov Selkowitz [this message]
2017-03-03 1:57 ` Michael Enright
2017-03-03 13:50 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 22:17 sorryforaskingthis.bk.ru via cygwin
2017-03-02 22:54 ` Yaakov Selkowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7071e3e-d5ca-f5cb-e0c5-153b3dfdd190@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).