Click here to Skip to main content
15,888,271 members

Comments by Phoenix Liveon (Top 40 by date)

Phoenix Liveon 19-Jul-22 7:38am View    
Thanks, noted.
Phoenix Liveon 19-Jul-22 6:32am View    
Thank you!
Phoenix Liveon 19-Jul-22 5:56am View    
OK... So... C-language, technically do not support polymorphism? But there must be a proper/correct way? For now I will try to get enough enough information about these pre-define c++ casting operation. And thank so much again.
Phoenix Liveon 19-Jul-22 5:44am View    
Hi, @CPallini, first of all THANK YOU VERY MUCH, I know this is a sufficient/effective solution, but is there a premitive/c-style casting way of doing it? For educational purpose, I'm eager to know what its look like.
Phoenix Liveon 28-May-22 5:38am View    
Oh! It is a MACRO way of initializing/building things, it is for linking either 'dynamic' and 'static' libraries into your project using a 'toolChain: MSVC-2019 | n >=1926' and we could provide two separate sets of specific lib for DEBUG or RELEASE.

I'm really grateful for this wonderful informative solutions; this is really new to me, because I rarely read this type of pre-processor script, because if it gets bloated, it takes time to read it, but once we're done reading it, it's really easy to follow up and also just don't mind the pre-define MACRO, it is one of the main reasons I don't want to read it is that trailing those pre-defined MACROS is quite painful work of arts.

However, it is an alternative solution to my problem of looking for a Gradle build script and by using a kotlin domain specific-language. The core problem is how do we properly utilize these Gradle plugins; "cpp-application" with its features such as buildtypes and flavor extensions?

PS: double-check; can we include/push your solution within a (PCH) PreCompiled Header?