Closed Bug 532621 Opened 10 years ago Closed 10 years ago
Allow to build gnomevfs handler extension with --disable-gnomevfs
Make possible to build gnomevfs extension without enabled-gnomevfs
Attachment #415836 - Flags: review?(ted.mielczarek)
Can you explain why you want this, and what it would be useful for? I don't understand the rationale.
I don't want to have enabled some staff which is available only with GNOMEVFS enabled, but I want to have gnomevfs extension to be able to handle obex, smb e.t.c....
Comment on attachment 415836 [details] [diff] [review] gnomevfs build config >#BMO bug needed >diff -r 0656a43e60de configure.in >--- a/configure.in Tue Aug 04 21:15:44 2009 +0300 >+++ b/configure.in Tue Aug 04 23:44:32 2009 +0300 >@@ -5221,6 +5221,12 @@ then > fi > MOZ_ENABLE_GNOMEVFS= > ]) >+ else >+ if test `echo "$MOZ_EXTENSIONS_DEFAULT" | grep -c gnomevfs` -ne 0; then I think you want $MOZ_EXTENSIONS, not _DEFAULT here. I really hate that we have GnomeVFS code split between toolkit and extensions in the first place, but I guess I just hate extensions/ in general, so I filed bug 536237 on that. r=me with that change.
Attachment #415836 - Flags: review?(ted.mielczarek) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Version: 1.9.2 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.