![]() Ok a small update for those who are interested. If possible I'd like to be able to do it with the standard suite of VS command line tools. I don't want to have to manage a separate script file, as I want to be able to add/delete shaders at a whim and not have to worry about keeping a script file up to date. Then of course be able to load these files at run time. cso files from a given directory and append them to the executable. What I'd like to do is to be able to, in a post-build step (perhaps pre-link, perhaps post-link, either is fine) be able to take all the. resource file which is then linked in with the linker. The first option that came to mind was to somehow use the Resource compiler (rc.exe) to bundle the shaders in, but it seems rc.exe requires a resource script, and churns out a. ![]() cso files into the executable so that I don't need to worry about losing them, or mess with versions (sometimes debug shaders are a bit different than release shaders to make it easier to track errors, things like that), and just keep things neat and tidy. cso files, which I load manually at run time. Right now all my shaders are compiled through visual studio to. I'm using VS2012 'I'm broke'/express edition. I've been working on, what has become, a relatively large project with a large number of shaders.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |