(02-18-2011, 06:06 AM)Runo Wrote: [ -> ]Are this hotfixes safe? I mean, will they fuck with my settings or something like that?
I do not know. You can use it, or wait for SP1 and use buggy VS2010 until SP1 becomes stable. And you do really know it's developer error in code or compiler bug ...
(02-18-2011, 06:10 AM)shuffle2 Wrote: [ -> ]You're on crack.
I already explained how to edit that property sheet - so I have no idea what you're complaining about there.
I use vs2010 ultimate and windows sdk 7.1. My environment didn't require any idiotic tampering. If you feel the need to ruin your own environment, that's fine - but don't post incorrect instructions for other people to follow.
If you want to change Platform Toolset manually in all you project then OK. I do not want to, and it does not break anything.
I do not found a IDE option to change this property to default to different Platform Toolset.
r7190_Win32
http://www.mediafire.com/?qybyqwntuknupdi
r7190_Win64
http://www.mediafire.com/?1p4vibk3nptcga9
___________________________________________
the only change I made are
paths to VC++ Directories:
Microsoft.Cpp.Win32.user and Microsoft.Cpp.x64.user for DirectX
and for error LNK1181: cannot open input file 'iphlpapi.lib'
add to
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.default.props
<PlatformToolset Condition="'$(PlatformToolset)' == ''">Windows7.1SDK</PlatformToolset>
And nothing more
Quote:I do not know. You can use it, or wait for SP1 and use buggy VS2010 until SP1 becomes stable. And you do really know it's developer error in code or compiler bug ...
Good point. I compiled for the first time and failed with a weird error that I posted earlier in this thread. I tried again and it did beautifully, without a single error, just the normal bunch of warnings during the compilation. But then I saw my Dsound was not working, I have to use Xaudio2 as audio backend. This doesnt happen on UnknownForce's build, same rev, could this be a compiler bug?
Also, I noticed that my Dolphin builds have a "M" after the rev number in the window title. E.g. rev 7188M
Why is that?
Thanks
(02-18-2011, 07:29 AM)Runo Wrote: [ -> ]Quote:I do not know. You can use it, or wait for SP1 and use buggy VS2010 until SP1 becomes stable. And you do really know it's developer error in code or compiler bug ...
Good point. I compiled for the first time and failed with a weird error that I posted earlier in this thread. I tried again and it did beautifully, without a single error, just the normal bunch of warnings during the compilation. But then I saw my Dsound was not working, I have to use Xaudio2 as audio backend. This doesnt happen on UnknownForce's build, same rev, could this be a compiler bug?
Also, I noticed that my Dolphin builds have a "M" after the rev number in the window title. E.g. rev 7188M
Why is that?
Thanks
M is added when sources from SVN are modiffied (M like Mod
).
It's a part o automatic versioning system.
Ohh, right
What about I cant have sound on dsound backend? I tried compiling yet again and it didnt work, and this only happens on my builds
Thx again
EDIT: I tried reverting to original SVN, but when I do that it resets my changes to directories and the toolset, what should I do? I mean, how others get around that, I've never seen a build with M