Jan Wilmans

A build system like cmake is able to many things, such as create packages, run tests, reconfigure the build for different platforms. The same way you should not create God...

Thanks for your response, I also don't have the bandwidth to help right now, but if I do I will try to create a PR

I'm willing to assist, let me know on Twitter @janwilmans On Tue, Mar 30, 2021, 01:19 Patrick Quist ***@***.***> wrote: > This has been blocked for a while because of...

I'm not sure what you mean with 'only generate the include folder', copperspice is not a header only library, so a bunch of .so files are needed at runtime. If...

Ah, I understand a bit more now. Would it help if I offer the pre-build result in a separate repo ?

What if it would only point to the separate repo? then it just updates whenever we re-run the offline build (which could be manually, or automatically nightly) head on copperspice/copperspice...

this being said, to actually run the program, I guess you _do_ need to .so's to be present, for what environment should they be build ?

That sounds good, I dont mind creating my own, do you have an example how to draw a completely custom control using line/curve primitives?

The first clue is to create the run directory using `mkdir -p /usr/local/var/run/` This gets rid of the `Unable to create listener socket` error but the `Local Name collisions` remain

``` oot@vcenter:/home/vimec# ./lprint test.txt DYMO LabelWriter 450-4 root@vcenter:/home/vimec# E [2022-07-18T14:14:05.252Z] [Job 4] Unable to process job with format 'application/octet-stream'. ``` without specifying the printer, the error message is different, still...