Post by BlueMagnificent on Aug 1, 2014 2:11:16 GMT 1
Good Morning and happy new month to all.
I just thought of giving a brief information on the compiler of choice for our humble project DARKDOVE, most especially on the windows platform. The good news is that any compiler that can properly build Urho3D and all of its Sample Application is totally allowed and can be used in development. But this can only be so as long as the code is compatible across every other compilers, by that I mean using standard C++ syntax, semantic and constructs of instead of compiler specific ones. The aim here is for every code to be easily compilable on all compilers being used for development without modification (or with minimal modifications if need be).
So as said earlier so long as the compiler can build Urho3D and the Sample Applications, and So long as the Sample Applications can run without problem, then the compiler is good to go.
I have two Urho3D libraries, one built with Microsoft Visual C++ Express Edition 2010 and the other with MinGW-w64. Currently I use the MinGW-w64 build so MinGW-w64 is my compiler of choice
.
NOTE
The reason for this liberality in the choice of compiler is not that there is no agreement on the choice of compiler to use, but to leverage the diversity of the used compilers for code testing since the users who might want to build the game from source would be using any compiler at their disposal.
I just thought of giving a brief information on the compiler of choice for our humble project DARKDOVE, most especially on the windows platform. The good news is that any compiler that can properly build Urho3D and all of its Sample Application is totally allowed and can be used in development. But this can only be so as long as the code is compatible across every other compilers, by that I mean using standard C++ syntax, semantic and constructs of instead of compiler specific ones. The aim here is for every code to be easily compilable on all compilers being used for development without modification (or with minimal modifications if need be).
So as said earlier so long as the compiler can build Urho3D and the Sample Applications, and So long as the Sample Applications can run without problem, then the compiler is good to go.
I have two Urho3D libraries, one built with Microsoft Visual C++ Express Edition 2010 and the other with MinGW-w64. Currently I use the MinGW-w64 build so MinGW-w64 is my compiler of choice
.NOTE
The reason for this liberality in the choice of compiler is not that there is no agreement on the choice of compiler to use, but to leverage the diversity of the used compilers for code testing since the users who might want to build the game from source would be using any compiler at their disposal.
