public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: Tatsuro MATSUOKA <matsuoka@nuce.nagoya-u.ac.jp>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: fltk does not work on cygwin version octave-6.4.0
Date: Wed, 22 Jun 2022 21:33:17 +0200	[thread overview]
Message-ID: <e68a3b5b-ea76-1448-9c23-7e7eadbcb6c9@gmail.com> (raw)
In-Reply-To: <1829041618.1259316.1655894266818.JavaMail.yahoo@mail.yahoo.co.jp>

On 22.06.2022 12:37, Tatsuro MATSUOKA wrote:
>> ----- Original Message -----
>> From: "Tatsuro MATSUOKA"
>> To: "Marco Atzeri"; "cygwin
>> Date: 2022/06/22 水 12:53
>> Subject: Re: fltk does not work on cygwin version octave-6.4.0
>>>> ----- Original Message -----
>>>> From: "Marco Atzeri"
>>>> To: "cygwin
>>>> Date: 2022/06/22 水 02:06
>>>> Subject: Re: fltk does not work on cygwin version octave-6.4.0
>>>> On 21.06.2022 07:15, Tatsuro MATSUOKA wrote:
>>>>> fltk does not work on cygwin version octave-6.4.0
>>>>>
>>>>> octave:1> graphics_toolkit fltk
>>>>> octave:2> plot(1:10);
>>>>> Insufficient GL support
>>>>> error: unable to plot due to insufficient OpenGL support
>>>>>
>>>>> plot windows flashes and disappear immediately
>>>>>
>>>>> fltk graphics_toolkit works octave on native windows.

> Is the below related to the issue?
> 
>>> __opengl_info__
> warning: __opengl_info__: can not obtain OpenGL information
> warning: called from
>      __opengl_info__ at line 69 column 5
> 
> Similar behaviors happen qt graphics on octave-7.1.0 on native Windows.
> 
> Tatsuro
> 

Maybe.

On my PC

$ octave

octave:1> __opengl_info__
    version: 4.5.0 - Build 22.20.16.4815
     vendor: Intel
   renderer: Intel(R) UHD Graphics 620
extensions:
   GL_3DFX_texture_compression_FXT1
  .....

Similar to the X log

glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
(II) AIGLX: Testing pixelFormatIndex 1
GL_VERSION:     4.5.0 - Build 22.20.16.4815
GL_VENDOR:      Intel
GL_RENDERER:    Intel(R) UHD Graphics 620
(II) GLX: enabled GLX_SGI_make_current_read
...

You can test the GL behaviour with

$ cygcheck -l mesa-demos | grep bin
/usr/bin/eglinfo
/usr/bin/es2_info
/usr/bin/glinfo
/usr/bin/glxgears
/usr/bin/glxinfo
/usr/bin/wglgears
/usr/bin/wglinfo
/usr/bin/xeglgears
..

Regards
Marco



  reply	other threads:[~2022-06-22 19:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1014671988.1220984.1655788512175.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-06-21  5:15 ` Tatsuro MATSUOKA
2022-06-21  9:44   ` Takashi Yano
2022-06-21 10:48     ` Tatsuro MATSUOKA
2022-06-21 11:18       ` Takashi Yano
2022-06-21 11:25         ` Takashi Yano
2022-06-21 11:31         ` Jon Turney
2022-06-21 17:05   ` Marco Atzeri
2022-06-22  1:49     ` Tatsuro MATSUOKA
2022-06-22  3:53       ` Tatsuro MATSUOKA
2022-06-22 10:37         ` Tatsuro MATSUOKA
2022-06-22 19:33           ` Marco Atzeri [this message]
2022-06-22 23:05             ` Tatsuro MATSUOKA
2022-06-23  1:19               ` Marco Atzeri
2022-06-23  3:18                 ` Tatsuro MATSUOKA
2022-06-26 13:58               ` Jon Turney
2022-06-27  3:23                 ` Tatsuro MATSUOKA

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=e68a3b5b-ea76-1448-9c23-7e7eadbcb6c9@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).