OS/2, eCS & ArcaOS - Technical > Internet

Firefox Developer Edition 24.8.1b4

<< < (2/4) > >>

Dave Yeo:

--- Quote from: TeLLie on March 16, 2015, 05:44:32 pm ---Hi Dave,

I really appreciate that you build TB and SM, FF ..

But are not you afraid that this evokes precisely a DLL war ??

I'm afraid it will, but that's just my 2cents thought...

--- End quote ---

How so? TB and SM use the same DLLs as the Bitwise FFb4 minus a gcc*dll or two.
The FF-devel build uses the mzfntcfgft package that was a requirement since FF10.0.12 and mmap.dll. Either the RPM installed or the one I built without the gcc dll dependency as they are interchangeable.
I would have statically linked mmap.dll but it causes socket problems.

Dave Yeo:
I've posted the forgotten xqs files, https://bitbucket.org/dryeo/dry-comm-esr24/downloads/firefox-dev-24.8.1.b4.en-US.os2.xqs.zip.
Also a reminder that my builds are not associated with Bitwise other then using much of the same code so issues should only be raised with them if reproducible with their build.

Dariusz Piatkowski:
Dave!

Thank you!!! FF is chugging away here real nice...I have to say the initial assessment is positive, looks like it's noticeably faster as compared to the 17x releases.

I did start on the install of the Bitworks release, but the DLL nightmare just got to be too much...and attempting to pull aparts RPMs didn't even work for me...so thanks again for coming through with this.

Dmitriy Kuminov:
Dariusz, what exactly do you mean by the DLL nightmare? And what was the problem with RPMs?

Dariusz Piatkowski:

--- Quote from: Dmitriy Kuminov on March 23, 2015, 11:00:10 pm ---Dariusz, what exactly do you mean by the DLL nightmare? And what was the problem with RPMs?

--- End quote ---

Hi Dimitriy,

Well, basically I pulled the Bitworks published Firefox release which then required a number of RPM packages. I do not use RPM/YUM, I have been relying on ZIP releases mostly because it gives me control over what goes where and my setups are rather simple and I'm trying to keep it that way:

1) g:\os\dll
2) g:\usr\dll
3) g:\usr\bin

...I attempt to keep the duplicate DLLs to a minimum. Basically all non-IBM OS/2 dlls go to \usr\dll.

For whatever reason, I could not extract the needed DLLs out of the RPM packages (using ArchiveView and consistently getting "SYS1092: The handle could not be duplicated during a pipe operation.
" error), and so the minute that failed it was a dead-end...

While I understand the eventual simplicity of relying on RPM/YUM it just seems like we're not quite there yet. So in terms of testing out these beta release it just seems like it would be so much simpler to get a ZIP Firefox release and a matching ZIP release of all the required DLLs.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version