Penelope Developer Page: Difference between revisions

Jump to navigation Jump to search
Wrong section indenting for Windows
(Clarify Thunderbird vs. Penelope in a couple of places)
(Wrong section indenting for Windows)
Line 60: Line 60:
Note that it is this last line that includes the building the Penelope extension in the main build.  The source code for Penelope can be found in mozilla/penelope.
Note that it is this last line that includes the building the Penelope extension in the main build.  The source code for Penelope can be found in mozilla/penelope.


== Building Penelope on Windows ==
=== Building Penelope on Windows ===


See the steps above under Linux for how to get the source code via CVS.
See the steps above under Linux for how to get the source code via CVS.
Line 81: Line 81:
* make -f client.mk build
* make -f client.mk build


=== Visual Studio .NET 2003 and Service Pack 1 ===
==== Visual Studio .NET 2003 and Service Pack 1 ====


You must install Service Pack 1 in order to successfully build.  You can find Service Pack 1 [http://www.microsoft.com/downloads/details.aspx?familyid=69d2219f-ce82-46a5-8aec-072bd4bb955e&displaylang=en here].  There's one aspect to installing the Service Pack that can be somewhat tricky.  At a point during the install of the Service Pack it will ask you for the <code>vs_setup.msi</code> file of the original Visual Studio installer.  You must have the exact original installer that you personally used, otherwise the Service Pack upgrade won't continue on.  The Service Pack installer is woefully slow, and has bad UI as well.  Know that if you run it there will be places where there are long pauses (I had one that was around 15 minutes).  The release notes for the SP [http://support.microsoft.com/default.aspx?scid=kb;en-us;924009#70 detail this].
You must install Service Pack 1 in order to successfully build.  You can find Service Pack 1 [http://www.microsoft.com/downloads/details.aspx?familyid=69d2219f-ce82-46a5-8aec-072bd4bb955e&displaylang=en here].  There's one aspect to installing the Service Pack that can be somewhat tricky.  At a point during the install of the Service Pack it will ask you for the <code>vs_setup.msi</code> file of the original Visual Studio installer.  You must have the exact original installer that you personally used, otherwise the Service Pack upgrade won't continue on.  The Service Pack installer is woefully slow, and has bad UI as well.  Know that if you run it there will be places where there are long pauses (I had one that was around 15 minutes).  The release notes for the SP [http://support.microsoft.com/default.aspx?scid=kb;en-us;924009#70 detail this].


=== Windows Vista ===
==== Windows Vista ====


Windows Vista provides some roadblocks in compiling Thunderbird.  The first is the new security model.  By default, administrator accounts under Vista run applications at a reduced privilege level called Standard User.  Microsoft found that the most common legitimate reason to need administrator rights was when installing an application, and in order for all the existing installation programs to work under Vista they had to come up with a heuristic workaround.  What Vista does is automatically attempt to elevate the privilege of any application that has the words "install" or "setup" in the name of the executable filename.  I say "attempt" because there appear to be some situations where the privilege elevation fails, and one of those happens to be when called inside of scripts.  I think it has to do with the way the process is created (privilege elevation happens when you call ShellExecute(), but not when CreateProcess() is used), but I'm not sure of that entirely because I don't know how Cygwin shells start up new processes.
Windows Vista provides some roadblocks in compiling Thunderbird.  The first is the new security model.  By default, administrator accounts under Vista run applications at a reduced privilege level called Standard User.  Microsoft found that the most common legitimate reason to need administrator rights was when installing an application, and in order for all the existing installation programs to work under Vista they had to come up with a heuristic workaround.  What Vista does is automatically attempt to elevate the privilege of any application that has the words "install" or "setup" in the name of the executable filename.  I say "attempt" because there appear to be some situations where the privilege elevation fails, and one of those happens to be when called inside of scripts.  I think it has to do with the way the process is created (privilege elevation happens when you call ShellExecute(), but not when CreateProcess() is used), but I'm not sure of that entirely because I don't know how Cygwin shells start up new processes.
145

edits

Navigation menu