Archives Discussions

[drstrip]

I've created a new project by copying one of the examples. This project is NOT in the directory tree containing the examples. I've copied the .vsprops files to my project directory and edited the .vsproj file to point to the right place so that it will load. When I attempt to build this project, the compile and link work fine, but the post-build custom step fails because it is trying to copy the <project_name>.cl file to the CL directory defined by a relative path in the samples tree. Of course, in my case this path is not valid.

Two questions:

1. I've never played with custom build steps before and can't find where it's defined in the project. As far as I can tell, it doesn't appear in the project properties, it doesn't appear in .vsprops pages, and it doesn't appear to be defined in a .rules file, since I can't seem to find any in the entire ATI tree.  So, where is this post-build rule to be found?

2. And do I really need it? Is this just a hack in the samples to simplify searching for the .cl file in the sample code?

Thanks

[drstrip]

Not sure how I kept missing the Build Events tab and kept moving on to the Custom Build Step tab. So, I've found the event.

Now I just need to know if there is any compelling reason to do the copy.

[omkaranathan]

Presently you must have the source code to build your OpenCL program. This  means the .cl file is required to be at the place where executables are, or you have to modify your .vcproj file to look at the place where .cl file is present.