The CLGLInterop example however still just gives a black window. It
only outputs the FPS in cmdline.
Well it works fine on my Win7 x64 machine.
Those guys do know how to create useless exception messages o.O
Well can't investigate this further at the moment.
On Tue 10-Jan 3:29, Trass3r wrote:
Does this one work?
http://www.cmsoft.com.br/index.php?option=com_content&view=category&layout=blog&id=99&Itemid=150
Simply running the bin/Debug/CLGLInterop.exe included in the zip produces
** Exception Text **
Cloo.BuildProgramFailu
Does this one work?
http://www.cmsoft.com.br/index.php?option=com_content&view=category&layout=blog&id=99&Itemid=150
The CLGLInterop example however still just gives a black
window. It only outputs the FPS in cmdline.
any error messages?
compile it in debug mode with -debug -g.
None that I can see.
Hmm I'm not sure if I ever tested the code on Windows. The
version(Windows) stuff looks ok though.
I guess o
On Tue 10-Jan 1:23, Trass3r wrote:
The vectorAdd example works perfectly, without any editing (ie.
without removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO)).
How strange, does pragma(msg, CL_PROGRAM_STRING_DEBUG_INFO); give
different results for the two dmd revisions?
The CLGLInterop example
The vectorAdd example works perfectly, without any editing (ie. without
removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO)).
How strange, does pragma(msg, CL_PROGRAM_STRING_DEBUG_INFO); give
different results for the two dmd revisions?
The CLGLInterop example however still just gives a black
On Mon 09-Jan 23:39, Klyn wrote:
On Mon 09-Jan 14:24, Trass3r wrote:
Well, I resorted to using bud and managed to get the vectorAdd example
to compile, but when I run I get this error:
btw, bud's not maintained anymore.
Is this some kind of \ vs / bug?
Try removing the mixin(CL_PROGRAM_STR
On Mon 09-Jan 14:24, Trass3r wrote:
Well, I resorted to using bud and managed to get the vectorAdd example
to compile, but when I run I get this error:
btw, bud's not maintained anymore.
Is this some kind of \ vs / bug?
Try removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO) ~ @ vectorAdd.d(36
Well, I resorted to using bud and managed to get the vectorAdd example
to compile, but when I run I get this error:
btw, bud's not maintained anymore.
Is this some kind of \ vs / bug?
Try removing the mixin(CL_PROGRAM_STRING_DEBUG_INFO) ~ @ vectorAdd.d(36)
On Mon 09-Jan 2:45, Trass3r wrote:
Ok, so when i try to compile it says
src\opencl\c\cl_d3d10.d(88): Error: undefined identifier UINT
src\opencl\c\cl_d3d10.d(96): Error: undefined identifier UINT
and upon changing those to uint I get
src\opencl\c\cl_d3d11.d(77): Error: undefined identifier ID3
Ok, so when i try to compile it says
src\opencl\c\cl_d3d10.d(88): Error: undefined identifier UINT
src\opencl\c\cl_d3d10.d(96): Error: undefined identifier UINT
and upon changing those to uint I get
src\opencl\c\cl_d3d11.d(77): Error: undefined identifier ID3D11Buffer
src\opencl\c\cl_d3d11.d(84
On Mon 09-Jan 0:05, Trass3r wrote:
About the 'mentioned bugfix', I assume you're referring to "bug 6473
has been fixed => so let's fix that memory leak"?
Yep, just git checkout the revision before that one.
Ok, so when i try to compile it says
src\opencl\c\cl_d3d10.d(88): Error: undefined i
About the 'mentioned bugfix', I assume you're referring to "bug
6473 has been fixed => so let's fix that memory leak"?
Yep, just git checkout the revision before that one.
On Sun 08-Jan 22:53, Trass3r wrote:
I'm trying to use cl4d, but when I compile I get a stack overflow..
Sigh.
As I stated in the announcement you need a HEAD dmd.
Or use a cl4d revision prior to the mentioned bugfix.
Oh I think I now get what you mean by HEAD dmd: the latest version on
githu
I'm trying to use cl4d, but when I compile I get a stack overflow..
Sigh.
As I stated in the announcement you need a HEAD dmd.
Or use a cl4d revision prior to the mentioned bugfix.
On Fri 30-Dec 10:00, Stephan wrote:
On 29.12.2011 13:31, Trass3r wrote:
On Thursday, 29 December 2011 at 10:32:49 UTC, Extrawurst wrote:
nice work. why moved to github ?
I'm sick of having to switch from git to hg commands every time I work
on cl4d.
So I converted it to git, cleaned up the hi
On 29.12.2011 13:31, Trass3r wrote:
On Thursday, 29 December 2011 at 10:32:49 UTC, Extrawurst wrote:
nice work. why moved to github ?
I'm sick of having to switch from git to hg commands every time I work
on cl4d.
So I converted it to git, cleaned up the history and just put it on
Github cause
On Thursday, 29 December 2011 at 10:32:49 UTC, Extrawurst wrote:
nice work. why moved to github ?
I'm sick of having to switch from git to hg commands every time I
work on cl4d.
So I converted it to git, cleaned up the history and just put it
on Github cause it has nicer features.
btw. with
On Thursday, 29 December 2011 at 09:48:54 UTC, mta`chrono wrote:
hey that's cool. thank you for your effort. what about moving
this to deimos?
Remember this is a wrapper, not only a binding.
What would be the merit of outsourcing the binding?
nice work. why moved to github ?
btw. with dmd2057 and the -property flag it does not build anymore.
Stephan
On 29.12.2011 02:18, Trass3r wrote:
I finally moved cl4d to https://github.com/Trass3r/cl4d
It's in a very usable state. Contains 2 samples including an
OpenCL/OpenGL interop one simil
hey that's cool. thank you for your effort. what about moving this to
deimos?
- mta`chrono
I finally moved cl4d to https://github.com/Trass3r/cl4d
It's in a very usable state. Contains 2 samples including an
OpenCL/OpenGL interop one similar to
http://www.youtube.com/watch?v=K1FOIhA6ecQ
btw, as of my latest commit you need a HEAD dmd to build it. This
fixes a severe memory leak.
23 matches
Mail list logo