Re: [opensource-dev] Windows 64 bit build issue

2016-11-30 Thread Callum Prentice (Callum)
Great. I had an idea that was the case. Thanks again Cinder. On Wed, Nov 30, 2016 at 6:30 PM, Cinder Roxley wrote: > We nuked that whole project and set volume directly on Windows using > waveOutSetVolume(HWAVEOUT, DWORD). >

Re: [opensource-dev] Windows 64 bit build issue

2016-11-30 Thread Cinder Roxley
We nuked that whole project and set volume directly on Windows using waveOutSetVolume(HWAVEOUT, DWORD). https://bitbucket.org/alchemyviewer/alchemy/commits/b3e54a075de4440390bb1be8c9f73bfd94053a01 The shim is only needed up to XP and is completely unnecessary with the availability of WASAPI in

Re: [opensource-dev] Windows 64 bit build issue

2016-11-30 Thread Callum Linden
Thanks so much for the speedy reply Cinder. I hoped that was the case and the build seems okay without it. The other perplexing one is for the winmm_shim project. For 64 bit builds it fails with a bunch of unresolved externals which look to be related to MMX intrinsic maybe. Not at my

Re: [opensource-dev] Windows 64 bit build issue

2016-11-30 Thread Cinder Roxley
It’s not needed. We dropped it in Alchemy when adding 64-bit support, and it continues to run fine. /FIXED:NO just ensures that code can be position independent. Maybe at some point this was needed a long time ago for apr hijinks or Windows98 compatibility or something of that nature, but you

[opensource-dev] Windows 64 bit build issue

2016-11-30 Thread Callum Prentice (Callum)
I'm working with Nat Linden on the 64 bit viewer build and we've been encountering an odd error - A number of projects in 64 bit only configurations have an entry for "Force Includes" files set to XED:NO. Nothing on Google so we were stumped for a while but eventually tracked it down to a number