mongoose/examples/raspberry/raspberry-pi-pico-w/Makefile

NAME = raspberry-pi-pico-w

$(NAME):
	git clone --depth 1 https://github.com/mongoose-examples/$(NAME)

build: | $(NAME)
	cp ./../../../mongoose.[ch] $(NAME)
	make -C $(NAME) build

clean:
	make -C $(NAME) clean
	rm -rf $(NAME)
Add Pico-W example 2022-10-07 09:08:59 +03:00			`NAME = raspberry-pi-pico-w`

Dettach git clone and fix clean The user has to clone the repo, then edit the Makefile to change WiFi credentials. Running make build does both and the tests go flawlessly The user can run make to clone the repo, then change credentials and run make build, it will skip cloning if the repo is already there In some systems the compiled files are not owned by the user as Docker runs as root, so we first invoke clean in the cloned repo (which erases the compiled files), and then remove the cloned repo that the user owns and can rm. 2022-10-14 11:59:16 -03:00			`$(NAME):`
Add Pico-W example 2022-10-07 09:08:59 +03:00			`git clone --depth 1 https://github.com/mongoose-examples/$(NAME)`
Dettach git clone and fix clean The user has to clone the repo, then edit the Makefile to change WiFi credentials. Running make build does both and the tests go flawlessly The user can run make to clone the repo, then change credentials and run make build, it will skip cloning if the repo is already there In some systems the compiled files are not owned by the user as Docker runs as root, so we first invoke clean in the cloned repo (which erases the compiled files), and then remove the cloned repo that the user owns and can rm. 2022-10-14 11:59:16 -03:00
			`build: \| $(NAME)`
Add Pico-W example 2022-10-07 09:08:59 +03:00			`cp ./../../../mongoose.[ch] $(NAME)`
			`make -C $(NAME) build`

			`clean:`
Dettach git clone and fix clean The user has to clone the repo, then edit the Makefile to change WiFi credentials. Running make build does both and the tests go flawlessly The user can run make to clone the repo, then change credentials and run make build, it will skip cloning if the repo is already there In some systems the compiled files are not owned by the user as Docker runs as root, so we first invoke clean in the cloned repo (which erases the compiled files), and then remove the cloned repo that the user owns and can rm. 2022-10-14 11:59:16 -03:00			`make -C $(NAME) clean`
Add Pico-W example 2022-10-07 09:08:59 +03:00			`rm -rf $(NAME)`