64bit/QtDev: Difference between revisions
Jump to navigation
Jump to search
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Requirements== | ==Requirements== | ||
* Maximum bid USD $ | * Maximum bid USD $750 (fixed price) (Or please help me understand a realistic budget) | ||
* see [[64bit/Dev|further requirements]]. Stuff labeled " | * see [[64bit/Dev|further requirements]]. Stuff labeled "'''Extra'''" is NOT required. For all else: DO NOT BID UNLESS YOU MEET REQUIREMENTS! | ||
* expert in Git | * expert in Git, enough to figure your way around [https://git-fork.com/ Fork] | ||
* expert in Qt | * expert in Qt | ||
* expert in BUILDING Qt Binaries | * expert in BUILDING Qt Binaries | ||
| Line 8: | Line 8: | ||
==Deliverable== | ==Deliverable== | ||
* Qt Frameworks binaries | * Qt Frameworks binaries compile "into place" such that building other projects with Qt now use the new libraries, including full support for '''macdeployqt''' (do not accept unless you know what that means) | ||
* Qt Creator can compile itself, relaunch, and | * Qt Creator can compile itself, relaunch, and see the fixes implemented | ||
* when building / debugging | * when building / debugging dependent projects, can debug into Qt libraries, hit breakpoints there, edit code there. | ||
* provide example "hello world" project with "dependency" on Qt Frameworks project, that knows to compile frameworks first, then itself, if any frameworks file is edited. | * provide example "hello world" project with "dependency" on Qt Frameworks project, that knows to compile frameworks first, then itself, if any frameworks file is edited. (Qt Creator seems the likely candidate for that) | ||
* Source trees are connected via github, so | * Source trees are connected via github, using [https://git-fork.com/ Fork GUI] (provided), so I can submit pull requests back to Qt.io, including for Example Projects | ||
* everything you did to make this work is copiously documented on a wiki page ([[64bit/QtDev/Doc|here]]), such that if a novice user of Qt followed it step by step, they would end up with all of the above | * everything you did to make this work is copiously documented on a wiki page ([[64bit/QtDev/Doc|here]]), such that if a novice user of Qt followed it step by step, they would end up with all of the above. This will be available to the public! | ||
Latest revision as of 00:55, 21 September 2020
Requirements
- Maximum bid USD $750 (fixed price) (Or please help me understand a realistic budget)
- see further requirements. Stuff labeled "Extra" is NOT required. For all else: DO NOT BID UNLESS YOU MEET REQUIREMENTS!
- expert in Git, enough to figure your way around Fork
- expert in Qt
- expert in BUILDING Qt Binaries
- expert in building Qt Creator
Deliverable
- Qt Frameworks binaries compile "into place" such that building other projects with Qt now use the new libraries, including full support for macdeployqt (do not accept unless you know what that means)
- Qt Creator can compile itself, relaunch, and see the fixes implemented
- when building / debugging dependent projects, can debug into Qt libraries, hit breakpoints there, edit code there.
- provide example "hello world" project with "dependency" on Qt Frameworks project, that knows to compile frameworks first, then itself, if any frameworks file is edited. (Qt Creator seems the likely candidate for that)
- Source trees are connected via github, using Fork GUI (provided), so I can submit pull requests back to Qt.io, including for Example Projects
- everything you did to make this work is copiously documented on a wiki page (here), such that if a novice user of Qt followed it step by step, they would end up with all of the above. This will be available to the public!