Structuring a plugin project??



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 10/02/2010 at 09:12, xxxxxxxx wrote:

    Hey there,
    i was wondering how you put structure into your plugin developement. how do you keep your different solutions updated, for example if you create something for r11 and r11.5

    i am struggling a bit here, since it happens sometimes that i add something to my r11 source code and later i find that i didnt update the r11.5 version accordingly. specially when there are compiling issues for the mac versions i go crazy

    so, what do you do to avoid such cases?? or is this simply a question of routine?

    thanks and cheers,
    ello



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 16/02/2010 at 05:58, xxxxxxxx wrote:

    I have one code for all versions sitting in my repository (subversioned). I use the code in all versions, so if I change something it changes it for all versions. I use preprocessor definitions to keep it version safe.


Log in to reply