…To allow for that i would like to have a general setup, say “max plugin” that wraps all the switches and paths and libs for the deployed versions of max and make that easy to reuse (and possibly centrally managed) in plugin projects and only add libs and other project specific stuff in the repos themselves. …especially in regards to having seperate repos and still use a central setup to support versions etc. You can quickly expose parameters that somebody can set in a GUI before building, for example for the Maya version or platform. I would think that the CMake GUI comes in handy here. A boilerplate setup for a Maya Plugin for example is even more simple and quickly done, once you got the CMake syntax.
CMAKE VS WAF .DLL
dll conversion for the typical QT tool setup is two lines, and works like a charm. I has reliefed me from dealing with the compilersettings in VS studio (which has traditionally been even worse) and creating custom build rules for automocing and. It has a steep learning curve, and i’m still at the beginning, but slowly i really start to like it. I totaly understand that I actually thought that CMake is pretty much a disease, until i lately forced myself into using it. I’m definetly not an expert on build systems, but i have very similar requirements to my development environment (Building DCC PlugIns andd small tools with C++ and Python), so i will give my 2 cents.
CMAKE VS WAF FREE
So i am looking for opinions on build systems (feel free to add to the mix!) and also hints on setting this up, especially in regards to having seperate repos and still use a central setup to support versions etc. But my milage variedĪlso i really like SConstruct and wscript files being python. But everytime i tried to use it with projects that use it it felt like a complete non-working nightmare. I have not ever used it in one of our projects. Also it seems it is not declatative as Scons is (which i found really confusing at times). It worked really well out of the box and supported windows SDK compilation really nicely out of the box including autodiscovery of compilers and creating 圆4 binaries. I just recently learned about waf (in a presentation of Avalanche Studios) and gave it a quick try. Whily i like Scons it seems to be not the best performance wise and i found some of the setup not ideal, especially in a windows world. Now so far i have dealt with the standard IDE building, Scons and recently WAF.
CMAKE VS WAF HOW TO
I am not sure yet how to best tackle that I do want the repos to be seperate per plugin.
I don’t want to buy loads of Licenses and deal with vsprops, slns, vcproj files that are different from project to project etc. I want this to run on buildslaves for nightlies, CI and deployment. I am aiming to move this away from the IDE. To allow for that i would like to have a general setup, say “max plugin” that wraps all the switches and paths and libs for the deployed versions of max and make that easy to reuse (and possibly centrally managed) in plugin projects So i would like to easy building against different host versions and (due to SDK requirements) different VC Versions (i think?) I want to make building plugins easy and quick to set up.
Mostly building application plugins (Max, Nuke, Maya) few standalone tools Other kinds of builds (py2exe, java stuff, python, potentially deployment etc) is wanted if possible I am currently evaluating build systems once again and am looking for opinions.
0 kommentar(er)
