On Saturday, 12 January 2013 at 16:34:12 UTC, David wrote:
>
> Using make with D works great, also there is cmake for D. But try to use
> two tools (d buildscript and let's say cmake) on windows. You have to
> force the user to either install mingw/cygwin or cmake/make and VS
> (cmake can only generate for mingw-make and VS not dmc). Users will end
> up not using it.
>
> stb_image e.g. is in no "OS-Package" (which also don't exist for windows)

of course makefiles work, it's just hated by so many programmers...

for windows there is 99% chance that already compiled executables/libraries exists.

and if some project doesn't have binaries for windows, it's maintainers fault, not windows. just imagine yourself compiling for example Qt or chrome on single core 2Ghz machine with 1gb ram because there is no compiled binaries, would you be happy after that?

but... we already going to OT, i don't want to start holy wars about build systems.

Am 13.01.2013 04:17, schrieb evilrat:
> On Saturday, 12 January 2013 at 16:34:12 UTC, David wrote:
>>
>> Using make with D works great, also there is cmake for D. But try to use two tools (d buildscript and let's say cmake) on windows. You have to force the user to either install mingw/cygwin or cmake/make and VS (cmake can only generate for mingw-make and VS not dmc). Users will end up not using it.
>>
>> stb_image e.g. is in no "OS-Package" (which also don't exist for windows)
> 
> of course makefiles work, it's just hated by so many programmers...
> 
> for windows there is 99% chance that already compiled executables/libraries exists.

Seems like I have ran into the 1% with all of the C projects I use.

On Sunday, 13 January 2013 at 10:47:41 UTC, David wrote:
>
> Seems like I have ran into the 1% with all of the C projects I use.

cause my pc dead i'm now also forced to use glfw on osx(cause x11-d wrapper works on linux only), now i know why you are felt to that 1%, you are trying to use unstable versions of libs which is under middle of development process. unless dev team has fully automated snapshot building system you are out of luck to get precompiled binaries of actual version O_-

Am 18.01.2013 09:13, schrieb evilrat:
> On Sunday, 13 January 2013 at 10:47:41 UTC, David wrote:
>>
>> Seems like I have ran into the 1% with all of the C projects I use.
> 
> cause my pc dead i'm now also forced to use glfw on osx(cause x11-d wrapper works on linux only), now i know why you are felt to that 1%, you are trying to use unstable versions of libs which is under middle of development process. unless dev team has fully automated snapshot building system you are out of luck to get precompiled binaries of actual version O_-

I compile pre-compile glfw for windows, but on Linux/OSX etc. I have it as submodule and it works fine! :)

On Saturday, 19 January 2013 at 15:32:46 UTC, David wrote:
>
> I compile pre-compile glfw for windows, but on Linux/OSX etc. I have it
> as submodule and it works fine! :)

works for me too, but this is sad that i need to use 3rd party libs just to create render window and handling input(well, it's possible to create cocoa window using plain c, but that would require some time which i don't have right now) :(