|  | 
|  | 1 | +name: A problem with compiling Sonic Pi | 
|  | 2 | +description: I had a problem when compiling my own build of Sonic Pi from the source code. | 
|  | 3 | +labels: ["triage","developer experience"] | 
|  | 4 | +body: | 
|  | 5 | +  - type: markdown | 
|  | 6 | +    attributes: | 
|  | 7 | +      value: | | 
|  | 8 | +        Hello! Thank you for wanting to raise an issue for us, so that we know what's not working for you. | 
|  | 9 | +
 | 
|  | 10 | +        Sorry you're having issues compiling Sonic Pi! We're always working to improve the build experience. | 
|  | 11 | +
 | 
|  | 12 | +        The core Sonic Pi development team is fairly small and made up of volunteers (with the exception of Sam Aaron, who relies much on crowd-funding) so the more help we can receive to manage, troubleshoot and hopefully fix your issues for you the better - help us to help you! Please follow the checklist below - that way you might not even need to raise an issue after all :smile: | 
|  | 13 | +  - type: checkboxes | 
|  | 14 | +    id: read-troubleshooting-guide | 
|  | 15 | +    attributes: | 
|  | 16 | +      label: Prerequisites | 
|  | 17 | +      options: | 
|  | 18 | +        - label: I've read the [Sonic Pi troubleshooting guide](https://github.com/sonic-pi-net/sonic-pi/wiki/Troubleshooting-Issues) and followed its suggestions where relevant | 
|  | 19 | +          required: true | 
|  | 20 | +  - type: input | 
|  | 21 | +    id: dev-commit | 
|  | 22 | +    attributes: | 
|  | 23 | +      label: Git commit id | 
|  | 24 | +      description: "What was the Git commit id of the code you were trying to compile from?" | 
|  | 25 | +      placeholder: "Example: 00f737e" | 
|  | 26 | +    validations: | 
|  | 27 | +      required: true | 
|  | 28 | +  - type: input | 
|  | 29 | +    id: os-version | 
|  | 30 | +    attributes: | 
|  | 31 | +      label: Operating System | 
|  | 32 | +      description: "What Operating System (and which version) were you using?" | 
|  | 33 | +      placeholder: "Example: Windows 10" | 
|  | 34 | +    validations: | 
|  | 35 | +      required: true | 
|  | 36 | +  - type: textarea | 
|  | 37 | +    id: build-steps | 
|  | 38 | +    attributes: | 
|  | 39 | +      label: What steps did you take to set up and to try to compile Sonic Pi? | 
|  | 40 | +      description: | | 
|  | 41 | +        You can drag related images into the description if you like. | 
|  | 42 | +        When attempting to compile Sonic Pi, what steps did you take? | 
|  | 43 | +        Provide as much detail as possible - such as: | 
|  | 44 | +        - Software dependencies you set up for the build - versions, places they were downloaded from, etc | 
|  | 45 | +        - Any build steps you took that were different to those described in the build guides ([BUILD-LINUX.md](https://github.com/sonic-pi-net/sonic-pi/blob/dev/BUILD-LINUX.md), [BUILD-MAC.md](https://github.com/sonic-pi-net/sonic-pi/blob/dev/BUILD-MAC.md), [BUILD-RASPBERRY-PI.md](https://github.com/sonic-pi-net/sonic-pi/blob/dev/BUILD-RASPBERRY-PI.md) or [BUILD-WINDOWS.md](https://github.com/sonic-pi-net/sonic-pi/blob/dev/BUILD-WINDOWS.md)) - including the order you performed them  | 
|  | 46 | +        For any steps you ran in the command line terminal, write or copy them here. Please use code formatting when you do so - if you're not sure how, please see the 'Code' examples at GitHub's [Mastering Markdown examples](https://guides.github.com/features/mastering-markdown/#examples). | 
|  | 47 | +      placeholder: "Example: I followed BUILD-LINUX.md, installing Qt 6.2.3 from https://www.qt.io/download-thank-you?os=linux&hsLang=en ..." | 
|  | 48 | +    validations: | 
|  | 49 | +      required: true | 
|  | 50 | +  - type: textarea | 
|  | 51 | +    id: what-happened | 
|  | 52 | +    attributes: | 
|  | 53 | +      label: What happened? | 
|  | 54 | +      description: | | 
|  | 55 | +        You can drag related images into the description if you like. | 
|  | 56 | +        Copy the results of the build process here, including errors. If there is an error message that you feel has a clear cause or explanation, you can paste just the error plus a small amount of the messages around it for context. If in doubt however, the more information you can give us the better - such as the entire build process output, in case more detailed investigation is necessary. | 
|  | 57 | +      placeholder: | | 
|  | 58 | +        Example: When I run `cmake --build . --config Release` I get the following result: | 
|  | 59 | +        ``` | 
|  | 60 | +        c++: fatal error: Killed signal terminated program cc1plus | 
|  | 61 | +        compilation terminated. | 
|  | 62 | +        make[2]: *** [gui/qt/CMakeFiles/sonic-pi.dir/build.make:3658: gui/qt/CMakeFiles/sonic-pi.dir/sonic-pi_autogen/EWIEGA46WW/qrc_SonicPi.cpp.o] Error 1 | 
|  | 63 | +        make[1]: *** [CMakeFiles/Makefile2:184: gui/qt/CMakeFiles/sonic-pi.dir/all] Error 2 | 
|  | 64 | +        make: *** [Makefile:84: all] Error 2 | 
|  | 65 | +        ``` | 
|  | 66 | +    validations: | 
|  | 67 | +      required: true | 
|  | 68 | +  - type: textarea | 
|  | 69 | +    id: other-details | 
|  | 70 | +    attributes: | 
|  | 71 | +      label: Other Details | 
|  | 72 | +      description: | | 
|  | 73 | +        You can drag related images into the description if you like. | 
|  | 74 | +        Feel free to provide any other relevant information about the issue if you have it, or can get it: | 
|  | 75 | +        - Ideas about possible root causes | 
|  | 76 | +        - Workarounds or potential solutions (or even better, send us a pull request!) | 
|  | 77 | +        - Etc... | 
|  | 78 | +      placeholder: "Example: Could this be related to X? Maybe we could add the foo software package as a dependency in BUILD-LINUX.md?" | 
|  | 79 | +    validations: | 
|  | 80 | +      required: false | 
0 commit comments