Re: [new] graphics/libliftoff

2023-04-08 Thread Vasyl Zubko
Is anyone interested in having this imported? Would require some dev help to do 
this, as I have no CVS account/permissions.

Ok?

On Wed, 5 Apr 2023, at 22:34, Vasyl Zubko wrote:
> Lightweight KMS plane library. 
>
> libliftoff eases the use of KMS planes from userspace without standing 
> in your way. Users create "virtual planes" called layers, set KMS 
> properties on them,
> and libliftoff will pick hardware planes for these layers if possible.
>
> Blog post with details: 
> https://emersion.fr/blog/2019/xdc2019-wrap-up/#libliftoff
> Repository: https://gitlab.freedesktop.org/emersion/libliftoff
>
> Builds and passes tests on -current. Verified for amd64.
>
> Attachments:
> * libliftoff.tar.gz



Re: NEW: graphics/libliftoff

2023-07-15 Thread Matthieu Herrb
On Sat, Jul 15, 2023 at 03:06:09PM +0200, Matthieu Herrb wrote:
> Lightweight KMS plane library.
> 
> libliftoff eases the use of KMS planes from userspace without standing
> in your way. Users create "virtual planes" called layers, set KMS
> properties on them, and libliftoff will pick hardware planes for these
> layers if possible.
> 
> Will be needed by wlroots/sway.
> 

New version wil fixed SHARELD_LIBS and PLIST




-- 
Matthieu Herrb


libliftoff.tgz
Description: application/tar-gz


Re: NEW: graphics/libliftoff

2023-07-16 Thread Jeremie Courreges-Anglas
On Sat, Jul 15 2023, Matthieu Herrb  wrote:
> On Sat, Jul 15, 2023 at 03:06:09PM +0200, Matthieu Herrb wrote:
>> Lightweight KMS plane library.
>> 
>> libliftoff eases the use of KMS planes from userspace without standing
>> in your way. Users create "virtual planes" called layers, set KMS
>> properties on them, and libliftoff will pick hardware planes for these
>> layers if possible.
>> 
>> Will be needed by wlroots/sway.
>> 
>
> New version wi[th] fixed SHARELD_LIBS and PLIST

Please s/Lightweight/lightweight/ in COMMENT and start SHARED_LIBS at 0.0
(new port).

libliftoff.pc mentions a dep on libdrm >= 2.4.108, that's not a problem
but it would appear more correct/future-proof to just drop the version
(from meson.build).

In DESCR I would drop the first paragraph (which just repeats COMMENT).
Actually I would just keep the second paragraph.

In Makefile, could you please tab-align values in assignements?
(No need for perfect alignement, it's just nicer to read.)

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE