Using uname to get OS platform gives inconsistent behavior about haywire HOT 7 CLOSED

Can you try this command from the Haywire directory?

".\bin\win-bash\uname.exe"

If I use the win-bash version directly on Windows it should report the proper value. Then Haywire builds aren't subjected to anything that may be on the path :)

from haywire.

That command gives the expected output, but builds don't work correctly - it detects my platform as *nix. (Uname is returning "windows32")

from haywire.

Did you change the build script to use the uname from win-bash? I'm trying to narrow down if I change the bash script to use that specific uname that it should fix it?

from haywire.

If I make uname use the direct path, won't that break the build on *nix?

from haywire.

If you confirm it works, I'll try to think of some way to avoid that :) I don't have an answer yet though but at least if that works it confirms its reliable. Kind of a chicken and the egg problem though :P

from haywire.

This works:

uname_bin=".\bin\win-bash\uname -s"
OS=`${uname_bin}`

from haywire.

From Jabbr.net #Haywire:

@kellabyte 
oh wait I got it
make build.bat pass the platform name as an argument

from haywire.