Cause its dead simple. Shell out, run a quick sed or something, then compile it in. It is quite amazing what 'magic meta' stuff you can do with that shit. Meanwhile 10 years in we are finally getting reflection.....
Man that aucks was looking forward to some kind of speed improvement. Using magic enum atm and I guess we'll continue to do so.
C++ build times are hard pill to swallow when migrating from c. This is just another reason we'll probably stick to writing c as t the company where I work. It's like asking someone to give up instant compilation for cleaner easier to read apps?
Also now that we have cleanup handlers in c (destructors) even less of a reason to move...
My well being is judged now by whether I took the time to watch a movie with my daughter, take my son out to fly a rc plane and so forth... so easy to dig into the daily grind ... not sure what life is about but I sure a shit know misery it born from abandoning your kids and the sickness that brings inside is insidious.
If I do nothing both will be in their rooms all day. Makes me sick.
> For example, Cmake can use vcpkg to install a package but then I still have to write more cmake to actually find and use it.
I have this solved at our company. We have a tool built on top of vcpkg, to manage internal + external dependencies. Our cmake linker logic leverages the port names and so all you really do is declare your manifest file (vcpkg.json) then declare which one of them you will export publicly.
Everything after that is automatic including the exported cmake config for your library.
reply