Optimized Mach-O build available

[Zach Lipton]

For those who have been wanting to try the Mach-O build of Mozilla on Mac OS
X, but aren't able to build the source, you can now download a binary
install from
http://ftp.mozilla.org/pub/mozilla/nightly/experimental/macho/mozilla-osX-ma
cho-11-21.dmg.sit.bin which includes everything you need.

Read the README file inside for details and report all problems ASAP.

If this is popular, I plan to do nightly or weekly mach-o builds so that the
bugs can be squashed.

Zach

[Jason Quigley]

Hi Zach!

This definitely feels a lot snappier.

One question: Where is prefs.js?

Thanks,
Jason.

[Zach Lipton]

I'm glad that it works for you. I need to find out about doing nughtlys or
weeklys of this. The build options that I used aren't very good either (no
chatzilla, etc) but I'll tweek that as well. '

For prefs.js, I think that it is in your users directory in the .mozilla
folder. It won't show up in the finder unless you used tinkertool to show
hidden folders, but you can access it using terminal. The linebreaks are
most likely unix, so you will need to use a commandline editor like pico or
vi or emacs to edit it.

Zach

On 11/22/01 3:33 AM, in article 3BFCE298...@mac.com, "Jason Quigley"

[Zach Lipton]

I failed to mention in this post that this build includes everything you
need for Mozilla Calendar including an exclusive mac os x libical binary
installer. If you have wanted to see Mozilla Calendar, this is your chance!

Zach

On 11/21/01 5:53 PM, in article B8219A89.11D60%za...@zachlipton.com, "Zach

[strobe anarkhos]

In article <B8219A89.11D60%za...@zachlipton.com>, Zach Lipton <za...@zachlipton.com> wrote:

> For those who have been wanting to try the Mach-O build of Mozilla on Mac OS
> X, but aren't able to build the source, you can now download a binary
> install from
> http://ftp.mozilla.org/pub/mozilla/nightly/experimental/macho/mozilla-osX-ma
> cho-11-21.dmg.sit.bin which includes everything you need.

Hm, is this build creating a ~/.mozilla folder? I thought Mozilla used the :preferences folder

[strobe anarkhos]

I tried to quit it from the Dock, but it didn't respond. Are AppleEvents broken?

[Zach Lipton]

This is a unix version running on the mac meaning that it creates profiles
where unix does. If you want this changed to use ~/Library/Preferences, file
a bug... CC me on it please, za...@zachlipton.com

Zach

On 11/22/01 1:09 PM, in article 221120011309166635%anar...@nospam.mac.com,

[Marcus G. Daniels]

ZL> For those who have been wanting to try the Mach-O build of Mozilla on Mac OS
ZL> X, but aren't able to build the source, you can now download a binary

Working fine! :-)

[Brian Clark]

I installed it without any problems at all. Works great. I have
noticed a noticible speed improvement in page rendering. For example,
freshmeat.net renders at least twice as fast as the carbon version of
Mozilla.

Brian!

[Kimon Tsinteris]

I second that! All pages I have surfed to so far have rendered faster, and
having timed against the same cfm build from the 21st, I have found a number
of pages to load 2X+ as fast! Great accomplishment!

-Kimon

On 25/11/01 13:19, in article
9fd64bcb.0111...@posting.google.com, "Brian Clark"

[Brian Clark]

Why does this identify itself as Build ID 0000000000? Shouldn't it be
something like 11-21-2001? Should I file a bug about this?

Brian!

[Dan McDonald]

In article <B8219A89.11D60%za...@zachlipton.com>,
Zach Lipton <za...@zachlipton.com> wrote:

>For those who have been wanting to try the Mach-O build of Mozilla on Mac OS
>X, but aren't able to build the source, you can now download a binary

<SNIP!>

AWESOME!

Okay, here's one us UNIX-heads can use. The Mach-O works great off of a UFS
partition (my biggest and really only beef with CFM currently). Hmmm, as an
aside, I wonder if it's a MacOS bug that disables Mozilla running off a UFS
partition?

Anyway, if you wish to share preferences between CFM and Mach-O, try
symlinking to your ~/Library/Mozilla/Profiles/<you>/????.slt. Here is the
breakdown:

