From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: 70880@debbugs.gnu.org
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Subject: [bug#70880] [PATCH v3 6/8] gnu: Add prusa-libbgcode.
Date: Sat, 13 Jul 2024 14:13:15 +0300 [thread overview]
Message-ID: <beabc04aa4aaf7df23c74dbe1c89afd1e12f557a.1720869087.git.poptsov.artyom@gmail.com> (raw)
In-Reply-To: <cover.1720869087.git.poptsov.artyom@gmail.com>
* gnu/packages/engineering.scm (prusa-libbgcode): New variable.
Change-Id: I1f18c399d0fe36987c613ce4c0c3845c803beb45
---
gnu/packages/engineering.scm | 46 ++++++++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)
diff --git a/gnu/packages/engineering.scm b/gnu/packages/engineering.scm
index 5dfb1e1be3..30eb5a7773 100644
--- a/gnu/packages/engineering.scm
+++ b/gnu/packages/engineering.scm
@@ -3775,6 +3775,52 @@ (define-public libigl
visualization, matrix manipulation.")
(license (list license:gpl3 license:mpl2.0))))
+(define-public prusa-libbgcode
+ ;; Use the latest commit since there are no proper releases nor tags.
+ (let ((commit "8ae75bd0eea622f0e34cae311b3bd065b55eae9b")
+ (revision "0"))
+ (package
+ (name "prusa-libbgcode")
+ (version (git-version "0.0.0" revision commit))
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/prusa3d/libbgcode")
+ (commit commit)))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "0fjx2ijz9zqpqs486lcrrrhqvmfzrpb8j6v57l0jiynavwv3kznw"))))
+ (native-inputs (list catch2))
+ (propagated-inputs (list zlib boost heatshrink))
+ (build-system cmake-build-system)
+ (home-page "https://github.com/prusa3d/libbgcode")
+ (synopsis "Prusa Block and Binary G-code reader/writer/converter")
+ (description
+ "Binary G-code is a new standard for encoding and compressing ASCII G-code
+files. G-code files are easy to read and interpret, but their downside is that the
+data is not saved efficiently, and the file size is often very large. Compression of
+the file is problematic because the printers usually run on limited hardware and they
+may not have enough memory and/or CPU power to decompress it.
+
+Block and Binary G-Code is a new G-code file format featuring the following
+improvements over the legacy G-code:
+@itemize
+@item Block structure with distinct blocks for metadata vs. G-code.
+@item Faster navigation.
+@item Coding and compression for smaller file size.
+@item Checksum for data validity.
+@item Extensibility through new (custom) blocks. For example, a file signature block
+may be welcome by corporate customers.
+@end itemize
+
+The binary G-code format is flexible and the encoding and compression of individual
+blocks is variable. @code{libbgcode} library contains the routines to convert ASCII
+G-codes to binary and vice versa.")
+ ;; See
+ ;; <https://github.com/prusa3d/libbgcode/blob/main/pyproject.toml>
+ (license license:agpl3+))))
+
(define-public prusa-slicer
(package
(name "prusa-slicer")
--
2.45.2
next prev parent reply other threads:[~2024-07-13 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1720869087.git.poptsov.artyom@gmail.com>
2024-07-13 11:13 ` [bug#70880] [PATCH v3 1/8] gnu: cgal: Update to 5.6.1 Artyom V. Poptsov
2024-07-13 11:13 ` [bug#70880] [PATCH v3 2/8] gnu: glfw: Update to 3.3.10 Artyom V. Poptsov
2024-07-13 11:13 ` [bug#70880] [PATCH v3 3/8] gnu: glfw-3.4: New variable Artyom V. Poptsov
2024-07-13 11:13 ` [bug#70880] [PATCH v3 4/8] gnu: libigl: Update to 2.4.0 Artyom V. Poptsov
2024-07-13 11:13 ` [bug#70880] [PATCH v3 5/8] gnu: Add heatshrink Artyom V. Poptsov
2024-07-13 11:13 ` Artyom V. Poptsov [this message]
2024-07-13 11:13 ` [bug#70880] [PATCH v3 7/8] gnu: Add prusa-wxwidgets Artyom V. Poptsov
2024-07-13 11:13 ` [bug#70880] [PATCH v3 8/8] gnu: prusa-slicer: Update to 2.7.4 Artyom V. Poptsov
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=beabc04aa4aaf7df23c74dbe1c89afd1e12f557a.1720869087.git.poptsov.artyom@gmail.com \
--to=poptsov.artyom@gmail.com \
--cc=70880@debbugs.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.