Making and Working with Libraries in C++ (Multiple Projects in Visual Studio) 

Dogecoin

Tudor Lechintan he doesn't like exception handling, and I agree, exception handling is stupid.

we dont want to make exceptions xD

3 important commands: -try -throw -catch

@@shpresimmuja467 why ? They can be very useful

Jose A he already did those

lol yes of course there will be more videos, it hasn't even been two weeks, relax :)

I'm relaxing. Sorry for hurrying you. I've just noticed that between each other vids there has been less than a week between them, sometime there were a new vid everyday. I was just curious. :'D

This is a really late reply, and probably not helpful anymore, but a couple of things to mention here. For the "customer", they won't notice. These are static libraries here, which means that when the application gets compiled they essentially become a part of the executable. So, you just give the "customer" the executable file, and it should just work. However, if you give the actual code to someone, things are a bit different. No, there is no makefile, because this is using the VC++ compiler, and all of these settings are stored inside the "vcxproj" file, so, if they have Visual Studio, and you give them the whole folder containing the "sln" file, all of the settings will transfer over. But, of course, they need Visual Studio. You could make a makefile yourself if you want.

Yes it was veri helpful. Appreciation from India

thanks a lot man

did you find a solution for this?

Not exactly. The compiler does not care about naming, naming is only useful for us people. So if you don't include Engine.h inside Engine.cpp, then the function declaration inside Engine.h could be treated as a completely different function from the one inside Engine.cpp. For this reason some compilers even throw an error when you define a previously undeclared top level function in a program that's not meant to be executable.

Wally Nut how do you even compile the code with simple text editors

Hi, sorry for the very late reply, I'm sure you'll have all figured it out by yourself by now, but maybe it will be useful for someone in the future. I was in your same situation because I am on Ubuntu and I decided to go raw with just notepad and g++. So I made some research and came up with something. This is for linux + notepad + g++ though, idk about windows, maybe there's something analogous: First, I tried to replicate the filesystem like this: engine/ |_ engine.h |_ engine.cpp game/ |_ application.cpp I then positioned myself in the engine directory: 1 - I generated the object file from engine.cpp > g++ -c engine.cpp After this, engine.o file should pop up in the directory 2 - I created the library file from the object file using linux's command for creating static libraries, ar > ar rsv engine.a engine.o After this, engine.a file should pop up in the directory, which is the actual library file 3 - I then positioned myself in the game directory > cd ../game 4 - Finally I compiled application.cpp linking it to the library. The parameters are: -I : (capital i) the relative / absolute path for inclusion of the header file (similar to what he did around 6:06), in our case it's the engine directory -L : the relative / absolute path to the library file (similar to what he did around 8:00), in our case it's the engine directory -l : (lowercase L) the name of the library file, in our case it's engine.a > g++ -I ../engine application.cpp -L ../engine -l:engine.a After this, the executable a.out should pop up in the directory and do whatever is in the main() function I used relative paths because I don't need it to be "a stable setting" since there's nothing automated in here.

Um, no. For C#, you would have to use a DllImport on a DLL file, which is a DYNAMIC library, in this video, he describes how to use STATIC libraries... Static libraries don't and physically can't exist for C# since it's practically interpreted after it's compiled to IL. So, technically, if you choose DLL in the list instead of LIB when he changed the project's properties, then added a C# project to the solution, set the build dependencies and set the library to copy to the C# bin directory, and used "DllImport" attributes within the C# code to access things in the DLL, then, yes, you could. Just not QUITE in the way he showed it.

Did you get an answer? I'm thinking about it too...

if you are having this error while you right click and building your application.cpp.... just Ctrl+F7 instead of right-click build You can successfully build your Game project.

Late answer but, When he typed it and ran the program, it recompiled automatically then ran the instructions of the program

Compiler