Hi everyone, my name is KM. Today is September 14th, 2024, and it is 4:37 AM. Recently, I made up my mind to learn algebraic topology using Allen Hatcher's book. If you scroll down, you can find standard notations; all these notations come from theory, so we need to be familiar with them. We also have to know how to operate. Many people believe topology is abstract, but from my perspective, topology finds homotopy and homotopy type. If you read this text, you will soon find that it involves deformation or transformation because we are mathematicians. At the same time, we are engineers. 

For example, we implement complex structures using algorithms constructed with one, two, or more dimensions. My short-term goal is to study topology, and my long-term goal is to implement algorithms that allow for the deformation of polygons continuously and visually into tori. For instance, polygons with edges 1, 2, 3, 4, 5, 6, 7 need to be deformed continuously and visually into a torus with two holes. Similarly, polygons with edges 1 through 12 need to be visually deformed into a torus with three holes. 

I want to implement C++ code to deform polygons continuously and visually to visualize the deformation processes. To achieve this, we need some tools. We will install and set up OpenGL tools in my current session.

To build GLFW, pre-GLUT, or other OpenGL tools on your own, these videos will be useful. I filmed these videos in English, and also in Korean. I assume you have installed the latest version of Microsoft Visual C++. As of today, September 14, the latest Microsoft C++ version is 17.1.3. Also, go to Tools, then Get Tools and Features; Microsoft C++ must be installed as an individual component. If you scroll down, you will find the Windows 10 SDK. Try to install the latest Windows SDK. In my case, I'm using Windows 10. Probably early next year or in 2025, I will install Windows 11. As of today, I am using Windows 10. In this case, install the latest Windows 10 SDK. You have to remember that if you have installed a Windows SDK version, then you have to install it. I also assume you have installed the Intel oneAPI Base Toolkit from the Intel website. I have the latest oneAPI Base Toolkit as of today. I also assume you have installed the toolkit from the NVIDIA website. You can download the latest CUDA Toolkit. I always assume you have installed the latest development tools. After installing these tools, you have to set the proper environment variables in the Intel oneAPI. Don't miss the oneAPI; hit enter, and then you can find multiple videos on how to set up Intel oneAPI. Refer to my previous videos; I will

Works behind the scenes. This is the official guide, so this book is a must-read if you want to understand OpenGL programming. I would also recommend OpenGL. This book is also useful, just so you know. I assume you have installed the C++ library extensions in YouTube. Once again, search for C++ library extensions. Don't miss IQ 95; then you can learn how to set up C++ library extensions. If you haven't installed the C++ library extensions, you may not be able to follow my current and future sessions.

Now, scroll down. You can download OpenGL tools, all in one package. This package is very big; it is over 600 MB. I said over 600. If the internet is slow, then download all files one by one. Because I am from South Korea, I can download 600 MB with one click. Sadly, my server is located in the UK, so depending on the internet, it will take longer. If you want to be a specialist or develop your own application, then come to South Korea. South Korea provides very fast internet speed at a very low price. If my server were located in South Korea, it would take just a few minutes; since my server is located in the United Kingdom, it takes longer.

Now, I will show you how to unzip it. I will unzip this package. In the OpenGL materials folder, you can find the items. I will open the folder and arrange it

To tools in the CDEB soft folder. This folder is optional, but if you follow my videos and match the folder exactly, then you will have less trouble while following my videos. However, this folder is required; you have to unzip these files into this folder. 

Now we can try examples in this folder. Double-click it to copy the path. Open up Microsoft Visual Studio, go to File, open solution, and then find the solution file. Scroll down, and you can find the solution. Open it; we will use Debug x64. Right-click the solution properties, select Configuration Properties, and make sure to select Debug. 

Then, in Configuration Properties, select General. You have to select the latest version of Windows SDK. Select this option and click Apply. In Release, select Release; you should also select the latest installed version. Click OK. 

You should be able to build it. 59 succeeded, failed while reading the OpenGL programming guide. The OpenGL guide to OpenGL is this book. You can use the sample files in this solution, for example, right-click on Cube Map, set it at the start of the project, then press F5, either one like this, then close. 

Of course, you can examine the source code in this folder. Now go back to the solution, hit enter, scroll down, and you will find the SuperV solution. Open it, select the solution, and then select Debug. This Windows

Deb, you can find OpenGL PG9 tools in this folder. You can find Vermilion undb. We need files for OpenGL SV7 tools. If you want, you can go to this folder. In this folder, this is SP7 code. Master, from this folder, you have to copy, for example, SP7. Not in here. Go up SCB; you have to copy files. If you want, re-open the main folder, go to OpenGL tools here. Go up. 

Go to PG9 in the GL tools in the backups. Go up here. We are GLUT. Please open the folder, then you can find GLUT. Open up all we need for this project. Please right-click and set the start of the project. Right-click properties. Now select Debug in the compilation properties. General, you have to select the latest version instead of Windows 11. Then have the latest Windows 11. 

Okay, be able to build successfully. One succeeded because this is the library we only need for the time being. If the need arises, you can build other files as well. Now, release. Right-click project, only build only. Please, GL. You should be able to build successfully. Please, GLUT 3.4.0. Now go in the BC. 

Open, save all. We need SH. Go to SH properties in the release configuration. You have to select the latest version only. Go,

Myself, CY, in the beginning, you can find these tools. I built these 23 tools by myself. If you need to rebuild these files, you can use this method. For example, in our previous solution, GL and the new solution. If you want to build static, then make it set at the start of the project. We just built a static library; they usually provide static libraries. Static libraries are more secure than shared libraries, but shared libraries also have their pros and cons. When we use a shared library, we can be exposed to security problems. However, while we are building applications and managing our applications, shared libraries provide more flexibility. So depending on your needs, you can build and use either a shared library or a static library.

