Porting to AmigaOS4 thread

@Raziel
Wasn't done yesterday, as fighting with some newer bison issues , almost deal with.

@kas1e

Take your time.
Will not be able to test it before after christmas anyway due to work.

But thank you very much

@Raziel
Done!
https://www.amigans.net/modules/xforum ... hp?topic_id=8122&forum=25

Through, firstly try it. As seems (at least from my first try) there can be some issue with new Bison, when it by some reasons tried to parse in adtools's libintl some .y file, and seems done it wrong, and one of the files can't compile. I found in google some fixes, but then, somehow that problem auto fixes, and i can't reproduce it anymore : that why i didn't write about in article.

So, try it firstly, if you will meet with the same error when will build adtools, and expectually that libintl, i may try to check it again, as i probably fixed it for myself, just can't by some reasons rollback to recheck it.

@kas1e

Thank you.

Will check it out once I get home from woek

@kas1e

Phew, took a while to download, compile and install!
But it did so without any errors, test example compiled without any problem also.

So I can verify that the guide is without errors.

THANK YOU very much kas1e! :)

@kas1e

Is there anything different I have to look out for when I want to install third party libs, like libsdl, libpng and such or does it work just like with the native SDK?

@khayoz
Good! Thanks for tests

@Raziel
All the same. Just your SDK directory not work:SDK, but /usr/local/amiga/SDK. All directories layout inside are the same.

Once you will go into dark side of crosscompilation, you will never back :)

What you need to deal with are things i wrote in "tips&tricks, but that is for actual porting.

You can take scummvm as first test of course, and i csn help to deal with build process so you will get how to do it all

@kas1e

Thank you again.
Will sure ask if I hit something.

I'll probably not use it to compile scummvm, rather add-on stuff I can't compile natively, but scummvm will be a good test.

@Raziel
How long it takes to compile scummvm natively on your amigaone hardware ?

@kas1e

Approx. 1h 45mins, if done completely with configure beforehand.
Yes, I know it will easily be three or more times faster on the pc, but I want to keep the build native since that should still be the ultimate aim, shouldn't it?
To have a working SDK that is able to compile such big projects.
Otherwise we can drop the whole native sdk development and let the devs focus on something else.

I do still have one question.
Does cross compiling support shared builds/objects?
I know that shared builds are turned off for the cross builds (buildbot, through a linux server) in scummvm since it does not build working binaries.

Any chance we could have ffprobe ported to OS4? There's a 68K FFMpeg package that includes it.

Thanks.

@Raziel
Quote:

Just IMHO is that as we have no resources, we already need to drop in SDK all those Autotools, CMake, automakes and whatever else. They always VERY old, and never up2date, and never bug-free. What we need from SDK, its everything else which left: native libraries for clib2 and newlib, includes, native GCC (yeah, to compile natively on os4 anyway).

We anyway have NO SDK updates at all anymore (and I not sure if we ever will), so why we need to hold things inside, which will be mostly of no use because of different factors :) But anyway that not big deal, what we have now already enough, especially when there is ability to cross-compile things.

Quote:

Cross-compiling in no way anyhow different from a native building. Just you build amigaos4 things by x86 binaries, but still, everything as on native. Of course, you can build the same shared objects and whatever else. Everything the same as native, just bug less and issue free when it comes to Autotools and stuff.

I never like sobjes, but I still build one app which uses them: LodePaint, and that one I build on Cygwin's cross-compiler, so yeah, no problems.

@kas1e

And once again thank you.

Wrt to native compiling...
Our system will die even faster if there won't be an up to date native compiler anymore.
The reason is easy.
If a dev cross compiles he/she is already working most of his/her time on a foreign system.
Why would he/she care anymore once we really lose a native sdk?

I'm just talking from my pov, if I'd be forced to compile everything on a foreign platform, I'd sooner or later drop the hassle and simply use the program on said foreign platform (at last if my hardware dies).

And right now, I don't want to do that, I want to be able to do everything on amiga, for how long...I don't really know.
Since I don't do high end gaming, I could already switch to windows or linux with my (gaming) interests (scummvm residualvm, uae). I would even have less to care about...
And I fear that this might be one of the main reasons why no new users arrive...why would they bother with so much drawbacks?

If we start to let the native sdk stuff die too why would any outside devs, let alone users, care to use amigaos?

Plus, it's awesome as hell to be able to natively compile programs on amigaos.

@Raziel
Quote:

Well, that true, indeed :)

There is just released new version of VICE (3.4), any change to get Amiga version?

@All
Can anyone help me with that:



When compiling over Newlib, it brings me lots of heavy errors from include/c++/8.2.0/bits/hashtable.h, there is the output:

http://kas1e.mikendezign.com/aos4/adtools/output_unordered_map.txt

When I build the same test case over clib2, all fine.

Any ideas? Thanks!

@daveyw

Regarding ffprobe, can it do something that ffmpeg can't do if running ffmpeg -i <input> to see what type of file something is?

Edit: Grammar.

@MickJT

I'm not 100% sure. I am currently working on an arexx script that uses ffmpeg -i (run from Art Effect to build a preview of 20 thumbnails from a selected video, and then prints data about the video at the top). It's working ok, but I can't figure out how to accurately parse fps, and I'm getting the resolution from a frame grab, which could be problematic if I decide to go with scaling.

When I google some of the features of -i, I'm seeing a number of threads where people are asking questions, and somewhere in the answers someone says "just use ffprobe".

I'm thinking of switching to mplayer. It appears to produce data on a video in an easy-to-parse format, although some of the results I don't quite understand (codecs are returned as codes, so I guess I would need to map those to whatever).

Hey devs,

is there an easy method to create an amigaos4 .library file out of a .a library?

e.g. (and no i'm not trying to do that, it's just meant as an example)
Quote:
Something like (yes, i know this gcc switch does'nt exists...again, it's an example)
Quote:
Any help appreciated

@MickJTQuote:
ffprobe allow you to specify the items your interested in and outputs the information in an easy to parse format.

Keyword=value

$ ffprobe -v error -show_format -show_streams input.mp4
[STREAM]
index=0
codec_name=h264
codec_long_name=H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
profile=High
codec_type=video
codec_time_base=1/50
codec_tag_string=avc1
codec_tag=0x31637661
width=320
height=240

... etc.