Github messages for voidlinux
 help / color / mirror / Atom feed
From: michalszmidt <michalszmidt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: solvespace, template file included, needs fixing
Date: Mon, 04 Sep 2023 01:20:58 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45898@inbox.vuxu.org> (raw)

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

New issue by michalszmidt on void-packages repository

https://github.com/void-linux/void-packages/issues/45898

Description:
### Package name

solvespace

### Package homepage

https://solvespace.com/

### Description

**My 3 cents:**
It's just easier to get started comparing to advanced CADs, really good for quick 3d printing.

**From their website:**
SOLVESPACE is a free (GPLv3) parametric 3d CAD tool. Applications include:
- modeling 3d parts — draw with extrudes, revolves, helixes and Boolean (union / difference / intersection) operations
- modeling 2d parts — draw the part as a single section, and export DXF, PDF, SVG; use 3d assembly to verify fit
- 3d-printed parts — export the STL or other triangle mesh expected by most 3d printers
- preparing CAM data — export 2d vector art for a waterjet machine or laser cutter; or generate STEP or STL, for import into third-party CAM software for machining
- mechanism design — use the constraint solver to simulate planar or spatial linkages, with pin, ball, or slide joints
- plane and solid geometry — replace hand-solved trigonometry and spreadsheets with a live dimensioned drawing_

**Current work**
Uses cmake as build system if compiled from release (doesn't contain .git directory in tree) needs patch, that  sets GIT_COMMIT_HASH to one from commit and comments out some other script, see below). I tried to xbps-src to handle that but without success, please help.

patch was done using regular `diff` not `git diff`.

It's my first contribution here, forgive mistakes.

```ini
pkgname=solvespace
version=3.1
revision=1
archs="x86_64*"
build_style=cmake
configure_args="-DCMAKE_BUILD_TYPE=Release -DENABLE_OPENMP=ON"
makedepends="base-devel git zlib-devel libpng-devel cairo-devel freetype-devel json-c-devel fontconfig-devel gtkmm-devel pangomm-devel libspnav-devel MesaLib-devel glu-devel libgomp-devel eigen mimalloc-devel"
depends="zlib libpng cairo freetype json-c fontconfig gtkmm pangomm libspnav glu libgomp eigen mimalloc"
short_desc="Free parametric 3d CAD tool. CLI and GUI"
maintainer="Orphan <orphan@voidlinux.org>"
license="GPL-3.0"
homepage="https://solvespace.com"
distfiles="https://github.com/solvespace/solvespace/releases/download/v${version}/solvespace-${version}.tar.xz"
checksum=34a273ce642d0c77b8f101463730ed4eade7d90cfabfe486f3e7cbf494ff132a
```
patch
```diff
--- a/CMakeLists.txt	2023-09-03 21:54:08.706827662 +0000
+++ b/CMakeLists.txt	2023-09-03 22:02:20.616113196 +0000
@@ -34,9 +34,9 @@
 # NOTE TO PACKAGERS: The embedded git commit hash is critical for rapid bug triage when the builds
 # can come from a variety of sources. If you are mirroring the sources or otherwise build when
 # the .git directory is not present, please comment the following line:
-include(GetGitCommitHash)
+# include(GetGitCommitHash)
 # and instead uncomment the following, adding the complete git hash of the checkout you are using:
-# set(GIT_COMMIT_HASH 0000000000000000000000000000000000000000)
+set(GIT_COMMIT_HASH 70bde63cb32a7f049fa56cbdf924e2695fcb2916)
 
 string(SUBSTRING "${GIT_COMMIT_HASH}" 0 8 solvespace_GIT_HASH)
 project(solvespace
```

### Does the requested package meet the package requirements?

Compiled

### Is the requested package released?

Yes

             reply	other threads:[~2023-09-03 23:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03 23:20 michalszmidt [this message]
2023-10-14 11:43 ` [ISSUE] [CLOSED] " michalszmidt

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45898@inbox.vuxu.org \
    --to=michalszmidt@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).