Bug 390821

Summary: solve-field location
Product: [Applications] kstars Reporter: Hans Lambermont <hans>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: git   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: https://commits.kde.org/kstars/546dfef49beea0e29fed301ae58f889dcd6dbb53 Version Fixed/Implemented In:
Sentry Crash Report:

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