Back to General and Gameplay Programming

HLSL and GLSL wraping again

ImoogiBG · 2015-06-21T21:42:04

I want to ask you guys, what is your approach on HLSL and GLSL wrapping. I have a solution that works, but its really ugly and really don't like it : /////////////////////////////////////////////////////// // /////////////////////////////////////////////////////// #ifdef VERTEX_SHADER @vertex-attrib float3 $a_pos a_position @vertex-attrib float2 $a_uv a_uv @varying float2 $v_uv; @uniform float4x4 g_projView; @uniform float4x4 g_world; @shader-main-begin float4 worldPos = mul(g_world, float4($a_pos, 1.0)); $vs_out = mul(g_projView, worldPos); $v_uv = $a_uv; @shader-main-end #endif /////////////////////////////////////////////////////// // /////////////////////////////////////////////////////// #ifdef PIXEL_SHADER @varying float2 $v_uv @ps-out $color 0 @uniform texture2D tex0 @shader-main-begin $color = sample2D(tex0, $v_uv); @shader-main-end #endif This is later converted to HLSL/GLSL Basically i use FCPP(really i don't recommend it) for marcos and pre-processing. and than some basic token matching + few macros. But all that $ @shader-main-begin are really awful... I really can't think of any other cleaner to basically wrap those two languages together. What do you guys do?

General and Gameplay Programming Programming

Started by ongamex92 May 17, 2015 09:10 PM

11 comments, last by ongamex92 8 years, 10 months ago

ongamex92

3,287

Author

June 14, 2015 03:31 PM

New week new update! I had a conjunctivitis and my eyes felt really tiered but I've managed to implement type deduction for the expressions. Now we can turn code form :


mat4f getm() {.....}
void f() {
    mat4f m;
    vec4f v;
    v = m * v * (getm() * v);
}

To :


void f() {
  mat4f m;
  vec4f v;
  v = mul(m, v) * (mul(getm(), v));
}

This works by traversing the tree in 3 passes:

Pass 1 - run thought all nodes and describe all the defined functions and variables.

Pass 2 - using the Information above deduce the type of every expression (a table that contains "vec multiplied by a mat is a vec", and so on)

Pass 3 - The code generation. m * v in HLSL is mul(m, v) while on GLSL is m * v

The code is still here https://github.com/ongamex/playground/tree/master/lang , but i don't recommend you to even download it.

Next week I will try to Improve the architecture and the readability of the code.
The ultimate goal of this project is not to provide a complete solution, but rather to be a simple project that has the essential functionality in it and to be extendable by anyone.

PS:

Maybe I should start a Journal or a new thread, or maybe this isn't interesting to anyone?
Or maybe I'm over-hyped.