From aurelien.larcher at gmail.com  Sun Nov  1 13:10:34 2026
From: aurelien.larcher at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Larcher?=)
Date: Sun, 1 Nov 2026 14:10:34 +0100
Subject: [oi-dev] tips for building a Qt6 extension?
In-Reply-To: <fa00de56-408f-09d5-019f-ce87072d0dc6@ndsu.edu>
References: <924b035f-bda5-6ae5-ef0e-d05a08de7aec@ndsu.edu>
	<CAHMq6q3AvQDBbSUrG4EPWP58BWoTWo8ju1ggKQXRrGDdOsAx-A@mail.gmail.com>
	<fa00de56-408f-09d5-019f-ce87072d0dc6@ndsu.edu>
Message-ID: <CAHMq6q2CjAZ3vqekB8bLY5dPbpCOMvE=em+CgEmEUE6nb-jD0A@mail.gmail.com>

Do not hesitate to reach out if you struggle with C++ compilation errors.

Cheers

Aur?lien

Le vendredi 30 octobre 2026, Tim Mooney via oi-dev <oi-dev at openindiana.org>
a ?crit :

> In regard to: Re: [oi-dev] tips for building a Qt6 extension?, Aur?lien...:
>
> the release notes specify that C++20 is required to build QtWebEngine, the
>> features of which at the time of the release may have been better
>> supported
>> by Clang.
>> GCC 10 did not provide full support for consteval and improved template
>> deduction.
>> Any GCC >= 12 is probably suitable, and GCC 13 definitely is.
>> If you insist on Clang, any >= 18 will probably do the job and as long as
>> the same libstdc++ it should be fine.
>>
>> Howeber I would stick to the system GCC if I were you.
>> Given that GCC is more permissive and more forgiving with template
>> deduction, it should OK.
>>
>
> Thanks Aur?lien!
>
> You're definitely more knowledgeable about the C++ landscape than I am.
> What you're saying makes sense and sticking with gcc makes things easier
> for sure.
>
> After getting a couple of the other prereqs packaged and installed, I have
> made some progress, but it has been slow.  There are lots and lots of
> places in the cmake config that do checks like
>
> if (LINUX)
>         ... do a bunch of stuff
> endif()
>
> and I'm having to find all of those and either lie that OI is Linux or
> attempt other adjustments.
>
> Thanks again,
>
> Tim
>
> Le mardi 27 octobre 2026, Tim Mooney via oi-dev <oi-dev at openindiana.org> a
>> ?crit :
>>
>>
>>> All-
>>>
>>> Some software I'm experimenting with needs Qt WebEngineWidgets,
>>>
>>>         https://doc-snapshots.qt.io/qtwebengine/qtwebengine-platform
>>> -notes.html
>>>
>>> That's not part of OI's Qt6 build.  That's fine, it looks like it should
>>> be built (and if relevant, packaged) separately.
>>>
>>> I've never built a Qt extension, though, and this one specifically says
>>> it can't be built with GNU C/C++, it requires Clang.
>>>
>>> I'm not asking anyone to build and package this, but I'm wondering if
>>> anyone has any suggestions for building *any* Qt(6) extension with Clang?
>>> I'm pretty familiar with gcc, but I have next to no experience with
>>> Clang.
>>>
>>> It looks like OI's qtcreator package uses g++ but also requires Clang?
>>> Would that be the best option for an example, or is there something
>>> better?
>>>
>>> Thanks,
>>>
>>> Tim
>>> --
>>> Tim Mooney
>>> Tim.Mooney at ndsu.edu
>>> Enterprise Computing & Infrastructure /
>>> Division of Information Technology    /                701-231-1076
>>> (Voice)
>>> North Dakota State University, Fargo, ND 58105-5164
>>>
>>> _______________________________________________
>>> oi-dev mailing list
>>> oi-dev at openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>>
>>
>>
>>
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure /
> Division of Information Technology    /                701-231-1076 (Voice)
> North Dakota State University, Fargo, ND 58105-5164



-- 
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20261101/0adf0651/attachment.html>

From benny.lyons at gmx.net  Sun Nov  1 23:37:47 2026
From: benny.lyons at gmx.net (benn)
Date: Mon, 02 Nov 2026 00:37:47 +0100
Subject: [oi-dev] Upgrade with Intel graphics does not work
In-Reply-To: <auT8UFYyOg5eduRM@imap.fastmail.com>
References: <auT8UFYyOg5eduRM@imap.fastmail.com>
Message-ID: <0b9a60da3a0468ab395ecd822b930665b2859720.camel@gmx.net>

Hi Gary, 
On Fri, 2026-10-30 at 15:21 -0500, Gary Mills wrote:
> I recently upgraded a system from OI-2026-05-31 to OI-2026-10-16.
> This system uses the Intel graphics built-in to the CPU.? With
> xscreensaver or mate-screensaver, it no longer blanks the screen
> before login.? This worked with the original BE.? With
> mate-screensaver, it does blank the screen after login, but does not
> shut off the video.? This too used to work with the original BE, and
> with xscreensaver.? Is there any way I can fix this behavior?
> 
> The system does a BIOS boot, not an EFI boot.? At least, that's what
> the original BE did.? I assume that an OS upgrade will not change the
> boot type.? Is there any way to determine the boot type on a running
> system?
> 
> Screen blanking does work correctly on systems that have Radeon
> graphics.? Something must have happened to break systems that use
> built-in Intel graphics.
> 
You should see how the system booted, i.e.,  EFI
 by using dmesg:
   dmesg | grep -i efi
If this is empty, then this was a BIOS boot (assuming you are not
booting on some virtual machine.)


You can also check the logs created by syslogd under: /var/svc/log
Do something like grep -i whatever /var/svc/log/*log

Also check /var/adm/messages. Scroll down to the current date/boot time
and read though how your system was initiated.

Cheers
benn

_______________________________________________
oi-dev mailing list
oi-dev at openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev




From gary_mills at fastmail.fm  Mon Nov  2 01:33:35 2026
From: gary_mills at fastmail.fm (Gary Mills)
Date: Sun, 1 Nov 2026 20:33:35 -0500
Subject: [oi-dev] Upgrade with Intel graphics does not work
In-Reply-To: <0b9a60da3a0468ab395ecd822b930665b2859720.camel@gmx.net>
References: <auT8UFYyOg5eduRM@imap.fastmail.com>
	<0b9a60da3a0468ab395ecd822b930665b2859720.camel@gmx.net>
Message-ID: <aufob0Xr6VtzPEs2@imap.fastmail.com>

On Mon, Nov 02, 2026 at 12:37:47AM +0100, benn wrote:
> Hi Gary, 
[...]

Thanks for the response.

> You should see how the system booted, i.e.,  EFI
>  by using dmesg:
>    dmesg | grep -i efi
> If this is empty, then this was a BIOS boot (assuming you are not
> booting on some virtual machine.)

This is indeed empty, suggesting a BIOS boot, as I would expect from
an OS upgrade.  However, the dmesg memory buffer has probably
overflowed by now.

> You can also check the logs created by syslogd under: /var/svc/log
> Do something like grep -i whatever /var/svc/log/*log

There's no mention of EFI there.  It must have been a BIOS boot.

> Also check /var/adm/messages. Scroll down to the current date/boot time
> and read though how your system was initiated.

I got the boot time with "who -b" and found the startup messages.
However, I don't know what to look for.

I suppose I should do an EFI boot to look in the places you suggest,
and to see if the graphics problem is fixed.


-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-