Those are gcc dlls probably because sfml was precompiled with gcc. If you instead included sfml source in your project and made it compile alongside your main project with the same compiler (msvc) you wouldn't have that problem. Or request the user to provide their SFML package location to CMake during configuration of your project. The user's SFML package should use the same compiler as your project. Also SFML should make their CMake scripts detected compiler discrepancy when included by 3rd parties. Honestly, this is a packaging shortcoming of C++. CMake has tried to provide facilities for this. I dunno about other package managers (conan, vcpkg etc). Other languages provide their own packaging system which supposedly takes care of this kind of dependency tracking (eg node and rust).
Your personal development environment files shouldn't be in the gitignore. Then every person that works with your project has to add files that are only related to their own weird setup to the gitignore. Instead ide specific ignores should be put in the .git/info/exclude or ~/.gitignore (no clue what the equivalent is on windows)
Even this video gives a bad template for the many developers who simply write their own Makefile. So the point is to spend a little bit of time understanding the sources of your projects and their outputs.
I use noevim(nvchad specifically) and remember i have to put my build folder into gitignore, luckily since i know my folder structure and what um sending to github, i only need to hid the build folder, (i am leaving the cmake file since it makes it easy for anyone else just to cmake .. Then cmake --build . And get the executable
Eh, googling and copy-pasting a gitignore is faster than manually stitching it together. When I encounter unwanted behaviour, I debug it like I would with any bug. Seems like a nothingburger to me.
i dont use gitignore i want people to use all of my project
no
Do you just ship built executables along with your project?
most giggachad dev
@@AWildAligned I ship my OS along with my project 😎
@@lowlevelgamedev9330 could you also ship me your pc? i'm gonna need a good one to run the project!
gitignore? what's that? *commits API key*
yess, and personal passwords 😎
I use invered gitingore:
*
!src/
etc...
basically you have to manually add a file, it prevents accidentally leaking api keys or other private stuff
for java/scala/kotlin okay) but not each language has src as place where is stored code)
@@testologin most languages u can just put all ur code in src/ or at least all except an index/main file
@@Nesdac-k1l u can put whatever u want, as u will build this sources. Just exists some standards )
@@testolog exclude it manually
this is good I will try that
Those are gcc dlls probably because sfml was precompiled with gcc. If you instead included sfml source in your project and made it compile alongside your main project with the same compiler (msvc) you wouldn't have that problem. Or request the user to provide their SFML package location to CMake during configuration of your project. The user's SFML package should use the same compiler as your project. Also SFML should make their CMake scripts detected compiler discrepancy when included by 3rd parties.
Honestly, this is a packaging shortcoming of C++. CMake has tried to provide facilities for this. I dunno about other package managers (conan, vcpkg etc). Other languages provide their own packaging system which supposedly takes care of this kind of dependency tracking (eg node and rust).
oh probably, + some audio library thing
dll files are often too big for github in my experience. I've had a few that exceeded the 100mb limit.
well not the ones I wanted to put :))
Your personal development environment files shouldn't be in the gitignore. Then every person that works with your project has to add files that are only related to their own weird setup to the gitignore. Instead ide specific ignores should be put in the .git/info/exclude or ~/.gitignore (no clue what the equivalent is on windows)
Can you please make a tutorial on Physics with OpenGL!!
i am actually working at a physics related vid
Oh nice! I would actually love to have a tutorial on that
Another option is to always build to a location outside of your project source directory.
Or just add a build folder and ignore the build folder in gitignore
@@kreuner11 That's already mentioned in the video. Not explicitly but via the gitignore entries presented in the final shot.
Even this video gives a bad template for the many developers who simply write their own Makefile. So the point is to spend a little bit of time understanding the sources of your projects and their outputs.
I use noevim(nvchad specifically) and remember i have to put my build folder into gitignore, luckily since i know my folder structure and what um sending to github, i only need to hid the build folder, (i am leaving the cmake file since it makes it easy for anyone else just to cmake .. Then cmake --build . And get the executable
I have always done it this way with my projets...I don't understand how you can use a preset tbh.
Ok I wont
Using Linux with cmake so build is the best to ignore :)
Eh, googling and copy-pasting a gitignore is faster than manually stitching it together. When I encounter unwanted behaviour, I debug it like I would with any bug. Seems like a nothingburger to me.
skill issue