Compile Odyssey for ABI_V0

[ch1ll]

I don't know if I should spend time to make ffmpeg 3.0.1 to work or directly on 4.0.2 helping wawa...
I compiled ffmpeg with these additional flags:

--disable-inline-asm This was required to make it compile. I don't have anymore the error I had without it, but I found that solution on ffmpeg mailing list
--disable-network I added this to fix the issue related to owb linking issue posted before on this forum. My understanding was that ffmpeg does not manage directly connections...

If somebody has some idea let me know...

[wawa]

odyssey is currently the only program directly depending on ffmpeg. so my guess is, it would be the best to try and get 4.0.2 working with it. actually (afair) its only one function that acinerella is lacking, that doesnt get exposed by ffmpeg any more, and they claim it should have never been. on the other hand acinerella got updated in the mentime by morphos developer (piru), the sources are public. but it requires in turn further changes in at least one file where odyssey media player interfaces to acinerella, and according to andree, whom i asked, they aint inclined to share these changes, at least for now, because apparently it is not working as expected.

[nikos]

As you might know we got the sources to Odyssey web browser from a MorphOS developer. One difference with MorphOS compared to AROS is that they got overylay support in the OS. I know that Odyssey for MorphOS take advantage of that, and can for example go fullscreen, something that never worked in AROS version. The reason I say this is that there could be some code from MorphOS version that mess things up cause of this.
I know MorphOS never had the synch issues we have. No matter what ffmpeg version.
 
Playing video with external MPlayer there are no synch issues. What I been thinking is that there could be something inside Odyssey playing video that eat all the CPU power. I know even with Linux playing video in web-browser without GPU support can be heavy task. MorphOS is PPC only and maybe there are some things to look at. I'm thinking x86 could take advantage of some Intel CPU media extentions that PPC does not have. As you know I'm not a developer so don't laugh if this makes no scence

[Gundam]

@ch1:

How about updating the rendering engine to a newer version ?

[wawa]

thats a whole lot of work. i have looked at the changes since odyssey snapshot and its definitely beyond what i can do. there has been structural changes for what i remember. and also i expect the current engine to be heavier. as odyssey is heavier than ten years earlier aros owb webkit.

maybe it can be done, but it needs a skilled professional, not some noob. but then, first things first.

[ch1ll]

@wawa:
I'm preparing the patches to ABI_V0.
I see that the code compiled by the nightly build is on the svn branch: ABI_V0-20161228 and this is not in synch in github with the repository from ezrec. Is that correct?
Since I do not have write access to svn, if you agree I can check that new openssl do not break other contribs, and then prepare a patch so you can commit it.

Regarding other developments: currently, I see as first priority to be able to have a clean compilation of Odyssey. I should be able to release it quite soon. After that, we should stabilize Odyssey and integrate new ffmpeg. If we are able to attract more developers we may think about other changes more complex like new engines.

[magorium]

@wawa:
I'm preparing the patches to ABI_V0.
I see that the code compiled by the nightly build is on the svn branch: ABI_V0-20161228 and this is not in synch in github with the repository from ezrec. Is that correct?

That is correct. ABI_V0 was abandonded ages ago in favour of the 2016 branch (which ought to be dead as well by now, but current AROS distro's rely on it)

Since I do not have write access to svn, if you agree I can check that new openssl do not break other contribs, and then prepare a patch so you can commit it.

In case you do not have write access to svn then the method you mentioned is the suggested path. You can then either post the patch somewhere, preferably on the developers mailinglist (so that it can be reviewed). Of course if wawa or someone else is helping you then a private mail to your contact is probably sane as well.

But.... did deadwood not offfer write access to his personal repository on github ? Would that not be an easier path ? Not trying to stirr things up there, just an observation.

fwiw and afaik: ezrec put up his mirror before the 2016 break and so his scripts probably did/do not include this branch (at least i was unable to find it). You can at least get a copy of the branch using svn guest account. More info also on trac.aros.org (https://trac.aros.org/trac/browser/AROS/branches/ABI_V0-20161228)

[ch1ll]

Thanks for the suggestion. I have write access to daedwood's repository with odyssey code, but I also modified mmakefile.src for openssl, ffmpeg and for curl. On  curl I also backported some function from openssl.c from the last version.
Of course I was able to access svn using guest. I will share a patch here and in the mailing list.

[wawa]

thats cool.
i can test your patches for abi v1 platforms.
if you give me your mail via pm ill invite you to
https://amigaports.slack.com
where two of main aros develpers are hanging around.
maybe also neil and deadwood are interested. or whoever else?
that not to circumnavigate dev ml, but its good for coordination, quick advice and reference.

[wawa]

btw. of course ideally at some point would be good if you gain write access to svn yourself, after neil and perhaps others approve this.

[sabbate]

it seems to me that with the current engine you can use the program, wawa long ago had ported to abiv1 and nikos had tested it successfully

hi 

[magorium]

@ch1ll:
ah yes. That would make things a bit more difficult then.

Thank you for your efforts

[Gundam]

@ch1:

Consider compiling Odyssey also for abi v1_64 bit, which is the main branch; abi v0 is becoming obsolete and we should gradually move to abi v1.

[sabbate]

I think it's still some work on abiv1, so this porting on abiv0 is important, even icaros desktop is based on this last branch

salvatore

[ch1ll]

Hi all

I finally tested again the compilation process and committed the patch to ABI_V0-20161228-patch and to  Odyssey on deadwood repository on: https://github.com/deadwood-pl/OdysseyWebBrowser/tree/odyssey-r187682.
I also added my instructions on how I was able to compile.

@AROS committers: please review the AROS patches on: https://github.com/deadwood-pl/OdysseyWebBrowser/tree/odyssey-r187682/ABI_V0-20161228-patch
Basically to make Odyssey with new ssl working I had to:
- Backport OpenSSL 1.0.1
- Modify curl to make it work with new openssl
- Modify some compilation flags on ffmpeg, add AROS headers on networking files and disable udp (temporary)

Next step will be:
- Integrate with new ffmpeg
- fix Bookmark and Cookie broken dialog windows (I guess the known issue with tree list).

Please let me know your comments...