Ncurses 3D render engine: pt 1 (Getting started)

In this video, we covered how to setup the work environment for this project. Created the makefile, the defs and and ncurses window.
make sure to leave a like and subscribe
Link to github: github.com/lun...
1. install ncurses
2. install xterm (its the fastest terminal for ncurses)
3. copy and paste makefile

[@orrinbarabor1387]

I was looking to make a 3D engine using ncurses and I stumble across you. Thank you for the tutorials!

[@KayOScode]

Glad I could help!

[@Syrillios]

I remember seeing your original video around the beginning of the year & remembered it again today, just to see you're working on the tutorial. awesome!

[@xvit]

10:00 I believe you can also simply enter "reset" to re-initialise the terminal with reset(1) if it gets messed up.

[@xvit]

I congratulate you for returning to a project after a significant break. What matters is that it gets made at all, and we get the content, done well. Other people may have (mistakenly) thought well, it's an old idea, or old news now... That's not true, and doesn't matter anyway! The internet, done right, is a place to _collaborate and contribute, across time, across generations_. If we (or google) don't screw this up, people will be watching this in 100 years, when C (and probably curses), will still be relevant. The 1 year gap between videos won't matter then. Hi to those future programmers! Sorry about global warming. I tried. /massive tangent

[@kawsper]

Thanks for making this.

[@TheGruselmops]

Awesome! Respect for making this series after all! noecho() prevents your input from showing up on the screen right? Would be great, if you'd explain all the functions you use. cheers

[@KayOScode]

Thanks for the feedback, Ill go into more detail for future videos although we probably wont be using very many more external functions for the rest of the project.

[@JohnAlamina]

Thanks for the awesome tutorial. What editor are you using please?

[@KayOScode]

Thanks for viewing! The editor is vim, a command line editor for linux. It can be used in windows with wsl, or even something like cygwin. Ever since I started using it, I havent been able to go back

[@ignacionr]

so... in all these years you probably already learned this, but by doing this single include defs.h you do, you are making every part of your program depend on every dependency; that locks each part of your program into your full program, which isn't really a good thing...

[@KayOScode]

@@ignacionr yes, for any project more than a few thousand lines, I would never use a defs.h file. For small ones, the benefit is you get to have all your dependencies in one convenient place and you know all your sources have them

[@ignacionr]

@@KayOScode hmmm I disagree, but it only goes to showing that there's no one way but mainly prefferences. Your job is great and shows good taste, well done!

[@ignacionr]

make understands CXX for the C++ compiler, you shouldn't change CC; same for CXXFLAGS instead of CCFLAGS

[@KayOScode]

@@ignacionr makes sense, this project was originally in c, so some parts definitely have c roots that may or may not have been fully adapted

[@kumurukecc1604]

I have to use -ltinfo on my computer for some reason :/

[@KayOScode]

Im not entirely sure why that would be necessary. What os are you on?

[@kumurukecc1604]

I'm on Gentoo, and when I don't do it, g++ says "undefined reference to 'stdscr'" and "error adding symbols: DSO missing from command line" I'm not very sure, what that means :/

[@KayOScode]

@@kumurukecc1604 yeah, figured you were on gentoo. For whatever reason, I think its the way ncurses is installed, it needs tinfo

[@electronicwoe]

5:32 16 bit and *18* bit integers? Lol

[@KayOScode]

LOL

[@electronicwoe]

Lunatic Programmer I wasn’t aware of the int18_t :p