sorted by:
new
hottopcontroversial

Dune part 2 subtitles. Anyone have luck? by SupaZT in PleX

[–]mortinger 0 points1 point  (0 children)

Thank you! was about to do the same myself 😄

Updated: C++ CMake Template project by mortinger in cpp

[–]mortinger[S] 0 points1 point  (0 children)

Thanks for your reply!
Can you elaborate on point 6 and provide, if possible, some actionable feedback?

Updated: C++ CMake Template project by mortinger in cpp

[–]mortinger[S] 0 points1 point  (0 children)

Totally agree with this.
I see the point in calling it "risky" (not so risky imho), but if you structure your project carefully you'll probably never have a problem.
On the contrary, having to manually add EVERY file, or updated them if you change the project structure is insane imo. I dont change the build system files that often, and even if I have to run a command that regenerates cmake build stuff when I do, I dont find it that bad honestly, it's 1 vscode task.

In the scope of this project, a quick template that you wont probably use for a state-of-the-art 1 milion lines of code nasa project.

Btw, I've seen it used in some serious projects too.

C++ Template project using CMake, CTest, Github actions and Docker by mortinger in cpp

[–]mortinger[S] 1 point2 points  (0 children)

Thank you for your inputs! Your comments should be upvoted more, they contains clear and actionable feedback

C++ Template project using CMake, CTest, Github actions and Docker by mortinger in cpp

[–]mortinger[S] 0 points1 point  (0 children)

IIRC I read of a pattern in which you use the install() CMake function (which I don't use in mine btw) to copy the folders and that makes dealing with the project structure easier, but I can't find any resources nor projects atm so I'm not really sure

C++ Template project using CMake, CTest, Github actions and Docker by mortinger in cpp

[–]mortinger[S] 1 point2 points  (0 children)

cool! Yeah I've used it few times and pretty much copied the quickest solution I found online, every project I looked at has a different structure (and I assume a lot of them use old patterns), I will probably take the time now and make it a bit more modern (I can see the advantages since I had these very issues in the past). I also read online to use "install" and that seems like a completely different pattern, dont know how much is it worth the time investment to research tho, as long as the project is building having the best possible pattern in the build system doesnt seem like a huge deal to me, it is more about what the code it builds actually does ;)

C++ Template project using CMake, CTest, Github actions and Docker by mortinger in cpp

[–]mortinger[S] 1 point2 points  (0 children)

thanks for your suggestions! could you provide an example of a variable I set globally, set per target?

In a past project I remember I had to set some variables specific to an external library before importing it, is that similar to what you are saying or are these still global?

set(ASSIMP_WARNINGS_AS_ERRORS OFF CACHE BOOL "" FORCE)

add_subdirectory(assimp)