Anyone else having issues Building SonicPi on windows? #3382
Comments
|
Hi @iamjonny I don't know a whole lot about vcpkg, so take my suggestions with a grain of salt - but for laughs, I deleted the vcpkg folder from my Sonic Pi installation and tried doing a I then noticed that it had said earlier in that build, "Restored 19 package(s) from C:\Users\ethan\AppData\Local\vcpkg\archives" which I figured would be undesirable if I was trying to replicate a fresh install of vcpkg - so I deleted all contents from that archives folder, deleted the Sonic Pi vcpkg folder again, and re-ran Maybe worth trying something similar on your end if you haven't already? 🤷♂️ 🤞 |
|
Many thanks @ethancrawford, definitely worth a try 👍 The latest build completed with what appears to be the same results, including the triplet warning and the VS prompt's x86 targeting, not sure if they're related or important or "normal" There's 6 packages that are marked * as being scheduled for build (looking at the asterixes) and looks like it's always the libwinpthread library that's first to fail. I'm surprised you had no issues obtaining because I couldn't see that version (9.0.0.6373) on the remote filesystem when viewing - I had intended to try using an available version like V10, to see what happens... Interestingly the tailwind css resource was obtained successfully, I think this was one item that kept appearing in the build-error-collection TlDr; Localappdata\vcpkg\archived cleared and win-build re-ran, appears same issues on build |
|
Not sure what's specifically going wrong for you. I'm assuming you're attempting to build the latest from I think that @ethancrawford is likely to be on the right track. vcpkg can have old stuff hanging around which can interfere with new builds. That said, it's building fine on my Windows machine and fine on the Github CI - so it definitely can build in some situations in its current form. Something must be not quite the same on your setup. On a whim, I've updated to the latest vcpkg on Windows - so try completely nuking vcpkg - so the whole Sonic Pi src folder and the files Ethan mentioned, pull the latest version and try again. Note that any other issues (tailwind etc.) should be ignored until the vcpkg stuff is working well. |
|
I'm not sure how critical the Visual Studio prompt targeting x86 is also, if vcpkg says it is "installing for x64-windows-static-md", but I've been using Visual Studio 2022 Developer Command Prompt, and haven't seen any warnings like that. It may or may not help to use the developer command prompt, and/or target it to the correct architecture, if you aren't already - there are instructions on how to do so at https://learn.microsoft.com/en-us/visualstudio/ide/reference/command-prompt-powershell?view=vs-2022#command-line-arguments for example 🤷♂️ |
|
Thanks for the hot tips!! 🙏🏻 I'd received a link to the commit for the version I wanted to build, and with that I downloaded the zip from github, then extracted contents... maybe this is available from the latest dev as mentioned... I can download the https://github.com/sonic-pi-net/sonic-pi/archive/refs/heads/dev.zip version if that's recommended? I have tried nuking the source directory previously, retrying that now... The other notable differences include the versions of the apps I located, eg qt 6.4.3 etc (mentioned in first post here) and the OS (windows 11 pro)
|
|
In case it's relevant, When I tested this yesterday I was building latest commit on dev at the time, which was referencing vcpkg 2023.10.19. (Sam updated it even further a little earlier today also.) Maybe there's a specific issue with 2022.11.14 causing the mirrors for libwinpthread to fail? 🤷♂️ Incidentally, I had first succeeded a few days before that even with latest dev, no issues with vcpkg at the time - but I had specified Qt 6.6 something, and although it compiled, keyboard shortcuts stopped working! Downgrading to 6.4.3 worked. Good you chose that version 😅 |
Many Thanks for this too - I had tried to work out where in the commands called by the scripts that the arguments should be added for targeting, but got lost and intimidated by all the files in the cmake scripts - I'll revisit this now, to try to resolve he targeting issue - FWIW I am running from the vs dev command prompt; I'd ordered my active processes by architecture and noticed a build application was one of the few x86 processes running. |
|
I'm just about to retry with latest dev, if I run (Just wondering for future reference, eg what to purge when, and maybe to make a batch cleaner for tidying up stuff like the vcpkg folders, and anything else that should be wiped) Latest attempt!
re: target architecture I think the argument to add is
just waiting for objects to be received from git, then I'll relaunch the new, targeted dev-prompt and retry as per build instructions...
|
No idea tbh - I don't really know all that much about the windows/visual studio build toolchain 😅 |
|
Seems that 32-bit app is normal and okay, I won't muck with that unless I encounter memory issues. Related info, from Victor on the IntelliBuild team Although I was able to fetch sonic-pi the vcpkg fails; am wondering if possible to get this via browser with d/l manager, and if that'll help here.
Because the wifi password is not known (sharing with QR) I'm using hotspot on mobile, but apparently a mobile hotspot is not a proxy...
Another great page on SO re the issues with git clone and curl helped configure verbose logging
I tried adjusting the http lowLimit but still getting the issue... but after repeated calls to Thank you all so much for all your assistance and saint-like patience!!! 🙏 🤘🏻 |
|
just one more thing before I close this as solved 😁 I just wondered, if I'm rebuilding after changes, is it possible to do so now without an internet connection? eg offline build process? if possible, do I have to do anything to make the build process not try to download stuff (that presumably I now finally have) ? THANK YOU SO MUCH!!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Appears problems persists with one or more of the dependencies.
sonic-pi.exe not made, and various other issues.
Environment info
Build log
The text was updated successfully, but these errors were encountered: