You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, the checked out source code from the main branch itself does not build under macOS (probably for other OS too). For example, deploy_fritzing_mac.sh refers to qt5 which breaks if we have qt6 installed. Also, It limits the version of qt6 to QT_MOST=6.5.10 for no good reason. Also, when building with clipper-6.4.2, the library itself generates .dylib shared libaries, while the fritzing-app requires static linking. The list goes on and on.
I have created a patch, but as you see, the patching process is highly nontrivial. There are multiple tutorials on "how to build this fritzing" online.
Hi, the checked out source code from the main branch itself does not build under macOS (probably for other OS too). For example, deploy_fritzing_mac.sh refers to qt5 which breaks if we have qt6 installed. Also, It limits the version of qt6 to QT_MOST=6.5.10 for no good reason. Also, when building with clipper-6.4.2, the library itself generates .dylib shared libaries, while the fritzing-app requires static linking. The list goes on and on.
I have created a patch, but as you see, the patching process is highly nontrivial. There are multiple tutorials on "how to build this fritzing" online.
https://gist.github.com/cocoabox/7731fb4db30615e32e9e8c84eef62b85
Questions.
Is this supposed to happen? Maybe I'm building it wrong, but I think the build process work even without patching.
Do you have plans to modify your code to make it "buildable"? I have this branch in my fork : https://github.com/cocoabox/fritzing-app/tree/1.4.0-patches but I'm hesitant on submitting a PR because of question 1.
If you could answer the above questions that would be great. Thanks.
The text was updated successfully, but these errors were encountered: