Fresh out of the box errors with pico_sdk_init.cmake

[neurothoughtmachine]

EDIT: This is for a windows 10 build using G++ (without MinGW-w64).
If I can't get G++ to work (without MinGW-w64) then I use MSVC.

Fresh out of the box errors...

I installed VSCode a few days ago.
After having to add the following line ...

# set cmake dir
set (PICO_SDK_PATH "/picosdk/sdk")

... to my CMakeLists.txt

... and ...

#cmake version
cmake_minimum_required(VERSION 4.12 VERSION 3.31.6-msvc6)

... to my CMakeLists.txt.

These are the next errors:

[main] Configuring project: blink_example_c
[proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE --no-warn-unused-cli -S "C:/Learning Projects/MS Code/blink_example_c" -B "c:/Learning Projects/MS Code/blink_example_c/build" -G "NMake Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] CMake Error at C:/picosdk/sdk/external/pico_sdk_import.cmake:109 (get_filename_component):
[cmake] get_filename_component unknown component BASE_DIR
[cmake] Call Stack (most recent call first):
[cmake] CMakeLists.txt:8 (include)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE --no-warn-unused-cli -S "C:/Learning Projects/MS Code/blink_example_c" -B "c:/Learning Projects/MS Code/blink_example_c/build" -G "NMake Makefiles" exited with code: 1

MSVCode points to a error in line 9:
`add_library(_pico_sdk_pre_init_marker INTERFACE)

I haven't changed anything to pico_sdk_init.cmake
Below is a copy of the file.

# Pre-initialize the Raspberry Pi Pico SDK, setting up the platform and toolchain and some CMake utility functions
# This file must be included prior to the project() call

# Note: this file is perhaps named badly, as it provides a method pico_sdk_init which
# the enclosing project calls LATER to actually "initialize" the SDK (by including the CMakeLists.txt from this
# same directory)

if (NOT TARGET _pico_sdk_pre_init_marker)
    add_library(_pico_sdk_pre_init_marker INTERFACE)  # Exception has occurred <<<----------

    function(pico_is_top_level_project VAR)
        string(TOLOWER ${CMAKE_CURRENT_LIST_DIR} __list_dir)
        string(TOLOWER ${CMAKE_SOURCE_DIR} __source_dir)
        if (__source_dir STREQUAL __list_dir)
            set(${VAR} 1 PARENT_SCOPE)
        else()
            set(${VAR} 0 PARENT_SCOPE)
        endif()
    endfunction()

    function(pico_message_debug MESSAGE)
        # The log-level system was added in CMake 3.15.
        if(${CMAKE_VERSION} VERSION_LESS "3.15.0")
            message(${MESSAGE})
        else()
            message(DEBUG ${MESSAGE})
        endif()
    endfunction()

    if (NOT PICO_SDK_PATH)
        set(PICO_SDK_PATH ${CMAKE_CURRENT_LIST_DIR})
    endif ()

    get_filename_component(PICO_SDK_PATH "${PICO_SDK_PATH}" REALPATH BASE_DIR "${CMAKE_BINARY_DIR}")

    set(PICO_SDK_PATH ${CMAKE_CURRENT_LIST_DIR} CACHE PATH "Path to the Raspberry Pi Pico SDK" FORCE)

    list(APPEND CMAKE_MODULE_PATH ${PICO_SDK_PATH}/cmake)

    include(${CMAKE_CURRENT_LIST_DIR}/pico_sdk_version.cmake)
    include(pico_utils)

    message("PICO_SDK_PATH is ${CMAKE_CURRENT_LIST_DIR}")
    macro(pico_sdk_init)
        if (NOT CMAKE_PROJECT_NAME)
            message(WARNING "pico_sdk_init() should be called after the project is created (and languages added)")
        endif()
        add_subdirectory(${PICO_SDK_PATH} pico-sdk)
    endmacro()

    macro(add_sub_list_dirs var)
        foreach(LIST_DIR IN LISTS ${var})
            get_filename_component(SHORT_NAME "${LIST_DIR}" NAME)
            pico_message_debug("Including custom CMakeLists.txt ${SHORT_NAME}")
            add_subdirectory(${LIST_DIR} ${SHORT_NAME})
        endforeach()
    endmacro()

    macro(add_sub_list_files var)
        foreach(LIST_FILE IN LISTS ${var})
            pico_message_debug("Including custom CMake file ${LIST_FILE}")
            include(${LIST_FILE})
        endforeach()
    endmacro()

    macro(pico_register_common_scope_var NAME)
        if (NOT ${NAME} IN_LIST PICO_PROMOTE_COMMON_SCOPE_VARS)
            list(APPEND PICO_PROMOTE_COMMON_SCOPE_VARS ${NAME})
        endif()
    endmacro()

    set(PICO_PROMOTE_COMMON_SCOPE_VARS
            PICO_INCLUDE_DIRS
            PICO_SDK_POST_LIST_DIRS
            PICO_SDK_POST_LIST_FILES
            PICO_CONFIG_HEADER_FILES
            PICO_RP2040_CONFIG_HEADER_FILES
            PICO_BOARD_CMAKE_OVERRIDES
    )

    macro(pico_promote_common_scope_vars)
        set(PICO_PROMOTE_COMMON_SCOPE_VARS ${PICO_PROMOTE_COMMON_SCOPE_VARS} PARENT_SCOPE)
        foreach(VAR IN LISTS PICO_PROMOTE_COMMON_SCOPE_VARS)
            SET(${VAR} ${${VAR}} PARENT_SCOPE)
        endforeach()
    endmacro()

    include(pico_pre_load_platform)

    # We want to configure correct toolchain prior to project load
    # todo perhaps this should be included by the platform instead?
    include(pico_pre_load_toolchain)
endif()

[lurch]

"/picosdk/sdk" looks like a Unix-style path, but C:/Learning Projects/MS Code/blink_example_c" looks like a Windows-style path?

Are you following the instructions in https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf ?

[neurothoughtmachine]

"/picosdk/sdk" looks like a Unix-style path, but C:/Learning Projects/MS Code/blink_example_c" looks like a Windows-style path?

Are you following the instructions in https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf ?

This is for a windows 10 build using G++.

/picosdk/sdk is windows directory.
Cmake files are written in bash (but you already knew that, right).
Bash requires you to list directories as if you are using linux.

The datasheet (while it is very nicely done) only includes instructions for linux users.

I am using the following two vidtuts and info found on google ai and other random places.

https://www.youtube.com/watch?v=B5rQSoOmR5w
https://www.digikey.com/en/maker/projects/raspberry-pi-pico-and-rp2040-cc-part-1-blink-and-vs-code/7102fb8bca95452e9df6150f39ae8422

I have yet to find a complete tutorial for windows that covers everything (fresh VSC install, pico-sdk extension install/config, C++ compiler install/config, CMake install/config, tasks.json config, and settings.json config).

Every place I have been (including the datasheets and this git for the picosdk) doesn't covers everything.
Thus (a noob such as myself) is forced to piece everything together with bubblegum, string cheese and luck.

So I have no idea if these errors are from a lack of config info, a lack of complete steps, or depreciated info.

[lurch]

Cmake files are written in bash (but you already knew that, right).

Nope, Cmake files are written in CMake, which might look like Bash in some places, but is actually quite different to Bash.

The datasheet (while it is very nicely done) only includes instructions for linux users.

Huh? Chapter 2 of the Getting Started has a "On macOS and Windows" section, and Chapter 3 has a "Raspberry Pi OS and Windows" section.

I am using the following two vidtuts and info found on google ai and other random places.

https://www.youtube.com/watch?v=B5rQSoOmR5w https://www.digikey.com/en/maker/projects/raspberry-pi-pico-and-rp2040-cc-part-1-blink-and-vs-code/7102fb8bca95452e9df6150f39ae8422

Those tutorials are both from over 4 years ago! 😮 Our software setup process has moved on significantly since then. I suggest that you forget / uninstall everything you've done so far, and instead try following the instructions in the Getting Started guide to install and use the Pico VS Code extension, which automates all of the steps that you've been trying to do manually.
Once you have the basics working, you can then start applying any customisations, if needed.

[neurothoughtmachine]

Cmake files are written in bash (but you already knew that, right).

Nope, Cmake files are written in CMake, which might look like Bash in some places, but is actually quite different to Bash.

same difference. who cares. I'm not using Linux. That is the point.

use the Pico VS Code extension,

I'm already using the Raspberry Pi Pico extension
How do you think I got to this GitHub to begin with?

which automates all of the steps that you've been trying to do manually.

Really? You're telling me that Raspberry Pi Pico extension is supposed to automate the make file and all of the json.files?

Here's what I did
I did a vanilla install of visual studio code (for x86, I don't have an arm laptop)
I installed the C/C++ extension from MS
I installed the Pico VS code extension (which point you back to this github)
I installed the Cmake tools extension.
I then tried to run the example blink code and nothing happened but errors.
So I go online and learn about all these wonderful Json files and the makefile that I'm supposed to manually configure.
After installing the Pico VS code extension--the make file and Json files were blank--until I filled them in.

I suggest that you forget / uninstall everything you've done so far

I agree with you there. My install may be too muddled by now. and a fresh start might be easier.

I didn't try to specialize anything.
I don't even want to use VSCode. but I have no choice in the matter.
So I am trying to keep this as simple as I can.

I am using the following two vidtuts and info found on google ai and other random places.
https://www.youtube.com/watch?v=B5rQSoOmR5w https://www.digikey.com/en/maker/projects/raspberry-pi-pico-and-rp2040-cc-part-1-blink-and-vs-code/7102fb8bca95452e9df6150f39ae8422

Those tutorials are both from over 4 years ago! 😮 Our software setup process has moved on significantly since then.

I know that the tutorial is 4 years old.
Nearly every tutorial (text and video) on the internet is roughly four to eight years old.

The c++ extension, the picosdk, those json files and the make file seem to wrap everything up.
if somebody would paste those five files on the internet somewhere then people could copy it and at least have a clue to what is going on and how it is properly done. one simple screenshot for each would do the trick. but no one wants to do that.

It's the secret sauce no one wants to share. esp for windows.
Nobody wants to show you how they did theirs or how to fix your own. except for a few old examples on reddit and stackoverflow (the random places I referred to earlier).

The datasheet (while it is very nicely done) only includes instructions for linux users.
Huh? Chapter 2 of the Getting Started has a "On macOS and Windows" section, and Chapter 3 has a "Raspberry Pi OS and Windows" section.

I know you're trying to help and I appreciate that but please try to understand that you need to look the reference material that you are citing with such enthusiasm before citing it.
Apparently, things have changed since you last looked at it.

Go look at the reference material you are citing. go look at it.
Maybe 4 yours ago it had such information.

In fact here they are:

This is chapter 2. This is a single page chapter. I don't see anything on here about windows (except go install from here). This is linux.

This is chapter 3. This is a two page chapter. I don't see anything on here about windows other than 'no dependence needed'.

After I installed the Raspberry Pi Pico Visual Studio Code
and
the C/C++ extensions
the make file and all of the json were blank

I don't need help with vanilla installation.
I can figure that out on my own.
This is not my first SDK.
This is not my first IDE.
I am not stupid.
However, this is my first time installing MSCode, or ever seeing a makefile or a json file.
I have never cross-compiled before.
Thus far, I have only made desktop executables for windows.

I need help with the 4 Json files and the make .txt file.

Are you willing to help me with the make file and json files?

[lurch]

You're telling me that Raspberry Pi Pico extension is supposed to automate the make file and all of the json.files?

Yes, exactly.

I'm sorry to hear that you're having such trouble getting everything working. I can assure you that the Getting Started guide I linked to (which was last updated 1 year ago, not 4 years ago) works fine for the majority of Windows users, so I'm not sure where you're going wrong.
If you need more help getting the Pico VS Code extension working you could try asking for help at https://forums.raspberrypi.com/viewforum.php?f=143 or https://github.com/raspberrypi/pico-vscode