Closed
Bug 129492
Opened 22 years ago
Closed 22 years ago
Need to package embed.jar on Mac for PPEmbed
Categories
(Core Graveyard :: Embedding: APIs, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: mikepinkerton, Assigned: mikepinkerton)
References
Details
(Keywords: topembed+)
Attachments
(1 file, 4 obsolete files)
11.69 KB,
patch
|
mikepinkerton
:
review+
sfraser_bugs
:
superreview+
shaver
:
approval+
|
Details | Diff | Splinter Review |
Mac embedding clients need Embed.jar created. Right now, it's only built on win and unix. It really should be done as part of our normal build process (with a build option), but MacPerl is such the ugly step-sister. Would it be totally out of bounds to tell people to run the scripts with cmd-line perl on OSX? Just a thought.
Assignee | ||
Updated•22 years ago
|
Assignee | ||
Updated•22 years ago
|
Updated•22 years ago
|
QA Contact: mdunn → depstein
Assignee | ||
Comment 1•22 years ago
|
||
cc'ing adam for r= of upcoming patch.
Assignee | ||
Comment 2•22 years ago
|
||
this patch is in two parts: 1) changes to gen_mn.pl to break out the routines that do the work into a package so that it can be called from a script by MacPerl as well as by the command line from the make system. I had to tweak some things to get them working with macperl (such as using opendir() instead of "ls -1 |", etc). 2) changes to the mac perl build scripts to use this script and mimic the wonkyness of the win/unix embedding packaging system. don't shoot the messenger ;) needing r/sr. if both conrad and adam could look over these, it would be great.
Comment 3•22 years ago
|
||
if $main::options{chrome_jars} == 0 (the way I usually build), DumpChromeToTemp() wouldn't work. If that was the case, couldn't it just set the temp dir to be the un-jarred chrome dir and still work?
Looks ok except for missing newline at the end of GenerateManifest.pm. It still works on Linux/Win32 right? r=adamlock
Assignee | ||
Comment 5•22 years ago
|
||
fix to not un-jar if building with jars.
Attachment #73256 -
Attachment is obsolete: true
Assignee | ||
Comment 6•22 years ago
|
||
adam, i did some cursory testing with osx's command line perl, but not entirely. do you mind giving this a quick test on win32 or unix? thanks!
Comment 7•22 years ago
|
||
Comment on attachment 73267 [details] [diff] [review] do the right thing if not building with jars r=ccarlen. Should there be a build flag "build_embedding_dist" which would turn on "embedding_chrome", "embedding_xul", and copy PPEmbed to that location. Then we'd have a smoketestable PPEmbed build.
Attachment #73267 -
Flags: review+
Assignee | ||
Comment 8•22 years ago
|
||
conrad, that's my next goal, beyond the scope of this bug ;)
I'm getting this error on Win32. I won't be able to check on Linux because my Unix is machine is currently out of action: ..\..\dist\WIN32_D.OBJ\Embed\tmpchrome\toolkit/content/global/bindings/tree.css inflating: ..\..\dist\WIN32_D.OBJ\Embed\tmpchrome\toolkit/content/global/bindings/wizard.xml Too many arguments for GenerateManifest::parse_input_manifest at GenerateManifest.pm line 142, near "$verbose)" Too many arguments for GenerateManifest::dump_output_manifest at GenerateManifest.pm line 143, near "$verbose)" BEGIN not safe after errors--compilation aborted at GenerateManifest.pm line 238. BEGIN failed--compilation aborted at gen_mn.pl line 7. NMAKE : fatal error U1077: 'perl.exe' : return code '0xff' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\NMAKE.EXE"' : return code '0x2' Stop.
Assignee | ||
Comment 10•22 years ago
|
||
ok, win issues straightened out. just need to do + sub GenerateManifest { instead of + sub GenerateManifest() { with that change, it works dandy (says adam). now i just need sr.
Assignee | ||
Comment 11•22 years ago
|
||
Attachment #73267 -
Attachment is obsolete: true
Comment 12•22 years ago
|
||
Comments: +sub GenerateManifest { and other subroutines. It's better to do sub GenerateManifest($$$$$$$) { because then perl can then check the number of params at compile-time (assuming that we don't rely on variabe # params behavior). + open(MANIFEST, "<$manifest") or die ("Error: Cannot open manifest \"$manifest\".\n"); MANIFEST is never closed. It's better to use local file handles too. +1; \ No newline at end of file Fix this. + # Need to do this dynamically, because this module can be used before + # mozilla/config has been checked out. Is this true in this case?
Assignee | ||
Comment 13•22 years ago
|
||
Attachment #73283 -
Attachment is obsolete: true
Assignee | ||
Comment 14•22 years ago
|
||
address all smfr's comments in the patch, tested on win32 and macos. works just dandy. smfr? can you sr?
Attachment #73570 -
Attachment is obsolete: true
Assignee | ||
Updated•22 years ago
|
Attachment #73688 -
Flags: review+
Comment 15•22 years ago
|
||
Comment on attachment 73688 [details] [diff] [review] tweak some more things for smfr ($$'s and local file handle) That'll do, pink. sr=sfraser
Attachment #73688 -
Flags: superreview+
Updated•22 years ago
|
Comment on attachment 73688 [details] [diff] [review] tweak some more things for smfr ($$'s and local file handle) a=shaver for 1.0 trunk.
Attachment #73688 -
Flags: approval+
Assignee | ||
Comment 17•22 years ago
|
||
landed on trunk.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 18•22 years ago
|
||
verified patch against Mozilla 1.0.0 5/14/02 build.
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•