We are using the SDK 2.1 and we see that under WinXP we still need to have a console window. If not, the SDK will open 3 console windows and then close them just after.
Could you please explain? In which app are you seeing the console windows?
I just commited a post, "DOS Shell poping up on clBuildProgram", addressing the same problem. I think shell pops up on the call to clBuildProgram. It has been the same under the 2.0 sdk.
OpenCL Studio (www.opencldev.com)
That's right, it sounds that it is related to clBuildProgram...
Yes, the same happens to me.
Each time I call clBuildProgram a MS-DOS console window appears. I think it's because ATI is calling the OpenCL compiler from the command line instead of invoking it from a DLL.
Pls, fix it. Looks not very professional.
Will this be fixed in the next release? This issue has been frequently reported against the past two releases.
If it's being delayed because the frontend is moving to be in process, perhaps a stopgap would be to make a version of clc.exe that is not a console application but instead a windowed application with no window. (like javaw.exe vs java.exe if you are familiar with Java on Windows)
Given all the other advances that have been made I think it's remarkable that this hasn't been addressed yet. Second to the lack of an end user runtime this is probably the most important "outside the spec" problem with the StreamSDK.
The lovely console window still pops with the SDK 2.2....
Originally posted by: MicahVillmowThis is something we are in the process of working on. The problem is stemming from the fact that clc.exe, our frontend, is ran out of process, causing the popup window.
Retrieving data ...