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
I was helping a school setup a Windows 10 computer lab with the Windows Pico SDK Installer and Pimoroni-Pico. Some of the Pimoroni examples/libraries motor2040, inventor2040w, cosmic_unicorn won't compile with the Windows Pico SDK installer. The rest is building just fine.
Build Command used:
cmake --build C:\Users\User\Documents\pico\pimoroni-pico\build --config Debug --target all -j 12
I should note that the reason make isn't used here, is because there are not many make files generated on Windows, most of them from what I see are only within a few driver and micropython directories. I'm not sure if make files not being generated on Windows is intended, but I thought it might be worth mentioning. If you were to try and use make, there's no make file to target so make is not going to do anything. Using cmake, or selecting and opening a Pimoroni example source file and using Run and Debug in VS Code bypasses this "problem" altogether.
I tried investigating the problems with motor2040 but couldn't find out why. Commenting out motor2040 from both the libraries and examples CMakeLists.txt to bypass it, the compilation gets further, but then has similar errors with inventor2040w, commenting that out, cosmic_unicorn has similar errors, and commenting that out, everything else seems to build just fine. I was able to just remove these three from the school's setup process since they aren't required for their targeted Pico hardware. The school was hoping for the full SDK to be available, however they allowed me to modify both the CMakeLists. I had limited time with them and I had far more pressing issues to deal with. So I left them with an updater that will update their toolchains. If/when you all fix it, they will get the fixes downstream. I wish I was able to investigate it further for you and for them, but with the time I had left, I wasn't able to look into it all that much. I figured I'd personally pass off this info to you all, to see what isn't building with the Windows Pico SDK Installer. It seems to me the number of people using Windows for Pico development is pretty low and the number of people using Pimoroni SDK on Windows seems to be even lower, so I wouldn't say this is a urgent matter.
I should also note, a few warnings pop-up with inky_frame_7.hpp/.cpp but these don't seem to cause any building issues, I didn't have that hardware to test if it's impacting anything though.
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp:109:20: warning: base 'pimoroni::PicoGraphics_PenInky7' [-Wreorder]
109 | height(height) {
| ^
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp:102:5: warning: when initialized here [-Wreorder]
102 | InkyFrame(int width, int height) :
| ^~~~~~~~~
[5446/12389] Building CXX object examples/inky_frame/CMakeFiles/inky_frame_7_day_planner.dir/__/__/libraries/inky_frame_7/inky_frame_7.cpp.obj
In file included from C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.cpp:8:
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp: In constructor 'pimoroni::InkyFrame::InkyFrame(int, int)':
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp:89:18: warning: 'pimoroni::InkyFrame::ramDisplay' will be initialized after [-Wreorder]
89 | PSRamDisplay ramDisplay;
| ^~~~~~~~~~
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp:109:20: warning: base 'pimoroni::PicoGraphics_PenInky7' [-Wreorder]
109 | height(height) {
| ^
C:/Users/User/Documents/pico/pimoroni-pico/libraries/inky_frame_7/inky_frame_7.hpp:102:5: warning: when initialized here [-Wreorder]
102 | InkyFrame(int width, int height) :
| ^~~~~~~~~
The text was updated successfully, but these errors were encountered:
I was helping a school setup a Windows 10 computer lab with the Windows Pico SDK Installer and Pimoroni-Pico. Some of the Pimoroni examples/libraries
motor2040,inventor2040w,cosmic_unicornwon't compile with the Windows Pico SDK installer. The rest is building just fine.Build Command used:
I should note that the reason make isn't used here, is because there are not many make files generated on Windows, most of them from what I see are only within a few driver and micropython directories. I'm not sure if make files not being generated on Windows is intended, but I thought it might be worth mentioning. If you were to try and use make, there's no make file to target so make is not going to do anything. Using cmake, or selecting and opening a Pimoroni example source file and using Run and Debug in VS Code bypasses this "problem" altogether.
Errors encountered:
I tried investigating the problems with
motor2040but couldn't find out why. Commenting outmotor2040from both the libraries and examplesCMakeLists.txtto bypass it, the compilation gets further, but then has similar errors withinventor2040w, commenting that out,cosmic_unicornhas similar errors, and commenting that out, everything else seems to build just fine. I was able to just remove these three from the school's setup process since they aren't required for their targeted Pico hardware. The school was hoping for the full SDK to be available, however they allowed me to modify both the CMakeLists. I had limited time with them and I had far more pressing issues to deal with. So I left them with an updater that will update their toolchains. If/when you all fix it, they will get the fixes downstream. I wish I was able to investigate it further for you and for them, but with the time I had left, I wasn't able to look into it all that much. I figured I'd personally pass off this info to you all, to see what isn't building with the Windows Pico SDK Installer. It seems to me the number of people using Windows for Pico development is pretty low and the number of people using Pimoroni SDK on Windows seems to be even lower, so I wouldn't say this is a urgent matter.I should also note, a few warnings pop-up with
inky_frame_7.hpp/.cppbut these don't seem to cause any building issues, I didn't have that hardware to test if it's impacting anything though.The text was updated successfully, but these errors were encountered: