all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: 54973@debbugs.gnu.org, help-guix@gnu.org
Subject: Re: Blender has no denoiser
Date: Sat, 16 Apr 2022 23:04:28 +0200	[thread overview]
Message-ID: <20220416230428.3d17c79f@riseup.net> (raw)
In-Reply-To: <40Zr-Q4F-XDh_dufMzotUMxO1XN0y9KoBl1a0rub7s8YdrmrtxAgxxe5w1S-pej228YLenhVBoLMT7-VE99VcLRIUS4TJo45R9ePqnZW0j0=@elenq.tech>

On Sat, 16 Apr 2022 18:30:19 +0000
Ekaitz Zarraga <ekaitz@elenq.tech> wrote:

> Hi,
> 
> ------- Original Message -------
> On Saturday, April 16th, 2022 at 6:29 PM, Haider Mirza
> <x7and7@gmail.com> wrote:
> 
> 
> > The Guix installation of Blender has no denoiser.
> > Blender's compositor says that Blender is compiled without
> > "OpenImageDenoise"
> >
> > Last time I checked OIDN (OpenImageDenoise) is free software and
> > all it's dependancies are also.
> > I tried to packaged OIDN but it just ended up being a massive pain
> > and It's depenadancy (ispc) just refused to compile.
> > Can you suggest some sort of solution (The IRC has no answers)
> > --
> > Haider Mirza via Emacs on a GNU/Linux system  
> 
> I had a similar issue in the past with blender, it was missing a
> dependency and I had to package it myself. It is what it is.
> Sometimes you need to package this kind of software, it's full of
> compilation errors and so on. The only thing we can do is to help you
> package it. Can you share the package you developed?
> 

It was already sent in the CC'd issue. I think it's best to continue
the discussion there, instead of forking it onto two lists.


  reply	other threads:[~2022-04-16 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 12:02 Blender has no denoiser Haider Mirza
2022-04-16 18:30 ` Ekaitz Zarraga
2022-04-16 21:04   ` raingloom [this message]
2022-04-16 21:20   ` Haider Mirza

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=20220416230428.3d17c79f@riseup.net \
    --to=raingloom@riseup.net \
    --cc=54973@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.