Topic: VC++ Toolkit 2003 compile problem..

[DsNo]

Against variant me maybe the minute when it knows it is?
The portion which is problem is the "sh.exe"...

My environment...

OS : Windows XP Professional (32-bit)
CPU : Intel Core 2 Duo E6400
SW : Windows Server 2003 R2 Platform SDK, DirectX Software Development Kit,
        Microsoft Visual C++ Toolkit 2003, MinGW 5.1.3, GNU utilities for Win32,
        ActivePerl, Nasm...

[Leaf]

I caught this problem ago.
Then I used Cygwin to compile it, the problem was solved.

[DsNo]

I caught this problem ago.
Then I used Cygwin to compile it, the problem was solved.

There is not a problem from Cygwin or MinGW.
But DirectX9 to select the VC++ in because.

[CaptainCPS]

If you check this carefully you will notice that Cygwin is used too when compiling with VC++ / MS SDK Environment

...
In addition to the above, you will need to have a version of Gnu make, nasm,
and Perl. You can either install Cygwin from <http://www.cygwin.com/>, which
takes care of all three, or
get Gnu make from MinGW at <http://sourceforge.net/projects/mingw/>,
get nasm rom <http://nasm.sourceforge.net/> (put nasmw.exe in your path), and
get ActivePerl from <http://www.activestate.com/Products/ActivePerl/>.
...

Install the Cygwin... and use this in a text file but with your own environment paths (just edit where they are in your hard drive, dont delete any because this will set the compilation environment required by VC++ / MS SDK )...

(btw, this is my working '.bat' file that I use)

@echo off

@call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat"
@call "C:\Program Files\Microsoft_DirectX_SDK_October_2004\Utilities\Dx_Setenv.cmd"
@call "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\SetEnv.Cmd"
@path=C:\MinGW\perl;%path%
@path=C:\MinGW\perl\bin\MSWin32-x86;%path%

@make vc

@echo .
@echo FBA Compilation using Visual Studio 8 (vc toolkit) Done
@pause

...then save text file as 'VCToolkitBuild.bat' and put it in your FBA dev directory

If you installed Cygwin and made this, it should compile without a problem ;-)

SeeYaa!!
 

 

[DsNo]

CaptainCPS-X assists from thank you.

Previously problem the problem got again it solves.

[CaptainCPS]

Errors like that are because you have a file missing in the 'makefile'... in this case is the 'romsave.o'...

if youre doing a FBAP compilation you must have these...

      neogeo.o neo_run.o neo_decrypt.o neo_text.o neo_sprite.o neo_palette.o neo_upd4990a.o \
      romsave.o neo_prot.o neo_boot.o \

When I saw your post I edited my makefile and removed the 'romsave.o' to check and i got the same error, so thats why im sure thats the problem 

I Hope that now you can do your build with no probs ^^

SeeYaa!!
  

[DsNo]

CaptainCPS-X your right... I was leaving out the "romsave.o".
The error occurs last from Link process.

[CaptainCPS]

Linker Tools Error LNK1123

failure during conversion to COFF: file invalid or corrupt

The object or resource could not be converted to Common Object File Format (COFF).

This tool requires the format of all input files to be COFF. If an input file is not COFF, LINK automatically converts 32-bit OMF objects to COFF, or the tool runs CVTRES.EXE to convert resource files.

Possible causes

* The file is corrupt.
* The file is not a valid file type. An example of an invalid type is a 16-bit OMF object.

I think you have to delete the 'obj' dir located in the fba_dev directory just to make sure everything is compiled from zero, i think something is corrupt there...if this doesnt solve that then maybe a Resource file (*.rc) located in 'src/burner/win32/' is corrupt...

If thats the case then, i recommend that if you gonna edit something there just edit the 'App.rc' and dont change the others, that may cause some problems when compiling and converting the resources (make a backup too of all files edited so you dont lose track of the changes you made  )

SeeYaa!!

[DsNo]

CaptainCPS-X thanks it gives with sincerity.. Compile was successful finally..

Before used "cvtres.exe"..
"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64\cvtres.exe"

After used "cvtres.exe"
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\cvtres.exe"..

[CaptainCPS]

No problem man  , now i uderstand exactly why you was getting the error, i didnt think that the 'cvtres.exe' was a problem at all because when thats the case a CVTRES error is displayed too...
 

CaptainCPS-X thanks it gives with sincerity.. Compile was successful finally..

Before used "cvtres.exe"..
"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64\cvtres.exe"

After used "cvtres.exe"
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\cvtres.exe"..

...in conclusion, it was converting the COFF in a way that a 64-bits linker understand, or Most probably it was not getting to convert it at all because of the system you have is 32-bits

you found the cvtres.exe in other place, but here you have other one...

C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win64\x86\AMD64\cvtres.exe

Try with this one too maybe you dont have to go away from the 'MS SDK R2' directory at all

if it doesnt work just use the one that you was using, but i think this one will work just fine too 

SeeYaa!!
 

[DsNo]

This probably is problem, the possibility of knowing it is?

[CaptainCPS]

This probably is problem, the possibility of knowing it is?

That happen mostly if you got the wrong DirectX SDK (happened to me once)... so here is the one that is needed with FBA...

DirectX 9.0 SDK Update - (October 2004)

http://www.microsoft.com/downloads/details.aspx?FamilyID=b7bc31fa-2df1-44fd-95a4-c2555446aed4&DisplayLang=en

If you allready have this DirectX SDK then probably there is something wrong in the environment setting you have

I hope you can get it working now 

SeeYaa!!!
 

[DsNo]

Already it is in the process of using the "DirectX SDK (December 2006)".

Possibly there will be also a "DirectX SDK" difference move. It will try again.
Thank you CaptainCPS-X!!

[DsNo]

As well it was a "DirectX SDK" problem.
After changing with the "Microsoft DirectX 9.0 SDK (October 2004)", it operates to in all normality.

[CaptainCPS]

As well it was a "DirectX SDK" problem.
After changing with the "Microsoft DirectX 9.0 SDK (October 2004)", it operates to in all normality.

Nice to know man!

SeeYaa!