Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 3881

General • Re: PICO W Getting Started - I2C scanner Build Errors - mainly solved

$
0
0

I cloned the working projects as I found that I would get an error with nmake not found when the project(PROJECT NAME) line was processed. I have no idea why and no one has offered an explanation - sorry.
You need to find someone familiar with the Windows tools and how the 'recommended' toolset works.

My understanding, bearing in mind that I don't use this environment at all:

Pico SDK heavily relies on CMake. This isn't a 'make' program in the traditional sense, it works at a higher layer and outputs makefiles which you then need to use a traditional make program to do the actual compiling.
NMAKE is the classic Windows make program (supplied with Microsoft compilers). It is probably suitable for compiling SDK programs if you happen to have it and set things up accordingly.
NINJA is the make program that is installed by the Raspberry Pi installer.

How you get this set up to work right with VSCODE etc. I have no idea. I regard environments like that as being like trying to work with a soldering iron 20 metres long and a telescope. But I'm old-school and no doubt considered out of touch with modern fashion.
To get I2C to work I had to use a workaround

Code:

#include "hardware/i2c.h"#include "../../hardware_i2c/include/hardware/i2c.h"
As previously mentioned, this is wrong. On the one hand, great that you managed to get your program working, but on the other hand it says you don't have your build environment under control and that's likely to give you grief in the future.

Statistics: Posted by arg001 — Fri Feb 02, 2024 10:19 am



Viewing all articles
Browse latest Browse all 3881

Trending Articles