Now I will close it in the System C development software. We have to set environment variables for this. I collected these libraries in the B file from LIB devb. Also, release Go up, glew, lbb, x64. I collected these things in the release x64. I just wanted to help you learn how to build these things. After building, you can delete files if you need to build again. You can use the files in the back now.

In the D drive, development software tutorials, I will create a new folder called topology for quick access. In this folder, you can find advanced transform feedback and shader files. We will use these files. The properties will be explained shortly, so

Shaders are syntax-highlighted back to explain. If you open any shader files, you may notice that Microsoft IntelliSense fails to address this issue. Press Ctrl + Shift + P to select Edit Configuration. Here, we have to change the C++ standard to C++ 20. Also, open the C++ include closing. Now, back to draw.cpp. The syntax errors are gone, but this is not good enough because I set environment variables already on my machine. 

Let's explain how to proceed. We have to use C++ 20. Switch to the debug build. In case you use lowercase 2s, it should build. But I will give one more switch here: /D for debug mode. This means dynamic DLL debugging. The D stands for debugging. Hit enter when building in debug mode. We set the subsystem to DIR D. 

In debugging, we give r.exe. This is for the release build. Now, DIR.exe D is for the debugging build, while R is for the release build. In the case of a release build, R will show debugging information like this. To make it work and be able to build like this, we have to set environment variables. You also have to create a command prompt for preparing the build system. 

Building an OpenCL application is quite challenging because a number of tools are created by third parties. In the downloads section, again, for OpenCL materials, you can

In this case, we can arrange for easy reading. TVB ink is included, and some parts are repeated, but don't worry. We will start with TVB environment variables. This is for inclusion, so in the include section, you need these settings. 

Now, with TVB, you can find TVB Edit. You have to set this to x86 in the API under Program Files x86. Scroll down in the API, and in the latest include, see this folder should be specified here. Now I will cancel it. We define CLE here again. In C Edit, you can find CLE in the latest include. 

So, in this PC under Program Files x86, Intel, API, and the folder should be specified. Now we will include C++ and specify the .cpp extension. Include the browse directory in this PC, system, DB, soft, and the .cpp extension. This path should be specified here.

Now, can we specify NVIDIA? NVIDIA is defined in the system variables. Edit the PR files for NVIDIA GPU computing. This is the latest version, and you can browse in this PC under Program Files. You can find the NVIDIA CPU computing toolkit, then select the latest version 12.6. You will find the include folder here. 

Now, up to this point, we have defined NVIDIA. In MSVC, let's see here. In MSVC Edit, you can see Program Files, Microsoft Visual Studio 2022 Community, BC

In this folder, you have to select items like this: 14, 41, 3412. This is the biggest number. Latest, but this must be specified as MSBC. Now, open the tools in the PC system directory. Include this value in GL tools. Now, this one: BR. This PC system directory is DB O PG9 tools. Open GL program GUID 9. You should select this for the PC system directory, OPG Super V 7. This path should be defined. Up to this point, we have defined OpenGL. Now we need to define LIIV here in the system variables. LI should be defined; some are not defined here. This is defined. Now we have to define TVB x64 LIB here. TVB x64 LIB edit; we have to specify this path. I will show you side by side: system PR files x68 INT 1 API. Scroll down to the latest LIB. This path should be specified here. Now, we can set x64 here: C x64 LIB IT 1 API LIB. This PC system x68 IN 1 API compiler is ready. Then LIIV can be defined. Now we define OpenLIB here again. Edit and select this path: this PC system directory, Soft GL tools. We just specified this folder. Cancel, then browse this PC system directory, Soft OpenGL tools. Then LIIV, this path should be specified here. We specified all variables.

We do not have DLL files; we do not have DLL files also in this folder. These are static libraries. I think you understand how to set the NVCC environment variables with this. Sorry, I made a mistake here; you have to remove all blank spaces. This is for your reference. You have to make changes to include environment variables. I will show you once again. 

In the System Environment Variables, in the Include section, you have to define these environment variables like this; otherwise, the system may not build properly. Close it. 

Now, replace the file in the destination. If you already have this, it is in C:\Windows. Now, scroll down. You can find 2022 CCK. 

Delete this file location for x64 tools. Now, delete this like this here. Scroll down; this is the batch file. Copy this face also to C:\. If you have a blank space in your path, you have to correct it. 

Now apply. You can change it; you can select any IC. For example, I can select this GE Sbol. Okay, apply. 

You created this command front. You can delete all EXE or OBJ files. Also, like this, then /subsystem console, hit enter now; it should build. I made some mistakes; I think I made a mistake in the material. 

Here, I think I made a mistake. Sorry, I have to remove blank spaces here.

It is a confusing task. First, we have to open this command prompt again. We have to type: CD advb DIR d VJ dl.exe cl SD c++ 20 ehsc throw.cpp fe d.exe MD D. This is for the bird link system console. It should build successfully. In the console window, then R 4 release, we don't need it here. Then we can give O2 optimizations. We don't have any error messages in case there are errors. This is information. 

Now close it. You can change the size properties and font, for example, to 24, and apply it. Also, adjust the layout with B, such as 42, 30, 6 lines, and apply it. Double-click it. Now it opens with a big window. 

Now close it. You can drag and drop on your taskbar while editing videos. I found I made a mistake here; this is not a comment in the batch file. It should be rem, so this is fixed now. I can close it and copy it into Windows. 

Once again, I forgot one thing to remind you: search for edit system environment variables in the dialog box. There are two sections: user variables for username and system variables. Whenever you edit variables in this section, for example, when you make changes to any variables in the system variable section, you have to reboot your machine. 

Whenever you change a variable, don't forget

001- (SETUP) OpenGL Tools Setup

Scripts