Author Topic: Porting Odyssey 1.26 from MorphOS 3.12!  (Read 1157 times)

wawa

  • Senior Member
  • ****
  • Posts: 252
  • Karma: +1/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #15 on: October 28, 2019, 09:40:09 PM »
i also refer to patch and instructions by nicola scendoni. all i knew is as much as was written in there..

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #16 on: October 28, 2019, 10:03:09 PM »
I looked at the patch but I am not a programmer what should I do to change the version of openssl, you can see you and maybe you tell me, I am installing what is necessary to compile everything
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

wawa

  • Senior Member
  • ****
  • Posts: 252
  • Karma: +1/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #17 on: October 28, 2019, 11:27:13 PM »
im not a programmer as well.
you need to link odyssey against the version of ssl you want to use. afair it is being linked statically. if you know what that means. ssl is obne of static libs that are dependencies necessary to build odyssey. building them and setting up build environment  by hand is a major hassle imho which you will probably never get done. best is to use build system. but then im not sure how actually to build abi v0 since as i said i have never done it. and i dont know if the ssl library in question has been back ported to abi v0 and compiles there. also there might be issues with older tool chain.

first thing to get done in this case, if you have a linux host, would be
1. to check out deadwoods aros sources and
2. try to build aros cross toolchain for your target
3. and subsequently build aros itself with it
4. and then also try tobuild ssl which is in contrib (which you also need to check out)
5. and then if its not the version you desire, you might want to try to merge in the ccurrent abi v1 version
6. and then you would have to check out the proper branch of deadwoods odyssey repo into your contrib repo (r187682 is the latest and probably the one you desire)
7. you would have then to check if my mmakefile is in place and follow nicolas instructions
8 and then everntually you might have built the browser.
and then odyssey
« Last Edit: October 28, 2019, 11:42:40 PM by wawa »

miker1264

  • Senior Member
  • ****
  • Posts: 327
  • Karma: +12/-1
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #18 on: October 29, 2019, 12:55:52 AM »
Wow! Really?

I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.

I'm not sure what salvo's abilities are in that respect but he would probably struggle with it also the way you described it.

So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.

wawa

  • Senior Member
  • ****
  • Posts: 252
  • Karma: +1/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #19 on: October 29, 2019, 01:40:49 AM »
@miker
thing is i just outline how one needs to proceed not the details, as i cannot judge what would specifically become an issue en course.
i am also not a programmer as you know and here are plenty more experienced people who actually can code if this is so important a task.
also i was kinda trying to get people together around this trying to secure cross platform approach including abi v0, os4 and morphos potentially, but none actually engaged, neither joakim from os4 nor anyone from mos obviously and my pull request on deadwoods gitub just sits there since a year becoming outdated.

miker1264

  • Senior Member
  • ****
  • Posts: 327
  • Karma: +12/-1
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #20 on: October 29, 2019, 04:19:05 AM »
@miker
thing is i just outline how one needs to proceed not the details, as i cannot judge what would specifically become an issue en course.
i am also not a programmer as you know and here are plenty more experienced people who actually can code if this is so important a task.
also i was kinda trying to get people together around this trying to secure cross platform approach including abi v0, os4 and morphos potentially, but none actually engaged, neither joakim from os4 nor anyone from mos obviously and my pull request on deadwoods gitub just sits there since a year becoming outdated.

Sorry if that seemed critical. I know you are trying. But I don't think salvo can do all that to make the updates. Someone with more experience will have to do that. So that also means he'll have to wait a while longer. I just hope he and others understand that it's not an easy task and that it will certainly take some time to do.

ASiegel

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #21 on: October 29, 2019, 12:53:02 PM »
I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.
Thank you for confirming that there are others who consider this to be too time-consuming.

Quote
So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.
How many people besides deadwood managed to compile Odyssey for ABIv0 and share the binary with end users? A single person in 4 years? I am not sure if waiting is a winning strategy while more and more websites move to encrypted connections and upgrade ciphers in regular intervals.

