Change Details

When doing a release build, the visual studio solution will currently have 151 sub projects, all listed in a giant list, finding what you are looking for is getting kinda annoying. this patch will enable the generation of subfolders, so the project structure in the solution explorer will follow the directory structure on disk . Turning this: {F774764} into this: {F774765} There's a couple of problems though, cycles does not use blender_add_lib nor is there a macro's file I can hook into. So they all end up in the root folder. There's a couple of places we can fix this 1) just hardcode solution folder in each of cycles libs cmakelists.txt 2) add a cycles_add_library macro and duplicate the code from macros.cmake there. Cycles standalone will not have the USE_FOLDERS global set, so nothing will change there. 3) Just leave the cycles projects in root. any opinions here?

When doing a release build, the visual studio solution will currently have 151 sub projects, all listed in a giant list, finding what you are looking for is getting kinda annoying. this patch will enable the generation of subfolders, so the project structure in the solution explorer will follow the directory structure on disk . |Turning this:|Into this:| |{F774764}|{F774765}| There's a couple of problems though, cycles does not use blender_add_lib nor is there a macro's file I can hook into. So they all end up in the root folder. There's a couple of places we can fix this 1) just hardcode solution folder in each of cycles libs cmakelists.txt 2) add a cycles_add_library macro and duplicate the code from macros.cmake there. Cycles standalone will not have the USE_FOLDERS global set, so nothing will change there. 3) Just leave the cycles projects in root. any opinions here?

When doing a release build, the visual studio solution will currently have 151 sub projects, all listed in a giant list, finding what you are looking for is getting kinda annoying. this patch will enable the generation of subfolders, so the project structure in the solution explorer will follow the directory structure on disk . |Turning this: {F774764} into this: |Into this:| |{F774764}|{F774765}| There's a couple of problems though, cycles does not use blender_add_lib nor is there a macro's file I can hook into. So they all end up in the root folder. There's a couple of places we can fix this 1) just hardcode solution folder in each of cycles libs cmakelists.txt 2) add a cycles_add_library macro and duplicate the code from macros.cmake there. Cycles standalone will not have the USE_FOLDERS global set, so nothing will change there. 3) Just leave the cycles projects in root. any opinions here?