Homebrew Misc cannont find calico.h devkitpro error in vscode

[a_kid_named_finger]

every time i've include libnds throws an error vscode says its the include path but I have configured correctly devkitpro paths in settings.json and cpp_propeties.json and cannont find calico.h, idk how to fix it

 

[draftguy123]

Can´t help with vscode but did you install calico?

pacman -S calico

The path on my system is \devkitpro\calico\include\calico.h

 

[a_kid_named_finger]

Can´t help with vscode but did you install calico?

pacman -S calico

The path on my system is \devkitpro\calico\include\calico.h

i reinstalled calico lib and added to include the path, didnt work

 

[draftguy123]

i reinstalled calico lib and added to include the path, didnt work

Does the project compile in the msys environment terminal with make?
(Depending on your setup, e.g the compilers etc are installed)

I can`t help with vscode, I don´t use it.

Maybe this thread helps...
https://gbatemp.net/threads/setting-up-visual-studio-code-for-libnds-and-devkitpro.615121/

 

[a_kid_named_finger]

Does the project compile in the msys environment terminal with make?

nop i use the powershell terminal to compile

 

[StellarRaccoon]

Did you ever figure out this issue?? I followed the above thread, but calico.h still cannot be opened.

 

[JORGETECH]

As far as I'm aware, libnds as we knew it is being phased out or refactored into some sort of Real-Time Operating Sytem known as Calico, such RTOS manages everything libnds managed before, of course. This means some projects will need to be adapted for such changes.

I noticed this since I've had some problems compiling GBABF with the latest devkitPro toolchain, the errors pointed to Calico headers. For the time being, the solution I adopted was to install an older version of the devkitPro toolchain before those changes, luckily, user Leseratte maintains old versions here: https://wii.leseratte10.de/devkitPro/

I can't help with Windows and VSCode since I use Linux (and I compile using the terminal), but I guess you could extract the toolchain somewhere and change the paths in the project or something.

EDIT: After reading some more, it would be more correct to say newer versions of libnds adopted Calico as it's core, which is a low level layer that has RTOS-like capabilities.

 

[StellarRaccoon]

I noticed this since I've had some problems compiling GBABF with the latest devkitPro toolchain, the errors pointed to Calico headers. For the time being, the solution I adopted was to install an older version of the devkitPro toolchain before those changes

Thank you for the tip of using an older devkitpro. I found a thread on r/NDSHacks that recommended a older devkitpro 3.0.3 installation that includes NFlib and without the calico requirement (sorry, I cant add the link as a newbie) I was able to get the examples running smoothly. I will definitely stick with this older version as I learn

 

[pansy_thoughts]

Thank you for the tip of using an older devkitpro. I found a thread on r/NDSHacks that recommended a older devkitpro 3.0.3 installation that includes NFlib and without the calico requirement (sorry, I cant add the link as a newbie) I was able to get the examples running smoothly. I will definitely stick with this older version as I learn

you could use BlocksDS too. I had a ton of issues trying to get nflib to work using devkitpro and devkitARM, since as much as I modified the makefile to include nflib and such, it just wouldn't work (couldn't even compile the raw examples lol), and at the end the solution for me was to pretty much discard it and use BlocksDS with Wonderful Toolchain.

 

[StellarRaccoon]

you could use BlocksDS too. I had a ton of issues trying to get nflib to work using devkitpro and devkitARM, since as much as I modified the makefile to include nflib and such, it just wouldn't work (couldn't even compile the raw examples lol), and at the end the solution for me was to pretty much discard it and use BlocksDS with Wonderful Toolchain.

I spent 2 days trying to get devkitpro set up, got this running in an hour! Seems like this is the way to go if you are getting started!