Skip to content
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

Wiki Discussion #3

Open
vk6mo opened this issue Jun 1, 2023 · 1 comment
Open

Wiki Discussion #3

vk6mo opened this issue Jun 1, 2023 · 1 comment

Comments

@vk6mo
Copy link

vk6mo commented Jun 1, 2023

If we do
"sudo apt-get install libhamlib-dev"
then we don't need
"You can find the correct installation in the next link: https://www.linuxwolfpack.com/linuxmint_17_build_hamlib_fldigi_from_source.php"
I suggest we change instructions (I will do) to just install the library.
Are you OK with that?

If we do
"sudo apt-get install qt6-base-dev"
then we can't do
"ln -s /opt/Qt/6.2.4/gcc_64/bin/qmake /usr/bin/qmake"
qt6-base-dev installs lots of stuff in /usr/bin.
Also there are multiple paths to qmake, and the correct build relies on "/opt/Qt/6.2.4/gcc_64/bin/" being first in path to get the correct qmake.
For simplicity I suggest we just change instructions (I will do) to just
install Qt v 6.2.4 (from qt.io), then put the soft link in.
Are you OK with that?

Have tested command line build works fine with the above.

Will then add QtCreator build after that....

Was also thinking we could do a few pages

  1. Home
  2. Set Up For Command Line Build
  3. How-To Command Line Build And Install
  4. Set Up For QtCreator
  5. Other Notes
    Do you think more helpful that way?
@vk6mo
Copy link
Author

vk6mo commented Jun 5, 2023

Hi Eric, have implemented my ideas here. Happy to get your feedback if you think it can be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant