Github messages for voidlinux
 help / color / mirror / Atom feed
From: Lolzen <Lolzen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] obs: enable building browser source
Date: Fri, 06 Aug 2021 01:27:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32356@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

New issue by Lolzen on void-packages repository

https://github.com/void-linux/void-packages/issues/32356

Description:
Since obs 27.0 obs is able to be built with browser source for feature parity with windows in terms of panel docks (for example integrated twitch chat in within obs)
i only "tested" this by building my own portable version of obs. I can use the exact same config file interchangibly between the portable build and the official package from the void repos, as expected.

`wget https://cdn-fastly.obsproject.com/downloads/cef_binary_4280_linux64.tar.bz2
tar -xjf ./cef_binary_4280_linux64.tar.bz2
git clone --recursive https://github.com/obsproject/obs-studio.git
cd obs-studio
mkdir build && cd build
cmake -DUNIX_STRUCTURE=0 -DCMAKE_INSTALL_PREFIX="${HOME}/obs-studio-portable" -DBUILD_BROWSER=ON -DCEF_ROOT_DIR="../../cef_binary_4280_linux64" ..
make -j4 && make install`
as seen [here](https://github.com/obsproject/obs-studio/wiki/Install-Instructions#linux-portable-mode-all-distros)

             reply	other threads:[~2021-08-05 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 23:27 Lolzen [this message]
2021-08-11 22:34 ` paper42
2021-08-11 22:34 ` [ISSUE] [CLOSED] " paper42

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32356@inbox.vuxu.org \
    --to=lolzen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).