Question about prusaslicer package

Question about prusaslicer package

[pinoaffe]

Hi guix,

I recently made an attempt at packaging prusaslicer (just the
commandline interface, I couldn't get the GUI to work).

It does build successfully, and I've attached my package definition.

I ran into a weird bug where, for whatever reason, the commandline
utility only works if I run it from inside the directory where the
prusa-slicer binary is located.

Does anyone have a clue as to what might be going wrong?
(or, better yet, how to fix it?)

kind regards,
pinoaffe

Re: Question about prusaslicer package

[pinoaffe]

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

Ah I forgot the attachment...


[-- Attachment #2: prusaslicer.scm --]
[-- Type: application/octet-stream, Size: 2273 bytes --]

(define-module (prusaslicer)
  #:use-module ((guix licenses) #:prefix license:)
  #:use-module (guix build-system cmake)
  #:use-module (guix build cmake-build-system)
  #:use-module (guix download)
  #:use-module (guix git-download)
  #:use-module (guix packages)
  #:use-module (guix utils)
  #:use-module (guix build utils)
  #:use-module (gnu packages)
  #:use-module (gnu packages curl)
  #:use-module (gnu packages tls)
  #:use-module (gnu packages pkg-config)
  #:use-module (gnu packages tbb)
  #:use-module (gnu packages gl)
  #:use-module (gnu packages glib)
  #:use-module (gnu packages xorg)
  #:use-module (gnu packages multiprecision)
  #:use-module (gnu packages xml)
  #:use-module (gnu packages serialization)
  #:use-module (gnu packages compression)
  #:use-module (gnu packages maths)
  #:use-module (gnu packages image)
  #:use-module (gnu packages graphics)
  #:use-module (gnu packages wxwidgets)
  #:use-module (gnu packages boost))



(define-public prusaslicer
  (package
   (name "prusaslicer")
   (version "2.3.3-0")
   (source (origin
            (method git-fetch)
            (uri (git-reference
                  (url "git://github.com/prusa3d/PrusaSlicer")
                  (commit "version_2.3.3")))
            (file-name (git-file-name name version))
            (sha256
              (base32
               "0w0synqi3iz9aigsgv6x1c6sg123fasbx19h4w3ic1l48r8qmpwm"))))
   (build-system cmake-build-system)
   (arguments
    `(#:configure-flags `("-DSLIC3R_GUI=no" ; could't get cmake to find wxwidgets
                          "-DSLIC3R_BUILD_TESTS=off") ; tests link into the gui
      #:tests? #f))
   (inputs
    `(("boost" ,boost)
      ("curl" ,curl)
      ("pkg-config" ,pkg-config)
      ("tbb" ,tbb)
      ("zlib" ,zlib)
      ("dbus" ,dbus)
      ("glu" ,glu)
      ("glew" ,glew)
      ("glu" ,glu)
      ("libpng" ,libpng)
      ("gmp" ,gmp)
      ("mpfr" ,mpfr)
      ("expat" ,expat)
      ("cereal" ,cereal)
      ("nlopt" ,nlopt)
      ("openvdb" ,openvdb)
      ("openexr" ,openexr)
      ("libpthread-stubs" ,libpthread-stubs)
      ("cgal" ,cgal)
      ("openssl" ,openssl)))
   (home-page "https://github.com/prusa3d/PrusaSlicer")
   (description "asdf")
   (synopsis "asdf")
   (license license:agpl3)))

prusaslicer

[-- Attachment #3: Type: text/plain, Size: 527 bytes --]


pinoaffe writes:

> Hi guix,
>
> I recently made an attempt at packaging prusaslicer (just the
> commandline interface, I couldn't get the GUI to work).
>
> It does build successfully, and I've attached my package definition.
>
> I ran into a weird bug where, for whatever reason, the commandline
> utility only works if I run it from inside the directory where the
> prusa-slicer binary is located.
>
> Does anyone have a clue as to what might be going wrong?
> (or, better yet, how to fix it?)
>
> kind regards,
> pinoaffe

Re: Question about prusaslicer package

[Bengt Richter]

Hi pinoaffe,

On +2021-09-19 14:16:26 +0200, pinoaffe wrote:
> Ah I forgot the attachment...
> 


> 
> pinoaffe writes:
> 
> > Hi guix,
> >
> > I recently made an attempt at packaging prusaslicer (just the
> > commandline interface, I couldn't get the GUI to work).
> >
> > It does build successfully, and I've attached my package definition.
> >
> > I ran into a weird bug where, for whatever reason, the commandline
> > utility only works if I run it from inside the directory where the
> > prusa-slicer binary is located.
> >
> > Does anyone have a clue as to what might be going wrong?
> > (or, better yet, how to fix it?)
> >
> > kind regards,
> > pinoaffe
>
--8<---------------cut here---------------start------------->8---
from info execv, at the bottom
could this be a clue?

NOTES
    The default search path (used when the environment does not
    contain the variable PATH) shows some variation across
    systems. It generally includes /bin and /usr/bin (in that
    order) and may also include the current working directory.
               ^^^
    On some other systems, the current working is included after
    /bin and /usr/bin, as an anti-Trojan-horse measure. The
    glibc implementation long followed the traditional default
    where the current working direc‐ tory is included at the
    start of the search path. However, some code refactoring
    during the development of glibc 2.24 caused the current
                              ^^^^^^^^^^ ??   
    working directory to be dropped altogether from the default
                            ^^^^^^^^^^^^^^^^^^
    search path. This accidental behavior change is considered
    mildly beneficial, and won't be re‐ verted.
--8<---------------cut here---------------end--------------->8---

Might you have a script making relative helper-script calls
that depends on searching in the current directory, and works if
your cwd is there but not if you execute from elsewhere?

Though if it works, I guess that would suggest you have pre 2.24 glibc?
Not sure where I saw more info, so can't say.

Maybe changing some relative path to absolute could be a workaround?

HTH :)
--  
Regards,
Bengt Richter

Re: Question about prusaslicer package

[Ricardo Wurmus]

Hi pinoaffe,

> I ran into a weird bug where, for whatever reason, the 
> commandline
> utility only works if I run it from inside the directory where 
> the
> prusa-slicer binary is located.

Try to figure out what commands are called and then patch the 
source code to refer to the tools by absolute file name, e.g. with 
(string-append (assoc-ref outputs "out") "/bin/foo").

-- 
Ricardo