I agree it would be great if people would include build instructions with their projects. I've seen a couple of requests for instructions on how to build E-UAE, and there were no replies.
Last week, in the UAE Wrong Colors thread I asked for instructions and the response I got was run configure and edit some files. So I did a deep dive over the weekend to figure it out.

In the Unix/Linux world most of the time when I compile I find pretty detailed instructions, which typically can be summed up as "get these dependencies and run make." And it just works.

I think part of the problem is that E-UAE has so much legacy code that has to do with other platforms. Maybe its time to fork it and jettison all the stuff that isn't Amiga related.

So just a couple of notes:

The file that resulted is about 22 MB large and not quite as "zippy". When I play audio it kinda skips. The one you get from OS4Depot is only about 6 and
is quite responsive. Obviously the file you get when compiling is not very optimized. Hopefully maybe someone can shed some light on optimization.

It's been hit-or-miss regarding other options and compiling, at least for me. I didn't keep track of my attempts at other options. Sorry about that.
Maybe later this week I'll play around with it some more.

I'd love to hear what other people's experiences are, especially those who have more experience in compiling. If I need to clarify or make any corrections let me know.
I'll do my best to fix it.

Or How I Stopped Worrying and Learned to Love Configure (more or less)

So I got a bug up my keister this weekend to compile E-UAE. Since Odysee doesn't play well with Github, I used my Winblows machine to download a zip file with the
source code and copied it over to my Amiga. After a fair amount of trial and error, along with a bit of gnashing of teeth, I got it to compile. For anyone interested,
these are the steps I took to get it done.

1. Make sure you have all the dependencies. Obviously, you need the SDK installed. You also might need to download some packages. These were the ones I needed:

a. Awk/Nawk. You can get that here:
OS4 DEPOT-Awk

b. libz. You can get that here:
OS4 DEPOT-libz

c. mpega (just the header files). You can get that here:
OS4 DEPOT-mpega-includes

Most of these have Autoinstall, the mpega header files go into SDK:local/common/include.

2. Acquire Khval's e-uae 1-0-0-uae-1-1-2 source code. How you do that is pretty much up to you. I had to use my Winblows machine to get it. Make sure you're in the 1.1.2 branch.

3. Go to the drawer where your source code is. You should see configure in that drawer. From now on, any files or drawers I reference will be relative to that drawer.
Type sh to open a unix shell. You'll notice that all your directory/volume names will be preceded by a /. No colons.
Type Quote: to make sure your environment is set. If you see paths that start with /SDK, you're good to go.
If you see ones that start with /Cygwin, you might want to go to your S:User-Startup file and comment out the line that says Quote: and reboot.

4. Edit the configure script. Any text editor will do. I use LiteXL because it shows line numbers. Search for the line that says Quote:.
Delete bsdsocket-posix-new.$(OBJECT), leaving only bsdsocket.$(OBJECT).

5. Make the configure script executable again by typing Quote:.

6. Now you can run configure by typing Quote:
7. Don't run make just yet. You need to edit 2 more files, both called sysconfig.h First, open src/sysconfig.h Search for a series of #define SIZEOF_ statements and correct them to read:

Quote:

Do the same thing for src/tools/sysconfig.h

8. Okay, cross your fingers, pray and type make.

I have an X5000/040 and it takes about 6 and a half minutes to compile.

Also, if anyone has instructions on how to compile E-UAE, that would be awesome.

I'm not if this is what others are experiencing, but this is what I noticed:

Conditions:

1. uaegfx video mode set in emulation.
.uaerc - gfx_fullscreen_picasso=yes
gfxcard_size=32
2. Picasso screen mode in emulation (in my case AOS3.9) and
E-UAE set to same color mode (say 32bit ARGB, ARGB32).

Result:

Colors that are, how to describe it? Wonky? Um almost like there's a purple
multiplier filter applied to the entire application.
Text is also blurry and almost impossible to read.

Workaround:

Set UAE to display video mode requester and set screen mode from the
requester to ARGB32 and the emulated Picasso screen mode to 16bit.
.uaerc - amiga.screen_type=ask

I don't know, maybe color channels getting swapped somehow?

If anyone can tell me how to create and post a screen shot of E-UAE I can try
to do that.