I used a 5 years old version of Odyssey recently to do a quick technical test and it was close to being useless because secure connections would not work in many cases.

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #22 on: October 29, 2019, 01:44:59 PM »
exactly miker is right I can't do anything about it, nicola scendoni who is a programmer as far as I understood to write some code to update openssl and applied this as an external patch to the deadwood branch
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #23 on: October 29, 2019, 01:58:25 PM »
to compile the new openssl library I must first compile the entire source tree with the contrib? and then I have to install the SDK? then what command should I give to compile "./configure ... ... ..."
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #24 on: October 29, 2019, 02:02:36 PM »
ASIEGEL a compilation error has been made lately, "sin" it was necessary to update the openssl library with lts support
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #25 on: October 29, 2019, 02:17:16 PM »
I downloaded the sources and contrib manually, installed the build-essential and gimmearos package, maybe build essential was already included in buil essential, do I need to install the SDK also? I go to the aros site to read the documentation something is not clear to me, but surely for openssl I need the SDK
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

wawa

  • Senior Member
  • ****
  • Posts: 252
  • Karma: +1/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #26 on: October 29, 2019, 02:57:25 PM »
Ypu dont neeg gimmiearos. Just aros dtc and contribsrc copied within ,AROS source folder.
Then you need to create s buold folder and configure from there. Which exactly flags you need maybe deadwood or someone can tell

salvo

  • Member
  • ***
  • Posts: 179
  • Karma: +0/-0
  • Invalid Civil
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #27 on: October 29, 2019, 03:37:16 PM »
I did my best, I can't apologize
Icaros on HP Z600 Intel Xeon X5570 3 Ghz, Nvidia 8400gs
Support
https://www.actionaid.it/
https://www.amref.it/

nikos

  • Member
  • ***
  • Posts: 206
  • Karma: +4/-1
    • aspireos
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #28 on: October 29, 2019, 03:37:38 PM »
I'm a programmer and I think like a programmer. But even I would struggle to do all these things mostly because I'm not very good at using the build system yet. I'm much better at programming rather than using gcc and the build system.
Thank you for confirming that there are others who consider this to be too time-consuming.

Quote
So what is the best solution for him? Should he just wait till someone puts it all together or attempt it himself? I wouldn't try it because it's above my compiling abilities at the moment.
How many people besides deadwood managed to compile Odyssey for ABIv0 and share the binary with end users? A single person in 4 years? I am not sure if waiting is a winning strategy while more and more websites move to encrypted connections and upgrade ciphers in regular intervals.

I used a 5 years old version of Odyssey recently to do a quick technical test and it was close to being useless because secure connections would not work in many cases.

Yes, exactly. This is a lost case. Use web-browsers on other platforms.
Use your Telephone or something. Use AROS for fun and creative stuff.

terminills

  • Newbie
  • *
  • Posts: 45
  • Karma: +1/-0
Re: Porting Odyssey 1.26 from MorphOS 3.12!
« Reply #29 on: October 29, 2019, 06:28:37 PM »
Modifying open source software and keep updates closed. Only Amiga makes it possible.  :-(
I am afraid you are confused.

Odyssey became a part of MorphOS and its private code repository before Fabien published a more or less equivalent but legally separate open source version. Nobody took an open source version, then broke its license and used it inappropriately in a closed source version. Instead, development of a private branch of Odyssey merely continued just as it did in the past.

That said, even the current MorphOS branch is largely open source since it has been and continues to be based on Webkit. Modifications of Webkit cannot be closed source. They just happen to be completely and utterly useless for the AROS version of Odyssey after its developers chose to move to an entirely different verson of Webkit several years ago that only properly works with little endian processors, thus cannot be used by owners of big endian PowerPC hardware.

And there you have it. The diversion between Odyssey versions happened a long time ago and there is not one group to criticize for it. It was a natural evolution.

I have also personally suggested on multiple occasions that someone create a VM that includes everything to compile Odyssey on AROS in an effort to make participation for outside developers as easy and painless as possible. But if you are unwilling to bang your head against a wall for a weekend of your precious free time just to recplicate the necessary work to get to the stage of being able to compile Odyssey, you are apparently not welcome to contribute, which is a fair opinion to have I suppose but then people should not complain about a lack of participation in a project that supposedly needs more helping hands.

Having said all of this, given that Jacek has announced plans to develop a new MorphOS web browser based on a state-of-the-art version of Webkit, which will likely use Objective-C, and that Terminilis just hinted at separate improvements related to web browsing on AROS on Amigaworld, this discussion may actually be pointless.
Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P   However there's no current news on my hint. ;)