-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS macports build fails on Big Sur 11.1 (eigen3 build failure) #23
Comments
can you open a ticket to trac.macports.org with the same information? thank you |
Any updates on this? |
We did an update from May 1. Do you receive the same error? |
@ra1nb0w I ran sudo port install NanoVNA-QT and it throws a checksum error. |
Can you post the error and the main.log? thank you |
or you can re-try to build NanoVNA-QT since I committed a fix |
I've attached |
@ra1nb0w I also tried to build, but again no EDIT: Also, the brew installation seems OK as well:
|
you need to if you have homebrew installed into |
@ra1nb0w Thanks for your response, but it still fails:
As for where it is installed:
|
Seems a stealth update from upstream.
now should be correctly in sync the checksum. thank you for testing |
It finally worked, thank you very much for your help! :) |
good! |
@ra1nb0w While I'm on it, is it possible to interface with NanoVNA-QT through the command line or with some sort of scripting? My goal is to automate the capture of (Also: is it possible to get NanoVNA-QT working on a Raspberry Pi? I don't think they can run AppImages...) |
to access nanovna v2 from command line you need to write code in c/c++, see https://github.com/nanovna-v2/NanoVNA-QT/tree/master/libxavna raspberry: yes, you can compile and install nanovna-qt in the same way or use appimages |
I get this when running fatal error: 'xavna/xavna_cpp.H' file not found
#include <xavna/xavna_cpp.H>
^~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [testt] Error 1 Where exactly is this Edit: I found it's in the Essentially my goal is to:
Hopefully this isn't super hard to achieve with the API? (apologies for the likely dumb questions - I'm clearly a beginner 😅 ) |
|
I replaced the first line of the
Thanks for your patience |
you probably need to use C++ as the entire nanovna-qt interface. anyway, to get the entire header files install the update available in macports. |
another way to comunicate with nanovna2 is to use python, see |
@ra1nb0w Wow, I had no idea this existed. The only one I had spotted is this (https://github.com/ttrftech/NanoVNA/tree/master/python), which is very similar but does not support the V2 model. But your link did the trick! I've managed to completely wrap all my utilities around this now and everything works well, thank you very very much! 😃 |
@ra1nb0w One more thing in case you've got any ideas: I've managed to get everything working and I'm able to output touchstone files, plot them etc., but I see that the |S21| values disagree between the NanoVNA alone (i.e. not connected to python/a computer) and the ones the python script is measuring. My understanding is that once I calibrate the device (SOLT) and connect it to the computer, the python interface does not seem to pick up the latest calibration on file. Is there a simple way to either load the latest calibration on file or manually re-run the SOLT calibration again through python, or do I write something up and save each state (OPEN, SHORT, LOAD, THRU) as a separate sNp file and apply the calibration locally? |
I don't know since I always calibrate the range that I need before measure any values or at least I save the calibration data in a file and I will recall it when I need it. I think that the python library should have something that you can take and use in your code. |
Using
sudo port install NanoVNA-QT
build fails with error
which in result points to:
clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.1'
inmain.log
macports_log.txt
main.log
The text was updated successfully, but these errors were encountered: