VBA-M Forums

I am using Microsoft Visual Studio 2010 on Windows 7 Service Pack 1 x64.

When building the appropriate (VBA2010.sln) Solution File, I encounter an error...

Error 27 error MSB3721: The command "C:\Users\Cody Mitchell\Desktop\VBA-M\trunk\project\vs2010_mfc\..\..\..\dependencies\nasm.exe -o "C:\Users\Cody Mitchell\Desktop\VBA-M\trunk\project\vs2010_mfc\x64\Release_temp\2xSaImmx.obj" -D__DJGPP__ -O1 -f win32 -Xvc -- ..\..\src\filters\2xSaImmx.asm" exited with code 1. C:\Users\Cody Mitchell\Desktop\VBA-M\trunk\project\vs2010_mfc\nasm.targets 45 6 VisualBoyAdvance-M

I have only been able to run that command successfully by opening a cmd.exe window and executing the following:

Any help in building would be appreciated.

nasm is not handling command lines with spaces passed to it from vc2010 for some reason. its strange because the command line is wrapped in quotes like is required to pass the command line but it still fails.

moving it a location where the directory path has no spaces will resolve it.

Thank you, this did help, though now I get 4 more errors...

Error 17 error C1083: Cannot open include file: 'D3dx9core.h': No such file or directory C:\vba-m\trunk\src\win32\Direct3D.cpp 29 1 VisualBoyAdvance-M
Error 18 error C1083: Cannot open include file: 'al.h': No such file or directory c:\vba-m\trunk\src\win32\LoadOAL.h 3 1 VisualBoyAdvance-M
Error 19 error C1083: Cannot open include file: 'al.h': No such file or directory C:\vba-m\trunk\src\win32\OpenAL.cpp 13 1 VisualBoyAdvance-M
Error 20 error C1083: Cannot open include file: 'xaudio2.h': No such file or directory C:\vba-m\trunk\src\win32\XAudio2.cpp 13 1 VisualBoyAdvance-M


Sorry to bother you, but the latest x64 build is about 100 revisions off, so I figured I'd do it myself... though I've always been more of a ./configure guy. xD

Also, try using single quotes instead of double quotes. From what I was reading, it had to put a double quote around both ends of the command, but because of this, when reading the command and running it, the double quotes in the middle caused it to assume that the command string ended there and there was yet another string afterwords.

Edit: Or if possible, instead of single quotes, use an escape character, like in programming. ie \" Not sure it it would work in command line though but it's just a thought.

Quote:Error 17 error C1083: Cannot open include file: 'D3dx9core.h': No such file or directory C:\vba-m\trunk\src\win32\Direct3D.cpp 29 1 VisualBoyAdvance-M
Error 18 error C1083: Cannot open include file: 'al.h': No such file or directory c:\vba-m\trunk\src\win32\LoadOAL.h 3 1 VisualBoyAdvance-M
Error 19 error C1083: Cannot open include file: 'al.h': No such file or directory C:\vba-m\trunk\src\win32\OpenAL.cpp 13 1 VisualBoyAdvance-M
Error 20 error C1083: Cannot open include file: 'xaudio2.h': No such file or directory C:\vba-m\trunk\src\win32\XAudio2.cpp 13 1 VisualBoyAdvance-M

install the DirectX SDK, and openal sdk, and add them as VCC directories.

The properties of the project needs to be modified. Currently it directs it's include and library files to the OpenAL folder as well as the old August 2009 DirectX sdk. When every DirectX SDK is installed, it adds a path titled $(DXSDK_DIR) while changing it's folder name, which is currently June 2010.

It would be recommended that the svn be updated to accommodate that.

Just in case, the $(DXSDK_DIR) has the backslash in it, so for example pointing to the DirectX SDK's include folder would be $(DXSDK_DIR)include, instead of $(DXSDK_DIR)\include

Hope that is helpful as well.

OpenAL default installs to the specified location, and VC2010 does not load the DX Sdk from any directory by default, so i was just setting its default directory,

was easier to just define the full location >.>

Yes, it does have to be manually loaded, but the DirectX SDK June2010 download page has a section that explains how to integrate it by using the environment variable instead of just going straight to the DirectX SDK page.

Here's a long quote from the page, as well as a link to the source just to help.

"With Visual Studio 2010, the model for adding include, library, and executable paths has changed. In Visual Studio 2008 and previous versions, paths were specified as global settings under Tools\Options. With Visual Studio 2010, paths are now specified on a per-project basis on a VC++ Directories page. All the Visual Studio 2010 projects for the DirectX SDK samples and tools include direct per-project references to the DirectX SDK--via the DXSDK_DIR environment variable--and will compile without any additional steps."

http://www.microsoft.com/downloads/en/de...8a3ba730ba

FYI: I'm brand new to the programming scene, and can barely get past nodes, classes, and other things. I honestly don't know how to act around professionals. I do apologize if I seem rude or anything. I'm not trying to be.

im probably ruder the way we aussies interact is usually crude to most others lol.

Lol. Well, even so, I wouldn't want to piss of someone who holds a gunblade. Those things can poke an eye out, and I need both of mine.

lol, I'm not a professional.

I am just a hacker/reverse engineer who uses C/C++/ASM code to do thier bidding....

Alright. I finally have time to install the OpenAL and DirectX SDKs (school and all), so I will try again once the DirectX SDK downloads...

Edit:

Huzzah! Many thanks. I successfully built a 32-bit Release of VisualBoyAdvance-M. Not to be a bother, but trying to build one for 64-bit gave me 544 errors and 47 warnings. :S Any ideas?

...x64 was a test only thing, it wasn't too functional.

Ahh... I understand. In any case, many thanks for the help. Having the latest SVN build at all times is really something I enjoy having.