Re: [STUMP] Creating a FreeBSD StumpWM package
Javier Olaechea <[email protected]> Mon, 14 Aug 2017 00:29:21 -0500
| Newsgroups | gmane.comp.window-managers.stumpwm.devel |
|---|---|
| Message-ID | <CAFVS=zDf7_8YxqNAMAX2Kxf4P4pykuQskJB3jQkCrcAhUAXA8Q@mail.gmail.com> |
If the goal is to get something one can invoke from the shell or xinitrc, I
use cl-launch[0] plus the following script. You would have have to place
StumpWM sources somewhere where ASDF can find them and and copy the
following script (maybe change the Q arg to +Q so that it doesn't try to
fetch StumpWM from quicklisp).
```stumpwm-loader
#!/usr/bin/cl -Q -sp stumpwm -E main
(defun main (argv)
(if argv
(stumpwm (elt argv 0))
(stumpwm)))
```
[0]: http://cliki.net/cl-launch
On Sun, Aug 13, 2017 at 9:47 PM, Joseph Mingrone <[email protected]> wrote:
> Joseph Mingrone <[email protected]> writes:
>
> > Hello,
>
> > StuwmpWM used to have a FreeBSD package, but it became stale, then
> > broken and was eventually removed from the FreeBSD ports tree. It would
> > be nice for FreeBSD users to be able to get stump up and running with a
> > simple `pkg install stumpwm`, so I'm attempting to get the port/package
> > working again. I also notice there is no OpenBSD or pkgsrc package, so
> > if this package succeeds it might be a helpful template for them.
>
> > This is what works now. It pulls in all the dependencies, builds and
> > installs the executable, installs the lisp source and stumpwm.asd in the
> > common lisp central registry. The problem starts when stump is run. It
> > just starts sbcl and shows the repl with no errors. Any suggestions for
> > debugging?
>
> > Nothing stands out (to me) in the build log.
> > http://pkg.awarnach.mathstat.dal.ca/data/11amd64-default/
> 2017-08-13_18h13m27s/logs/stumpwm-20170807.log
>
> > Thanks for any insight,
>
> > Joseph
>
> This main problem has been solved and the package is mostly usable [1].
> The executable was being installed with `install -s ...`, which strips
> the executable. Clearly that was doing something wrong because the size
> of the stumpwm executable went from 55 MB to 233 KB.
>
> Regards,
>
> Joseph
>
> [1] One issue is that the executable is referring to paths used during
> the package building, that are not correct when it's installed on the
> user's machine. Hopefully I'll figure that one out.
>
> _______________________________________________
> Stumpwm-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
>
>
--
"I object to doing things that computers can do." — Olin Shivers
_______________________________________________
Stumpwm-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel