Bug 390821 - solve-field location
Summary: solve-field location
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: git
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-20 22:10 UTC by Hans Lambermont
Modified: 2018-02-21 07:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Lambermont 2018-02-20 22:10:59 UTC
kstars checks for /usr/bin/solve-field in kstars/auxiliary/ksutils.cpp and then just calls 'solve-field' in kstars/ekos/align/offlineastrometryparser.cpp wherever it is found in the path to determine the version. Lateron the /usr/bin/solve-field is used to actually solve a field.

Either we fix above inconsistency by for instance QProcess solveField in OfflineAstrometryParser::init should use Options::astrometrySolverBinary() to determine the solve-field path.

Or solve-field should be allowed to live anywhere in the path. (which would allow for my setup, I run a locally compiled astrometry with the binaries in ~/bin/ or something like that).
Comment 1 Jasem Mutlaq 2018-02-21 07:34:45 UTC
Git commit 546dfef49beea0e29fed301ae58f889dcd6dbb53 by Jasem Mutlaq.
Committed on 21/02/2018 at 07:34.
Pushed by mutlaqja into branch 'master'.

Use solver path in detection.

M  +9    -7    kstars/ekos/align/offlineastrometryparser.cpp
M  +1    -1    kstars/fitsviewer/fitsview.h

https://commits.kde.org/kstars/546dfef49beea0e29fed301ae58f889dcd6dbb53