Closed
Bug 286729
Opened 20 years ago
Closed 20 years ago
libXUL step 4 - rest of toolkit
Categories
(Toolkit Graveyard :: Build Config, defect)
Toolkit Graveyard
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.8beta2
People
(Reporter: benjamin, Assigned: benjamin)
Details
Attachments
(1 file)
|
36.89 KB,
patch
|
darin.moz
:
first-review+
|
Details | Diff | Splinter Review |
This incorporates pretty much all of the rest of toolkit into libxul. I've discovered some interesting/awful build dependencies here that I will fix later.
| Assignee | ||
Comment 1•20 years ago
|
||
Please ignore the UI changes in xpfe/components/console and toolkit/componnets/console, they are for another bug.
Attachment #177867 -
Flags: first-review?(darin)
Comment 2•20 years ago
|
||
Comment on attachment 177867 [details] [diff] [review] libxul, step 4, revision 1 So xul.dll now contains nsAppRunner.cpp? (sounds good) And xulrunner.exe has its own copy of nsINIParser.cpp :-/ And, you are for the first time making XUL.dll be something people may directly link against? Seems like some big changes happening here.
| Assignee | ||
Comment 3•20 years ago
|
||
> So xul.dll now contains nsAppRunner.cpp? (sounds good) Yes. > And xulrunner.exe has > its own copy of nsINIParser.cpp :-/ Yes. > And, you are for the first time making > XUL.dll be something people may directly link against? Define "people"... xulrunner.exe links against it, but it already does, so it's not a revolutionary change. It's true that this is the first time we're exporting XRE_main, but so what? I do intend to freeze it for 1.9, if not before.
Comment 4•20 years ago
|
||
My point was that this is us moving toward having end consumers link against xul.dll as well as xpcom.dll to embed us. I think that's fine, and I think we've talked about doing that, but perhaps you should update the libxul wiki to talk about this.
Comment 5•20 years ago
|
||
Comment on attachment 177867 [details] [diff] [review] libxul, step 4, revision 1 >Index: Makefile.in >+ifdef MOZ_ENABLE_LIBXUL >+tier_50_dirs += \ >+ toolkit/library \ >+ xpcom/stub \ >+ $(NULL) >+endif >+ >+ifdef MOZ_PSM >+tier_50_dirs += security/manager >+endif Eventually, we'll want to fold PSM into LibXUL. NSS itself should probably remain standalone since it installed as a system library on some linux distros already. >Index: chrome/Makefile.in >-DIRS = public src tools >+DIRS = public src >+ >+TOOL_DIRS = tools I kind of like the indented variable values myself, but no biggy. >Index: toolkit/profile/src/nsToolkitProfileService.cpp >+extern "C" XULAPI nsresult >+XRE_GetFileFromPath(const char *aPath, nsILocalFile* *aResult) nit: when implementing these methods there's no need to include the |extern "C" XULAPI| prefix provided you #include the header file where they are declared. It shouldn't matter, but in xpcom that's the convention we use. >Index: toolkit/xre/nsXULAppAPI.h >+#ifdef MOZ_ENABLE_LIBXUL >+#ifdef IMPL_XULAPI >+#define XULAPI NS_EXPORT >+#else >+#define XULAPI NS_IMPORT >+#endif >+#else >+#define XULAPI >+#endif So, consumers will need to #define MOZ_ENABLE_LIBXUL if they wish to import these functions, right? Hmm... we might change that in the future to make it the default. r=darin
Attachment #177867 -
Flags: first-review?(darin) → first-review+
| Assignee | ||
Comment 6•20 years ago
|
||
This was checked in last Friday.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8beta2
| Assignee | ||
Updated•18 years ago
|
Flags: in-testsuite-
Updated•6 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•