353983 - --enable-application=netwerk (standalone necko)

Status: RESOLVED FIXED

(Core :: Networking, defect)

Description

[Christian :Biesinger (don't email me, ping me on IRC)]

To make it possible to build standalone Necko, I want to add an --enable-application=netwerk compile option. This builds just the libraries that Necko needs (essentially XPCOM, libpref, intl and necko itself).

This adds a tier_necko which contains parts of tier_gecko.

NOTE: I had to name this netwerk rather than necko because the build system expects a mozilla/$(MOZ_BUILD_APP)/build.mk file. I could add a necko alias if desired.

Also, it is not really possible to run the unit tests here, because almost all of them need xpcshell and therefore xpconnect, which is not build in this configuration. Perhaps --enable-tests should build it.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

Attachment: patch

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

Attachment: patch v2

Now with client.mk changes. Also, fixes the condition for the libreg build, this is the change:
-ifneq (,$(MOZ_NO_XPCOM_OBSOLETE)$(MOZ_XPINSTALL))
+ifneq (1_,$(MOZ_NO_XPCOM_OBSOLETE)_$(MOZ_XPINSTALL))

That should lead to the desired result of libreg being built if xpcom-obsolete is built or if xpinstall is built (or both)

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

Attachment: patch v3

oops. fix BOOTSTRAP variables. sorry for the bugspam...

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

Comment on attachment 239850 [details] [diff] [review]
patch v3

+  mozilla/extensions/auth                       \

looks like this has to be removed, or normal checkouts will be broken :(

Comment 5

[Darin Fisher]

Comment on attachment 239850 [details] [diff] [review]
patch v3

I'm fine with this provided bsmedberg is happy with the build details.

Comment 6

[Christian :Biesinger (don't email me, ping me on IRC)]

checked in

Comment 7

[Nickolay_Ponomarev]

There's no documentation for this, right? Adding dev-doc-needed, as at the very least various outdated docs on MDC should be updated to say that standalone necko builds are possible.

Comment 8

[Fernando Cassia]

And so it transpires that Google decided to code their own networking implementation from scratch for use in its upcoming Chrome 2.0 browser.

Great work, Mozilla.org! (NOT!). You guys missed a great chance to have the Mozilla networking libs used by another major software player.

I guess nobody even thought of approaching Google to make them use Necko when they were having trouble porting Chrome to non-Windows platforms due to its reliance on WinHTTP, right?

Well, too late now...

FC

Comment 9

[Fernando Cassia]

http://dev.chromium.org/getting-involved/dev-channel/release-notes/releasenotes201561

Comment 10

[(not currently active) Ted Mielczarek]

You know that Darin Fisher (one of the lead engineers on Chrome) used to be the owner of our network module, right? I don't think this was due to lack of knowledge of the existence of necko.

Comment 11

[Eric Shepherd [:sheppy]]

So what would a .mozconfig file for this look like?  Just

ac_add_options --enable-application=netwerk

Or would more stuff be needed as well?  I'm working on documenting this at:

https://developer.mozilla.org/En/Building_Necko_standalone