A second beta from Dgame is ready to test.
As long as dmd has nothing compareable to 'const&' I banished 'auto ref' and use the workaround: two functions, one with, one without ref.

New:
 - the Audio package (.wave, .ogg and .vorbis files are ready to use)
 - several bug fixes and overworked code.

Note that Dgame is still a beta. But as far as I can see, the next step is a stable final version.

Link: http://dgame-dev.de/

On 11 January 2013 23:57, Namespace <rswhite4@googlemail.com> wrote:

> At first: I apologize for any errors in my grammar because I'm from Germany and therefore English is not my native language.
>
> Dgame is a 2D framework for D and it is completly written in D.
> You can find the documentation, a few Tutorials and a detailed description
> on this website: http://dgame-dev.de
>
> If you found any errors or something else I would be glad for a short mail with your feedback. Thanks.
>
> P.S.: Please remember that this is only a first beta. So if some errors/bugs occur, be patient with me, and tell me about them.
>


I see no makefiles to build Dgame. :o)


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

> I see no makefiles to build Dgame. :o)

Now. ;)
But actually the needed .lib files are in the directories 'Debug' and 'Release'.
Don't forget to read this tutorial: http://dgame-dev.de/?page=tutorial&tut=installation
I should link this on the download page, also.

Am 29.01.2013 15:54, schrieb Namespace:
>> I see no makefiles to build Dgame. :o)
> 
> Now. ;)
> But actually the needed .lib files are in the directories 'Debug' and
> 'Release'.
> Don't forget to read this tutorial:
> http://dgame-dev.de/?page=tutorial&tut=installation
> I should link this on the download page, also.

─[dav1d@ArchBox][/tmp/Dgame/Release]╼ file Dgame.lib


Dgame.lib: Microsoft Visual C library

Obviously nothing you can use on Linux, a makefile would solve that, let everyone build dgame on linux on it's own

On Tuesday, 29 January 2013 at 15:00:43 UTC, David wrote:
> Am 29.01.2013 15:54, schrieb Namespace:
>>> I see no makefiles to build Dgame. :o)
>> 
>> Now. ;)
>> But actually the needed .lib files are in the directories 'Debug' and
>> 'Release'.
>> Don't forget to read this tutorial:
>> http://dgame-dev.de/?page=tutorial&tut=installation
>> I should link this on the download page, also.
>
> ─[dav1d@ArchBox][/tmp/Dgame/Release]╼ file Dgame.lib
>
>
> Dgame.lib: Microsoft Visual C library
>
> Obviously nothing you can use on Linux, a makefile would solve that, let
> everyone build dgame on linux on it's own

Ahh. That could be a problem: I hate makefiles and never wrote one.
The "makefiles" that I use are now in the .zip. But I think they are still windows only.
I would be glad if some of you could help me. Otherwise I must figure it out tonight.

Am 29.01.2013 16:10, schrieb Namespace:
> Ahh. That could be a problem: I hate makefiles and never wrote one.
Hehe,

to quote "ibuclaw":
`make no-sense`

It doesn't need to be a makefile, some kind of build-script, which automates the process of building the library. E.g. a d file which compiles the stuff for you:

rdmd build.d

On Tuesday, 29 January 2013 at 15:19:37 UTC, David wrote:
> Am 29.01.2013 16:10, schrieb Namespace:
>> Ahh. That could be a problem: I hate makefiles and never wrote one.
> Hehe,
>
> to quote "ibuclaw":
> `make no-sense`
>
> It doesn't need to be a makefile, some kind of build-script, which
> automates the process of building the library. E.g. a d file which
> compiles the stuff for you:
>
> rdmd build.d

Seems I have to edit my tutorials and my installations guide.
You have now a build script.
Thanks to aladacron, I adapted his build script from derelict.
Compile build.d and let it run. Your lib files are generated in the directory "lib/MODE" where MODE is the current mode. Compile normal and MODE is Release, compile with -debug and MODE is Debug.
The only problem is currently, that I have no experiences with GDC and LDC, so I have no idea which flags they use for debug mode. Because of that, Debug build works currently only for dmd. But I will fix this later.

Forget to say:
Because of the new build script you have now a lib file for each package of Dgame.

On Tuesday, 29 January 2013 at 16:34:15 UTC, Namespace wrote:
> On Tuesday, 29 January 2013 at 15:19:37 UTC, David wrote:
>> Am 29.01.2013 16:10, schrieb Namespace:
>>> Ahh. That could be a problem: I hate makefiles and never wrote one.
>> Hehe,
>>
>> to quote "ibuclaw":
>> `make no-sense`
>>
>> It doesn't need to be a makefile, some kind of build-script, which
>> automates the process of building the library. E.g. a d file which
>> compiles the stuff for you:
>>
>> rdmd build.d
>
> Seems I have to edit my tutorials and my installations guide.
> You have now a build script.
> Thanks to aladacron, I adapted his build script from derelict.
> Compile build.d and let it run. Your lib files are generated in the directory "lib/MODE" where MODE is the current mode. Compile normal and MODE is Release, compile with -debug and MODE is Debug.
> The only problem is currently, that I have no experiences with GDC and LDC, so I have no idea which flags they use for debug mode. Because of that, Debug build works currently only for dmd. But I will fix this later.

LDC has ldmd2 wrapper script which is used similar to dmd and GDC has gdmd (gdmd is written in perl so you need to have perl installed to run it). Those wrapper scripts support most of DMD's flags. They also have -vdmd flag, which tells the wrapper script to print out the commands that it runs. You can use that to find out which ldc2 and gdc commands correspond to a given dmd command, if you want to use ldc2 or gdc directly.

I will pause the development / completion of Dgame and generally my work with D. If D should eventually solve the const& problem (and I underline the 'if'), that would be one reason to turn back.