Homebrew Visual Studio req squiggly lines?

[T3GZdev]

hi so far iv always used programmers notepad for ds/dsi(libnds) & some 3ds/new3DS(libctru) stuff.
iv been looking into using visual studio 2017 because im using that alot this semester.

i was previously having problems but have since found a fix. the problem i was having is in the spoiler. the fix is below.

Spoiler

i'm having problems? for example starting a 3ds or ds homebrew with visual studio.
im using this link for reference.
https://wiki.gbatemp.net/wiki/3DS_Homebrew_Development
"scroll down to the Visual Studio part"
i did steps #1 through #7 adding devkitarm & libctru(libnds if im making ds homebrew)

things compile but the red squigglies wont go away.

so i iv found a fix for this as of 10/16/17 that works for both DS(libnds) & 3DS(libctru) homebrew.
so following the instructions here(with some edits in): https://wiki.gbatemp.net/wiki/3DS_Homebrew_Development

1) File > New > Project From Existing Code...
2) choose Visual C++ & click Next.
3) Project file location, navigate to your projects folder. Enter a name for the project & click Next.
4) Use external build system, click Next.
5) Build command line: make
Clean command line: make clean
Output: "name of game".(3dsx if 3ds or .nds if ds)
Click Finish.

6) Right click project (in the solution explorer) > properties...
7) Under NMAKE > preprocessor definitions clear everything, click ok.
go back into NMAKE > add the devkitARM & ctrulib locations to preprocessor definitions (change if needed):

C:\devkitPro\devkitARM\include
C:\devkitPro\libctru\include

Click OK


suddenly it works?

 

[RocketRobz]

Ignore the red squiggles, lol.

 

[elhobbs]

for the project properties
VC++ Directories: clear everything (including the inherit from parent checkbox) except Executable Directories.
NMake->Preprocessor Definitions: ARM11;__STDC__;_3DS
NMake->Include Search Path: add the directories for devkitarm, libctru, etc.
this is what I use (probably needs to be updated for newer devkitpro releases, but you should get the idea)

$(ProjectDir)include;C:\devkitPro\devkitARM\arm-none-eabi\include;C:\devkitPro\devkitARM\lib\gcc\arm-none-eabi\6.3.0\include;C:\devkitPro\devkitARM\arm-none-eabi\include\c++\6.3.0;C:\devkitPro\libctru\include;C:\devkitPro\portlibs\armv6k\include

create a include file that you add before all other includes and add this:
#ifdef _3DS
#undef WIN32
#endif

#ifdef __INTELLISENSE__
#define __attribute__(...)
#endif

 

[T3GZdev]

hi sorry for the late reply, i the things from hobbs. but it still shows.
also edited original screenshot from 1st post. was wrong screenshot.
ifyou want i can zip a copy of it

 

[elhobbs]

hi sorry for the late reply, i the things from hobbs. but it still shows.
also edited original screenshot from 1st post. was wrong screenshot.
ifyou want i can zip a copy of it

you did not quite follow the directions. here is a sample project - it is configured to use the current versions of devkitarm and libctru - installed to the default location (ie c:\devkitpro). make sure you extract the zip contents to an empty folder (make sure there are no spaces anywhere in the folder name or path).

 

[T3GZdev]

sorry for the late reply but i actually found a fix that doesn't require the extra file.
i will be updating the original post in a sec.
edited:^

 

[elhobbs]

sorry for the late reply but i actually found a fix that doesn't require the extra file.
i will be updating the original post in a sec.
edited:^

Does the go to definition/right-click functionality work correctly? I tried something similar to this in the past and it would end up using the windows versions of the files.
I want to say the separate file was only needed for .c files - .cpp files were not a problem. I did see a different solution somewhere for .c files that made intellisense parse them like c++ files but I don’t remember where I saw it.
I have not had a chance to try your latest edit, but I will later this evening.

 

[T3GZdev]

Does the go to definition/right-click functionality work correctly? I tried something similar to this in the past and it would end up using the windows versions of the files.
I want to say the separate file was only needed for .c files - .cpp files were not a problem. I did see a different solution somewhere for .c files that made intellisense parse them like c++ files but I don’t remember where I saw it.
I have not had a chance to try your latest edit, but I will later this evening.

yes go to appears to work.