-
Notifications
You must be signed in to change notification settings - Fork 225
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
Improve COMPILING, CONTRIBUTING and TRANSLATING files #2561
Improve COMPILING, CONTRIBUTING and TRANSLATING files #2561
Conversation
735f9ea
to
7593f64
Compare
f053327
to
df47b87
Compare
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already much better but:
I think we should note the minimum, maximum and preferred version of Qt to use.
Also note to install the required 'opensource' version and not to use the 'universal installer'
Also the given Qt link will most likely lead to installing the latest Qt version which will not work. Maybe better directly link to the suitable versions at https://download.qt.io/official_releases/qt/ ?
Qt for macOS homebrew link does not work anymore (Should be brew install qt@5 ??) And why use homebrew ? better versions are available via the opensource installer. (And homebrew gave a lot of issues for me, finally still ending up with an incomplete Qt version.)
Qt for iOS: When building on macOS I think it's better to install the correct macOS version with the official opensource installer and then to make sure to also check the iOS option when installing.
Same goes for XCode: The given link (app store) will download the latest version, which won't work for Jamulus. Better state which version (11 ?) to use and use the link https://developer.apple.com/download/all/q=Xcode ?
Build on windows: Edit the $QtCompile32 and $QtCompile64 variables if needed ??
I'm still wondering why this is needed, since it gives rebase problems every time, why not use command line options and/or environment variables ? (We should create an issue to modify the script?)
For just debugging/testing there are also simpler options when using Visual Studio... (qmake -tp vc Jamulus.pro and simply build in VS)
Note: "If ? have a free Apple Developer Account", You must have, otherwise you couldn't download the needed software either.
@jujudusud what would you write? |
At the moment it's probably not clear for us either. We basically set the lowest version to Qt5.0 (if that exists) and the highest one to Qt 5.15.2/5.15.3 once Qt6 support is ready, we'd probably raise the maximum supported version.
I thought that's already documented - at least for Windows. Could you please click on the lines you'd want to add it and - in the editor - give a suggestion on what you'd want to add. See how to do this here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
Good to know it doesn't work anymore. I thought it's much easier to get Qt via brew since you'd not need the somewhat bloated Qt installer (with login).
For me the latest version worked well?
No. Will edit the file
Probably yes. You're much more experienced with the VS setup and I don't know much about how to set it up (as I develop mainly on Linux)
There's a distinction between Apple ID without Developer account (= allows you to download Xcode), Free developer account (you'll need to register your normal Apple ID or at least accept some terms somewhere to get a developer account) (= allows you to actually develop apps and run them on iOS devices) and the $99 one (which emlyn uses to sign the build which allows you to publish apps on the AppStore/sign them). Probably we need to clarify it a bit more, but I thought it's clear like that. |
You wrote "via coco" instead of "via choco". |
Ok. Fixed. |
Concerning the Qt variables, I think they don't need to be changed at all: Just give the correct path to the Qt build. |
COMPILING.md
Outdated
@@ -26,6 +33,8 @@ On Ubuntu-based distributions 18.04+, Debian 9+, and Raspberry Pi OS: | |||
- qttools5-dev-tools | |||
- libjack-jackd2-dev | |||
|
|||
**Note:** The exact dependencies might be different for older distributions. See [this comment by softins](https://github.com/jamulussoftware/jamulus/pull/2267#issuecomment-1022127426) | |||
|
|||
### On Fedora 33+ | |||
|
|||
- qt5-qtdeclarative-devel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering why qt5-qtdeclarative-devel should be the correct package. As far as I understand, it's mainly related to QML, which we don't use. Maybe it's a package which happens to pull in the right dependencies for us, but this should probably be re-checked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know about Fedora. Someone else should have a look at that
d37afc3
to
e2a4c14
Compare
Just let them run: In visual studio they will be able to build a debug or release version for testing and they will only need the scripts if they want to create the installer. P.S. Why do we use Powershell scripts for this in windows ?? Wouldn't be running sh scripts from Git Bash be more consistent ?? |
3c8c6d7
to
f08825e
Compare
I don't think windows ships .sh support by default? |
Just a small note/thought/question to @pgScorpio which came up to me right now: Are you used to developing mostly in a small team where everyone knows what the other people do or alone? I think some confusion about git might be the distributed nature of Free/OpenSource Software. I think the way of development here is very different to what I assume you're used to. So it's probably the source of confusion? |
No, but you will need git anyway and so you will also have Git Bash which does support it.
just because most of the time I already have Git Bash open and I'm too lazy to open a powershell too ;=) |
Indeed, most of the time I developed in teams with around 10 developers (most of the time all at the same location), and I am very used to working with PVCS and Microsoft VSS. So the confusion is because these are quite different from Git with a lot of same terminology, like Fetch and Checkout, but doing something completely different. Also the 3 stage archiving of Git makes branching, merging and rebase-ing is quite a lot more complicated and very confusing for me after using the other version control systems for over 25 years. But I'm learning... It's just a bit frustrating that in the past weeks I'm spending more time on Git problems than on actual coding. So I still would gladly accept your help with Git and on correcting some of my mistakes. (Could you PM me on that?) |
GitHub has no PM feature, but feel free to E-Mail me: https://github.com/ann0see/#hi-there--im-ann0see |
?? I don't see any email address there, but mine should be in my profile I think. (if not: pg_Scorpio@hotmail.com) |
Sent you a mail this morning. |
Sent you a mail this morning.
Strange... I still did not receive it.
…________________________________
Van: ann0see ***@***.***>
Verzonden: zaterdag 2 april 2022 19:08
Aan: jamulussoftware/jamulus ***@***.***>
CC: pgScorpio ***@***.***>; Mention ***@***.***>
Onderwerp: Re: [jamulussoftware/jamulus] Improve COMPILING and CONTRIBUTING files (PR #2561)
Sent you a mail this morning.
—
Reply to this email directly, view it on GitHub<#2561 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACGLHX6C2H4WIU3TL4I5FODVDB5ITANCNFSM5R4LZ25Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Strange. I've sent it via my own mailserver now. Maybe hotmail dislikes my E-Mail provider (that seems to happen quite often). Nevertheless, we can also meet today? |
1a69e95
to
e452695
Compare
5cedfcc
to
f3c9648
Compare
2f29817
to
97d56e6
Compare
d38b905
to
28c3b34
Compare
@gilgongo ran an AI over the file to make it sound a bit more natural: https://quillbot.com/ Could you please re-check? |
bae4930
to
76bec7a
Compare
Co-Authored-By: Jonathan <4561747+gilgongo@users.noreply.github.com> Co-Authored-By: Christian Hoffmann <christian@hoffie.info> Co-Authored-By: Peter L Jones <pljones@users.noreply.github.com>
76bec7a
to
425338f
Compare
This comment was marked as outdated.
This comment was marked as outdated.
@gilgongo please merge if this is ok for you. |
Short description of changes
Updates mainly COMPILING and CONTRIBUTING files. Some major and minor changes have been introduced.
CHANGELOG: Documentation: Rewrite some parts of COMPILING.md and CONTRIBUTING.md to stay up to date and enable clearer contribution guidelines
Context: Fixes an issue?
Fixes: #2553
Fixes: #2289
Does this change need documentation? What needs to be documented and how?
Maybe an updated contribution page on the website.
Status of this Pull Request
Ready for a hopefully not too long discussion.
What is missing until this pull request can be merged?
Review by @pgScorpio
Checklist