Unresolved extrnal build 938

[GoogleCodeExporter]

Trying to compile build 938 in release x86.  Have some unresolved 
external :

Error   1   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputGetCapabilities(unsigned long,unsigned 
long,struct _XINPUT_CAPABILITIES *)" (?
XInputGetCapabilities@@$$J212YGKKKPAU_XINPUT_CAPABILITIES@@@Z)
    Controller.obj  SlimDX

Error   2   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputGetState(unsigned long,struct _XINPUT_STATE 
*)" (?XInputGetState@@$$J18YGKKPAU_XINPUT_STATE@@@Z)    Controller.obj
    SlimDX

Error   3   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputSetState(unsigned long,struct 
_XINPUT_VIBRATION *)" (?XInputSetState@@$$J18YGKKPAU_XINPUT_VIBRATION@@@Z)
    Controller.obj  SlimDX

Error   4   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputGetKeystroke(unsigned long,unsigned 
long,struct _XINPUT_KEYSTROKE *)" (?
XInputGetKeystroke@@$$J212YGKKKPAU_XINPUT_KEYSTROKE@@@Z)
    Controller.obj  SlimDX

Error   5   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputGetDSoundAudioDeviceGuids(unsigned 
long,struct _GUID *,struct _GUID *)" (?
XInputGetDSoundAudioDeviceGuids@@$$J212YGKKPAU_GUID@@0@Z)
    Controller.obj  SlimDX

Error   6   error LNK2001: unresolved external symbol "extern "C" 
unsigned long __stdcall XInputGetBatteryInformation(unsigned long,unsigned 
char,struct _XINPUT_BATTERY_INFORMATION *)" (?
XInputGetBatteryInformation@@$$J212YGKKEPAU_XINPUT_BATTERY_INFORMATION@@@Z)
    Controller.obj  SlimDX

Error   7   error LNK2001: unresolved external symbol "extern "C" void 
__stdcall XInputEnable(int)" (?XInputEnable@@$$J14YGXH@Z)
    Controller.obj  SlimDX

Original issue reported on code.google.com by steve.a.beaudoin on 6 Mar 2009 at 12:19

[GoogleCodeExporter]

Don't see any obvious reason, will try and repro.

Original comment by promit....@gmail.com on 6 Mar 2009 at 1:00

[GoogleCodeExporter]

I'm unable to repro and neither is Mike. What configuration are you building, 
are 
you sure you haven't accidentally deleted something locally, and have you tried 
a 
full rebuild?

Original comment by promit....@gmail.com on 6 Mar 2009 at 1:22

[GoogleCodeExporter]

I did a clean solution and a rebuild.  The only modification I did to the 
solution is I removed the windows 7 project.  I am trying to compile in release 
x86.  I am not a pro of C++, but I have all includes and lib ok, since I am 
able 
to begin linking.  I installed the latest windows sdk and the november directx 
sdk.  This is a fresh vista with SP1 install. The only other modification I 
made 
is to visual studio (2008), I included the windows 6.0A sdk include and lib 
folder and the directx sdk include and lib forlders, both for x86.

Original comment by steve.a.beaudoin on 6 Mar 2009 at 3:12

[GoogleCodeExporter]

Can only be my VS settings.  The only thing I changed, as it is a brand new 
installation, are my include folders.  Here theyare, in the order they are in 
my 
settings :

Win32 - Includes path
---------------------
1. C:\Program Files\Microsoft DirectX SDK (November 2008)\Include
2. C:\Program Files\Microsoft SDKs\Windows\v6.0A\Include
... Default includes ...

Win32 - Lib path
----------------
1. C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib
2. C:\Program Files\Microsoft DirectX SDK (November 2008)\Lib\x86
... Default includes ...

Original comment by steve.a.beaudoin on 6 Mar 2009 at 9:49

[GoogleCodeExporter]

I quit.  Forget it.  I read your documentation on your site and you say vs2008 
only 
support fw 2.0 WITH sp1 and that I should compile with vs 2005.  So, I 
installed 
visual studio 2005, did the msbuild create2005environment, and now it can't 
find 
msclr/marshal.h, i looked into C:\Program Files\Microsoft Visual Studio 8
\VC\include\msclr and there is no marshal.h.  I quit, I will wait your next 
compiled 
revision to have the fix for bug 395.

Original comment by steve.a.beaudoin on 7 Mar 2009 at 2:39

[GoogleCodeExporter]

You know, we do usually email people up to date builds if they ask...

Original comment by promit....@gmail.com on 7 Mar 2009 at 5:29

[GoogleCodeExporter]

I thought that by using SVN, I had up to date source files?  But anyway, as you 
are 
about to deliver a new release, I will wait for it.  And as you are not able to 
reproduce the problem, it is probably a problem with my vs settings but can't 
find 
anything in the documentation to configure it correctly.  I did what the 
configuration told and I have new problems.

Original comment by steve.a.beaudoin on 7 Mar 2009 at 5:51

[GoogleCodeExporter]

Yes, if you download from SVN you're getting the exact same thing we work from.

You shouldn't need VS 2005. We all use 2008 without any problem. Looking at 
your lib
paths, I would try making the DX SDK the top path, since that's how it appears 
on my
machine.

Original comment by Mike.Popoloski on 7 Mar 2009 at 6:24

[GoogleCodeExporter]

I think the problem might be related to having the Windows SDK bits in that 
dialog. 
Usually there's an entry for $(WindowsSdkDir)\lib fairly far down the list and 
that 
makes everything work. Haven't tested it though.

Original comment by promit....@gmail.com on 7 Mar 2009 at 8:53

[GoogleCodeExporter]

Also dropping priority.

Original comment by promit....@gmail.com on 7 Mar 2009 at 8:59

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Well, doesn't seem like it's worth leaving this open.

Original comment by promit....@gmail.com on 12 Mar 2009 at 1:57

• Changed state: NoRepro