1.) Run Mozilla Mach-O for the first time.

2.) Get into a shell (aka run Terminal).

3.) "cd .mozilla/Profiles"

4.) "mv default orig" (This moves the Mach-O created default
profile over.)

5.) "ls orig", and make note of the name of the ????.slt directory.
For this example, we'll call it $ORIG.slt

6.) "mkdir default".

7.) "cd default"

8.) "ln -s ../../../Library/Mozilla/Profiles/<you>/????.slt
$ORIG.slt"

You now have Mach-O AND CFM looking at the same prefs. I haven't tried MUCH
here (e.g. adding bookmarks in one, etc.), but it sorta works.

BTW, with UFS support in place, I'd be very interested in getting Mach-O
promoted to full citizen status in the Mozilla community. If building this
works with ProjectBuilder and/or the special gcc we need, I could even start
cranking builds.
--
Daniel L. McDonald - Kebe Software & Services
Mail: dan...@kebe.com <*> | "rising falling at force ten
WWW: http://www.kebe.com/~danmcd | we twist the world and ride the wind"
Other info available upon request. | - Rush

[Mike Pinkerton]

before people get too carried away in a panic, we know there are TONS of
issues with the mach-o builds, such as filepickers not working, apple
event support not working, no splash screen, profiles in .mozilla, etc.

we just wanted to land the darn thing in the tree. it's not meant to
replace the CFM build by any stretch. These un-maclike things will be
fixed in good time.

Don't panic.

Zach Lipton wrote:

> This is a unix version running on the mac meaning that it creates profiles
> where unix does. If you want this changed to use ~/Library/Preferences, file
> a bug... CC me on it please, za...@zachlipton.com

--
Mike Pinkerton
Mac Browser Weenie
pink...@netscape.com http://people.netscape.com/pinkerton

[Conrad Carlen]

I ran the optimized Mach-o build against the Carbon build from 20011120
on jrgm's page loader: 5 cycles, no cache, and the median time for all
pages was:

Carbon: 3348 millisecs
Mach-o: 2962 millisecs

While not 2x faster, a significant improvement. I would have included
the results from the test but the Mach-o build crashed when trying to
save it :-/

-Conrad

[Darin Fisher]

Here's some more numbers taken using a G4 533MHz w/ 256Mb of RAM running
MacOSX 10.1:

For this set, I tested the 3 browsers using zdnet's ibench test (hosted
on dogspit.nscp.aoltw.net).

Netscape 6.2
------------
Total: 479.18
First: 59.78
Subsequent: 59.91

Mozilla [20011126/08]
---------------------
Total: 340.48
First: 41.45
Subsequent: 42.72

Zach's Mach-O Build
-------------------
Total: 290.76
First: 36.95
Subsequent: 36.26

For this second set, I tested the 3 browsers using jrgm's page-loader
(hosted on cowtools.nscp.aoltw.net).

Netscape 6.2
------------
Avg. Median: 2118 msec

Mozilla [20011126/08]
---------------------
Avg. Median: 1788 msec

Zach's Mach-O Build
-------------------
Avg. Median: 1326 msec

So, under ibench, Mach-O is roughly 15% faster, and under cowtools, it
is more like 26% faster. Definitely, not 50% faster... but certainly a
big improvement... very noticeable if you use the build :)

-darin

[Zach Lipton]

Don't bother filing a bug on this. I set the build options wrong and it
ended up at the default which is 0000000000. Because I was lazy and this was
a one-time manual thing, I didn't see much reason to go back and do it
again. This will be fixed later.

Zach

On 11/25/01 10:00 PM, in article
9fd64bcb.01112...@posting.google.com, "Brian Clark"

[Conrad Carlen]

The difference in your numbers and mine and why my speedup on jrgm's
page loader was smaller was due to connection speed and that I ran mine
without caching. Slower net access is the great equalizer. Still, more
data collected under different conditions is good to have.

-Conrad

[Will E. LumpLump]

I am not a programmer or anything like that. I just want to say that
this build is a lot faster for me than the carbon build of mozilla. I
mean it really flies. Keep up the good work, if you can get this build
out to the mainstream user, IE stands no chance. Thanks again for the
hard work.