Okay, 3D stuff seems a lot more zippy and responsive now. Doom3 Demo clocked in around 21 fps. I think before it was hovering around 16-17 fps.
That's a pretty big improvement. It's almost playable now. Too bad I don't really like the game.

Just updated my X5000/40. Everything seems to work. It replaced the Enhancer Time preferences, which is fine. The Enhancer Time was buggy.
With the new USB stack it recognized my wireless headphones, but I'm pretty sure it needs AHI drivers. It also recognized my ESM 9110 Wireless Game Pad.
I could make it do stuff in Amiga Input, but not in any games just yet. So, got some more learning to do!

@LiveForIt

OMG! This is so cool! Just last week I was trying to figure out how to compile UAE. Now I don't have to.

Once I figured out the keyboard combos to switch to fullscreen mode and quit and stuff, I was off to the races.

This is awesome. Thank you so much.

edit - I forgot to mention I'm emulating Amiga OS 3.9

Okay, Final Update:

After going through various attempts at getting my X5000/040 in order, it's finally running solid. No periodic lock-ups for a few days. It seems that there were several issues.
So if anyone has stability issues on their X5000/040, here are the three things I think helped, in order of importance:

1. Populating both memory slots with matched memory.

2. Utilizing video drivers from A-media's Rescue Stick.

3. Utilizing memory recommended by the manufacturer.

I'm not sure why having both memory slots occupied helped so much. My (less than educated) guess is that since the RX 580 is a higher performing video card,
a single ram stick couldn't keep up. Having both slots occupied engages interleaving, which increases memory bandwidth enough to keep up with the card.
If anyone else has any insight on this, feel free to chime in.

At any rate, everything runs much smoother. And faster.

@joerg

Something must have changed. When I tried "setenv stdout" it said "can't delete stdout". When I tried "setenv stdout vga,serial"
it said "error inserting variable errno 22". It wouldn't let me change it. Oh well. It works.

Thank you!

@joerg

Thank you. But how should I set that? Should I do setenv stdout vga,serial or is there a way to tell U-boot to use default environment settings?

@smf

Yeah it turns out I had to set stdout to serial. It must have changed at some point.
Anyway. I saw what I needed to see.

Thank you.

@balaton

Yes I want to set the output of Uboot. I want to see how my memory is being detected. I kind of wish Amiga OS had a CPUZ type of app.

But thank you.

Hello,

How do I set Uboot's output to the serial on the X5000? Is it setenv stdout serial, then saveenv? Or is there some other way? I don't have NVSetVAr in my C directory.

Thanks in advance!

Kevin

@MickJT
So I copied that amissl_v111m.library file over and that did the trick. Emotion playing from URLs just fine now.

Thank you.

@khayoz

Finally got my Kingston memory today and installed it. So far, things are going okay. It's a HyperX HX316C10FB/8.
It's pretty close to what is recommended by Aeon.

I read through that thread about interweaving memory. I still have the old stick. Do I dare try my luck at having 2 memory slots filled?
I don't know. We'll see.

Hello,

So it wasn't VideoVortex. Emotion says I/O Error whenever I try to point it to a URL.
I can play local files just fine, just not over the internet.

@khayoz
Yes I thought about that too. I used memtest and it passed all the tests.
Here's the thing though: the memory that Aeon recommends has latency timings of CL10, while the memory I have is CL11.
In the PC World, that doesn't make much difference. It's just a teensy bit slower. I don't know about the Amiga NG World though.
I ordered the memory that Aeon recommends from Ebay, but ran into a snafu and waiting for it to get corrected.

At any rate, the libraries I copied seem to be helping. I'll continue to go through the rescue USB stick and see what else I can copy.
I just want to be careful not to copy something that doesn't work.

Okay. I think I may come super-duper close to solving the problem. I copied the two libraries in the Libs:Warp3DNova/ dir from the Amedia Rescue USB Stick.
Things seem to be a lot better now. Apparently Amedia has more recent versions of those libraries than what's available on the Enhancer software.
I'm not going to ask any questions, but I'm gonna make a backup or two of the Amedia Rescue stick.

@khayoz and @eliyahu

Well I changed it to low power and high power and stilll the same problems. I don't understand it.