WinUAE compilation (again!)

[Dr. MefistO]

Hello!
Could somebody fix all that troubles with compilation?
I want Debug mode. And other modes. winuaeinclibs are old already! And it is not possible to compile with them!

Every time I have to deal with all that troubles, unresolved symbols, manually runnable commands, etc.

Visual Studio 2015. Please, somebody, clone latest sources, and try to compile it! When you'll done it, please, write good instruction for that.

[Toni Wilen]

Use winuaeinclibs_2015.zip. Old libs are not 2015 compatible. (for some unknown reason)

Use "Test", it is nearly same as debug.

[Dr. MefistO]

Ok, I'll try.
And how could I know about that new libs? Where are you keeping links to such stuff?

[Dr. MefistO]

New winuaeinclibs doesn't contain include (*.h) files. Why?
And in project genlinetoscr there is not include paths to sysconfig.h

[Toni Wilen]

Originally Posted by Dr. MefistO

New winuaeinclibs doesn't contain include (*.h) files. Why?

Not needed, they have not been changed. Only libs are incompatible.

And in project genlinetoscr there is not include paths to sysconfig.h

Why should it? Why don't you include actual errors? (btw, all non-winuae projects should be compiled in release mode)

--

"I don't do documentation". "Works for me". And so on. Sorry.

[Dr. MefistO]

Originally Posted by Toni Wilen

"I don't do documentation". "Works for me". And so on. Sorry.

I see.

[Toni Wilen]

winuaeinclibs_2015.zip now updated. Perhaps it helps.

("works for me" = I don't know whats the problem is unless it is explained in detail)

[Dr. MefistO]

I mean, that there are no any compilation documentation, any full and correct project and solution files. Link to winuaelibs could be found only by the such threads, as this one, and so on. Include paths in project files are different for different build configurations... And many-many such things...

Imagine, that someday, you will be no possible to continue any work on UAE. Just imagine that. Then, some guy will try to compile your project. And he will not compile it, because of such stuff!

Thank you anyway.

[Toni Wilen]

I don't care (who wants to volunteer to clean this up!?!) and it would not be that difficult, all of them are standard libraries, just download original sources from official download sites, compile them as static (or even dynamic if you want) libraries and link them.

They are not any kind of winuae-only custom libraries. Unfortunately Windows binaries are rarely available and usually when they are, they are not compatible with any newer compilers or have strange dependencies.

There is no need for winuaeinclibs.zip, it only makes it easier and quicker.

[mark_k]

Are there current (as you used to build 3.4.1b5 at the time of writing) winuaeinclibs archives (32- and 64-bit) which work with Visual Studio 2017?

[Toni Wilen]

Originally Posted by mark_k

Are there current (as you used to build 3.4.1b5 at the time of writing) winuaeinclibs archives (32- and 64-bit) which work with Visual Studio 2017?

Use winuaeinclibs_2015.zip (It is needed for 2015 and newer MSVC)

[mark_k]

Thanks, I have it almost building now. Could you add LogitechLCDLib.h to the winuaeinclibs archive? I get this build error:
..\lcd.cpp(13): fatal error C1083: Cannot open include file: 'LogitechLCDLib.h': No such file or directory

[Toni Wilen]

Added. (But it probably would have been easier to just disable that part)

[mark_k]

Also, I'm getting this:
LINK : fatal error LNK1181: cannot open input file 'ddraw.lib'

I found https://blogs.msdn.microsoft.com/chu...er-directdraw/, which mentioned that Microsoft removed ddraw.lib from the June 2010 DirectX SDK:
"It is worth noting, however, that the import library DDRAW.LIB is not present in the Windows SDK. It is therefore recommended that if you do make use of DirectDraw, you use explicit linking (i.e. LoadLibrary and GetProcAddress) to get any DDRAW.DLL entry-points."

Maybe worth doing that, to make building WinUAE easier for others? I'll try to find an earlier DirectX SDK to get the ddraw.lib file.

[Toni Wilen]

It is already included. I don't want to touch DD code anymore unless it goes away completely.

EDIT: Using loadlibrary (or delay load that winuae uses) has nothing to do with linking. lib is always needed.

[mark_k]

D'oh I copied the winuaeinclibs lib directory to the WinUAE/od-win32 source dir which fixed that.

Next problem... I downloaded current source from github, and the build reports link errors like:
1>fpp_softfloat.obj : error LNK2001: unresolved external symbol "struct floatx80 __fastcall floatx80_atanh(struct floatx80,struct float_status *)" (?floatx80_atanh@@YI?AUfloatx80@@U1@PAUfloat_status@@@Z)
...
1>E:\Work\WinUAE\amiga\winuae.exe : fatal error LNK1120: 18 unresolved externals

[Toni Wilen]

Originally Posted by mark_k

D'oh I copied the winuaeinclibs lib directory to the WinUAE/od-win32 source dir which fixed that.

Don't do that. Add both libs and includes to MSVC include/lib paths.

Next problem... I downloaded current source from github, and the build reports link errors like:
1>fpp_softfloat.obj : error LNK2001: unresolved external symbol "struct floatx80 __fastcall floatx80_atanh(struct floatx80,struct float_status *)" (?floatx80_atanh@@YI?AUfloatx80@@U1@PAUfloat_status@@@Z)
...
1>E:\Work\WinUAE\amiga\winuae.exe : fatal error LNK1120: 18 unresolved externals

Use last beta version, not current version.

EDIT: and make sure all files are added to project. EDIT2: Just use last beta, too many changes still pending..

[paraj]

For my own future reference, here is an unofficial, unsupported guide to building winuae c1be5812d725905a82561dbea8efd77f18e31e3a:

1. Get Visual Studio 2017 Community edition (include at least "Desktop development with C++", make sure Win8.1SDK+XP Support+VC++ 2015.3 tool set are all checked)
2. Get WinUAE source code
2. Download nasm and add it to your path (or put it in winuae/od-win32)
3. Get winuaeinclibs_2015.zip and extract to c:\dev
4. Download the DirectX SDK and install headers/libraries (you can install them to c:\dev - if you do copy the relevant lib files from lib\<arch> otherwise add them to VC++ directories later on).
5. Get aros.rom.cpp somehow and put it in the winuae source folder
6. From a command prompt, go to winuae\od-win32 and execute "asm.cmd"
7. Make sure d:\amiga exists and is writable (use "subst" if necessary). You can probably also change the output folder.
8. Open the winuae solution in MSVC (WinUAE\od-win32\winuae_msvc15\winuae_msvc.sln)
9. Add softfloat/softfloat_fpsp.cpp to the winuae project (Note MSVC crashed when I tried to do this from the IDE, so I just modified the vcxproj file manually!)
10. Change configuration to "Release" and build the projects manually in alphabetical order. (Ignore uaeunp)
11. Enjoy d:\amiga\winuae.exe