출처: http://sweeper.egloos.com/1792751


1. Static library

Dynamic (linking) library (흔히 얘기하는 DLL)을 설명하기 위해 간단하게 정리한다.

특정 기능의 라이브러리를 static 하게 제작한다는 것은 link 단계에서
라이브러리(*.lib 파일)를 실행 바이너리에 포함시킨다는 얘기이다.

즉, 라이브러리의 동작 코드가 이를 사용하는 실행 바이너리 속에
포함되기 때문에 별도의 추가 작업없이, 그리고 독립적으로(실행 바이너리만으로...)
라이브러리 함수들을 사용할 수 있다.

하지만, 정적 라이브러리를 사용하는 프로그램이 늘어나면 날수록
불필요하게 실행 파일들의 크기가 커지며,
라이브러리가 동시에 여러 실행 바이너리에 포함되어 실행되는 경우
메인 메모리의 공간 활용 효율이 떨어지는 등 multiple-caller가 존재하는 경우 그다지 바람직하지 않다.

정적 라이브러리를 사용하기 위해서는 프로젝트 설정의 Link 옵션에
라이브러리를 추가해 주거나 아래의 #pragma 지시자를 사용하면 된다.

#pragma comment(lib, "NAME.lib")


2. Dynamic (linking) library : DLL

말 그대로 "동적으로 링크하여 사용하는 라이브러리" 이다.

동적 라이브러리는 이를 사용하고자 하는 실행 바이너리에서
필요시 사용할 수 있도록 최소한의 정보만 포함하여 링크하거나,
아예 독립적으로 DLL을 로드/사용/해제할 수 있다.

1) Implicit linking

DLL을 구현하고 컴파일하고 나면 static library와는 다르게  output file이 2개 생성된다.
하나는 *.lib 파일이고 하나는 *.dll 파일이다.
여기서 *.lib 파일은 static library의 *.lib 파일과는 전혀 다르다.

Static library의 *.lib 파일은 라이브러리 전체 코드를 포함하는 바이너리이며,
DLL의 *.lib 파일은 DLL이 제공하고자 하는 함수 정보(함수명)을 가지는 정보 파일이다.

DLL의 *.lib 파일을 이용하여 링킹하는 것을 암시적 링킹(implicit linking)이라고 한다.
실행 바이너리를 링크 단계에서 실행 바이너리의 *.obj 파일들과 DLL의 *.lib 파일을
함께 링크하여 이 정보를 토대로 runtime에 DLL의 함수 코드를 참조하게 되는 것이다.
(한 줄로 요약하면 *.lib 파일은 링크시 필요하고, *.dll 파일은 실행시 필요하다)

정적 라이브러리를 사용할 때와 같이 프로젝트 설정의 Link 옵션에
라이브러리를 추가해 주거나 아래의 #pragma 지시자를 사용하면 된다.

#pragma comment(lib, "NAME.lib")

2) Explicit linking

명시적 링킹에서는 *.lib 파일이 필요하지 않다.
실행 바이너리 링크 단계에서 DLL의 함수 정보가 필요하지 않기 때문이다.

명시적 링킹에서 사용되는 세 가지 함수와 역할은 다음과 같다.

1. LoadLibrary : 필요한 DLL을 프로세스 가상 메모리에 맵핑한다.
2. GetProcAddress : DLL 함수의 포인터를 획득한다.
3. FreeLibrary : 프로세스 가상 메모리에서 DLL을 반환한다.

프로세스는 내부적으로 DLL의 레퍼런스 카운트를 계산한다.
LoadLibrary 호출시 DLL의 (프로세스) 레퍼런스 카운트는 1씩 증가하고,
FreeLibrary 호출시 레퍼런스 카운트가 1씩 감소한다.
레퍼런스 카운트가 0이 될 때 해당 DLL은 프로세스 가상 메모리에서 해제된다.

여기서 주의할 점이 물리 메모리가 아닌 가상 메모리에서의 반환(해제)라는 것이다.
레퍼런스 카운트는 각 프로세스 내부의 호출 회수이지,
전체 프로세스 간의 호출 회수가 아니라는 것이다.

이러한 레퍼런스 카운트를 두는 이유는 프로그램 실행 중에
DLL을 가상 메모리에 할당, 해제할 수 있도록 하기 위함이다.
(Implicit linking 방식에서는 이러한 장점을 얻을 수 없다.)

정리해서 명시적 링킹의 장점을 세 가지 정도 정리해 보면...

1. DLL이 필요한 시점에서 로딩하고, 불필요해지면 반환하기 때문에 메모리가 절약된다.
2. 프로그램 실행 중에 DLL 교체 및 선택이 가능하다.
3. 암시적 링킹은 프로그램 실행 전에 필요한 모든 DLL을 메모리에 로딩한다.
때문에 실행까지 걸리는 시간이 길어질 수 있다. 반면에 명시적 링킹은 필요한 순간에
하나씩 DLL을 로딩할 수 있기 때문에 그만큼 실행까지 걸리는 시간이 짧고,
DLL 로딩에 걸리는 시간을 분산시킬 수 있다.

뭐 위와 같이 명확한 장점들이 있음에도 불구하고 암시적 링킹이 더 선호되는 경우가 있는데,
이는 사용하기 쉽기 때문이다. 코드가 간결해 진다는 것, 사용하기 쉽다는 것은
대부분의 경우에 있어서의 성능보다도 더 큰 장점을 지니는 것이 아닌가 생각해 본다.

출처: http://mores.tistory.com/210

출처: http://www.tipssoft.com

Windows 프로그램을 하다 보면 Z order라는 말을 종종 접한다. 하지만, 그 의미가 무엇인지를 정확하게 아는 사람이 별로 없는 것 같아서 이렇게 소개한다.

"Z Order"는 어떤 창들이 다른 창들 뒤에 가려져야 하는지를 결정하는 방법이다. 좀더 자세하게 이야기하면 "A 윈도우의 Z Order"는 겹쳐서 쌓아 올려진 윈도우들 중에서 A 윈도우의 위치라고 할 수 있다.

우리가 보는 화면은 2차원적이다. 따라서 X축과 Y축으로 모든 것을 표현한다. 하지만 개념적으로 볼 때, 겹쳐진 윈도우들은 3차원적인 의미를 가지고 있다. 따라서 가상의 축(Imaginary Axis)을 하나 더 생각해야 한다. 이 측을 Z축이라고 하면 아래와 같이 표현될 것이다.

위 그림을 보면 알 수 있듯이 Z 축의 값이 겹쳐진 순서의 위치 임을 알 수 있다. 이것을 보면 왜 Z Order라는 용어를 사용하는 그 이유를 알 수 있을 것이다.

Windows는 기본적으로 Single List를 이용하여 Z Order를 관리한다. 그리고 Windows는 이 윈도우들이 topmost(top-level) 윈도우인지 또는 child 윈도우인지를 고려한 Z Order를 추가적으로 관리한다.

Topmost 윈도우들은 모든 non-topmost 윈도우들보다 더 위쪽에 출력된다. 이때, non-topmost 윈도우가 활성화되어 있다든지 가장 앞쪽에 있다는 것과 같은 상황은 무시된다. 이런 Topmost 윈도우들은 자신의 확장속성에 WS_EX_TOPMOST라는 속성을 가지고 있다. 그리고 child 윈도우들은 그것의 Parent 윈도우의 Z Order에 의해서 그룹 지어진다.

응용 프로그램에서 새로운 윈도우를 하나 생성시키면 Windows 시스템은 동일한 형태(topmost이든지 non-topmost)의 윈도우들이 가지는 Z Order에서 가장 위쪽의 값을 부여한다. 그리고 동일한 형태의 윈도우들간에 Z Order를 가장 높이고 싶다면 BringWindowToTop이라는 함수를 이용하면 된다.

SetWindowPos 와 DeferWindowPos 함수를 이용하여 윈도우의 Z Order를 재정렬 할 수도 있다.

이올린에 북마크하기

Volatile

volatile int k; 

void ThreadEntry(void* pParm) 

{ 

    bool* pbExit = static_cast<bool*>(pParm); 

    int i = 0; 

    

    while( !*pbExit) 

    { 

        i++; 

    } 

    

    printf("i = %d\n" ,i); 

} 

volatile bool* pbExit = static_cast<volatile bool*>(pParm); 

; 12   : bool* pbExit = static_cast<bool*>(pParm); 

; 13   : int i = 0; 

; 14   : 

; 15   : while( !*pbExit) 



  00000 8b 4c 24 04 mov ecx, DWORD PTR _pParm$[esp-4] 

  00004 33 c0 xor eax, eax 

  00006 80 39 00 cmp BYTE PTR [ecx], 0 

  00009 75 03 jne SHORT $L42424 

$L42423: 



; 16   : { 

; 17   : i++; 



  0000b 40 inc eax 



; 12   : bool* pbExit = static_cast<bool*>(pParm); 

; 13   : int i = 0; 

; 14   : 

; 15   : while( !*pbExit) 

////////////////////////////////////////////////////////// 

// 이 부분 보이시죠? 비교도 안하고 무조건 점프하는 모습!! 

  0000c eb fd jmp SHORT $L42423 -> 

$L42424: 



; 18   : } 

; 12   : volatile bool* pbExit = static_cast<volatile bool*>(pParm); 

; 13   : int i = 0; 

; 14   : 

; 15   : while( !*pbExit) 



  00000 8b 4c 24 04 mov ecx, DWORD PTR _pParm$[esp-4] 

  00004 33 c0 xor eax, eax 

  00006 80 39 00 cmp BYTE PTR [ecx], 0 

  00009 75 07 jne SHORT $L42424 

$L42423: 



; 16   : { 

; 17   : i++; 



0000b 40 inc eax 

//////////////////////////////////////////////// 

// 이 부분 보이시죠?? 비교해서 분기하는 모습!! 

  0000c 8a 11 mov dl, BYTE PTR [ecx] 

  0000e 84 d2 test dl, dl 

  00010 74 f9 je SHORT $L42423 

$L42424: 



; 18   : } 

출처: http://www.winapi.co.kr/clec/cpp2/15-1-4.htm

출처: http://www.edm2.com/0201/hooks.html

Introduction Beginning with the MVS operating system, user exits have existed in order to give those with a bit of programming skill the opportunity to change the default behavior for a particular event. Since then, these have evolved into system hooks, which provide the same ability; unfortunately, whether known as user exits or system hooks, there has been a lack of documentation on how to utilize these provisions from with OS/2 applications. This article will discuss what hooks are, what the different types of hooks are, and the uses of some of the various types of hooks. Finally, we will look at a (new) version of Life Saver, which uses one of the hooks to implement a screen saver. Going Fishing? What is a hook? In the sport of fishing, a hook attaches the fishing line) to the fish so that the line follows the movement of the fish. In programming, the concept is similar - you use a hook to attach your application to an event so that your application knows whenever the event occurs. Why is this useful? Consider an application that needs to know when the system is rebooting, or needs to know whenever the PrintScreen key was pressed (regardless of who has the focus). These types of things can only be done with hooks. OS/2 defines 17 types of hooks that can be set. Send message event (HK_SENDMSG) The hook is invoked whenever WinSendMsg() is called. Input event (HK_INPUT) The hook is invoked whenever WinPostMsg() is called, including - and especially - for all mouse and keyboard input. Message filter (HK_MSGFILTER) The hook is invoked during any Win function which enters a message loop, e.g. WinDlgBox(), WinMessageBox(), etc. Journal record (HK_JOURNALRECORD) The hook is invoked to record (journal) a message. Journal playback (HK_JOURNALPLAYBACK) The hook is invoked to play back a journaled message. Help event (HK_HELP) The hook is invoked whenever help is requested by the user or an application. Library and procedure event (HK_LOADER) The hook is invoked whenever WinLoadLibrary() or WinLoadProcedure() is called. User message registration event (HK_REGISTERUSERMSG) The hook is invoked whenever WinRegisterUserMsg() is called. Message control event (HK_MSGCONTROL) The hook is invoked whenever any of the following four functions are called: WinSetClassMsgInterest(), WinSetMsgInterest(), WinSetMsgMode(), and WinSetSynchroMode(). Find word event (HK_FINDWORD) The hook is invoked whenever a word to be drawn by the WinDrawText() function is too long to fit within the bounding rectangle. Code page change event (HK_CODEPAGECHANGED) The hook is invoked whenever a message queue's code page changes. Device context association event (HK_WINDOWDC) The hook is invoked whenever a device context is associated with a window. Window destroy event (HK_DESTROYWINDOW) The hook is invoked whenever a window is destroyed. Message filter event (HK_CHECKMSGFILTER) The hook is invoked whenever WinGetMsg() or WinPeekMsg() is called. Input insertion (HK_MSGINPUT) The hook is used to insert mouse or keyboard messages similar to the journal playback hook. System lockup event (HK_LOCKUP) The hook is invoked whenever WinLockupSystem() is called. System shutdown event (HK_FLUSHBUF) The hook is invoked whenever the Ctrl-Alt-Del key sequence is pressed. The user message registration event is generated by a function that is no longer documented. The WinRegisterUserMessage() function existed in the 1.3 Toolkit documentation but does no longer. Two other hooks - HK_PLIST_ENTRY and HK_PLIST_EXIT - are also defined in pmwin.h but they do not exist within the system (as far as I know). Hook Contexts Some hooks can be defined as application-wide or system-wide; the difference is that an application-wide hook will be called whenever the event occurs within the application, while a system-wide hook will be called whenever the event occurs anywhere within the system. Because of this property of system-wide hooks, the corresponding hook procedure must reside within a DLL. This has other interesting connotations which we will see later. Some hooks must be application-wide, while others must be system-wide. Such hooks do not have a choice. Chaining Hooks In reality, a hook is nothing more than a function that accepts one or more arguments. The function is called by the system, meaning that the function must be exportable and use the _System calling convention. Additionally, the system must be made aware of the hook's existance; it is registered via the function WinSetHook(). Similarly, when the hook is to be removed, the function WinReleaseHook() is called. Figure 1) Before and after calling WinSetHook(). BOOL WinSetHook(HAB habAnchor, HMQ hmqQueue, LONG lHookType, PFN pfnHook, HMODULE hmModule); BOOL WinReleaseHook(HAB habAnchor, HMQ hmqQueue, LONG lHookType, PFN pfnHook, HMODULE hmModule); Both function take the following parameters: habAnchor Anchor block of the calling thread. hmqQueue Handle of the message queue to install the hook on. This can also be HMQ_CURRENT to specify the message queue of the calling thread, or NULLHANDLE if this is to be a system-wide queue. lHookType One of the HK_* constants (see the first section). pfnHook Pointer to the hook procedure. hmModule Handle to the DLL containing the hook procedure. This must be specified if hmqQueue is NULLHANDLE. Functions for the various hook types are chained together, which allows for multiple hook functions to be installed for a particular hook type. The WinSetHook() call installs the hook function at the head of the chain. Figure 2) Multiple hooks of the same type. The hook on top was installed last using WinSetHook(). This is important because some Win functions install hooks themselves, such as the WinCreateHelpInstance() function. Since the help hook installed by this function indicates to the system that no other hooks after it should be called, any help hooks you install before calling this function will never see any help events. Two Examples A Small Example Consider the application provided as hooks.zip. It is nothing more than a dialog box with two hooks attached - the associate window HDC hook, and the destroy window hook. Whenever either hook is invoked, they beep if the window provided is a frame window. BOOL EXPENTRY assocWindowHook(HAB habAnchor, HDC hdcContext, HWND hwndAssoc, BOOL bAssoc) //------------------------------------------------------------------------- // This hook is invoked whenever an HDC is associated or disassociated with // a window. // // Input: habAnchor - anchor block of the thread in whose context the // event occurred. // hdcContext - handle of the device context. // hwndAssoc - handle of the window associated/disassociated. // bAssoc - TRUE if hwndAssoc is associated with hdcContext. FALSE // otherwise. // Returns: TRUE if successful processing, FALSE otherwise. //------------------------------------------------------------------------- { CHAR achClass[256]; WinQueryClassName(hwndAssoc,sizeof(achClass),achClass); if ((WinFindAtom(WinQuerySystemAtomTable(), achClass)==LOUSHORT(WC_FRAME)) && bAssoc) { WinAlarm(HWND_DESKTOP,WA_NOTE); } /* endif */ return TRUE; } BOOL EXPENTRY destroyWindowHook(HAB habAnchor, HWND hwndDestroy, ULONG ulReserved) //------------------------------------------------------------------------- // This hook is invoked whenever a window is destroyed. // // Input: habAnchor - anchor block of the thread in whose context the // event occurred. // hwndDestroy - handle of the window being destroyed. // ulReserved - reserved. // Returns: TRUE if successful processing, FALSE otherwise. //------------------------------------------------------------------------- { CHAR achClass[256]; WinQueryClassName(hwndDestroy,sizeof(achClass),achClass); if (WinFindAtom(WinQuerySystemAtomTable(),achClass)==LOUSHORT(WC_FRAME)) { WinAlarm(HWND_DESKTOP,WA_ERROR); } /* endif */ return TRUE; } Figure 3) Two simple hook procedures. The hooks are installed, as we noted, using the WinSetHook() call and are released using the WinReleaseHook() call. WinSetHook(habAnchor, HMQ_CURRENT, HK_WINDOWDC, (PFN)assocWindowHook, NULLHANDLE); WinSetHook(habAnchor, HMQ_CURRENT, HK_DESTROYWINDOW, (PFN)destroyWindowHook, NULLHANDLE); : : WinReleaseHook(habAnchor, HMQ_CURRENT, HK_WINDOWDC, (PFN)assocWindowHook, NULLHANDLE); WinReleaseHook(habAnchor, HMQ_CURRENT, HK_DESTROYWINDOW, (PFN)destroyWindowHook, NULLHANDLE); Figure 4) WinSetHook() and WinReleaseHook() calls. Note that the hooks are local to the message queue for the thread. Also, note how the hook procedures are cast to the generic type PFN to avoid warnings/errors by the compiler. A Large Example Now, look at the application provided in life.zip. This is a screen saver which utilizes the input hook to determine when a period of inactivity elapses; actually, the word should be "expires" since the input hook is invoked when there is no inactivity. The strategy for the application is to start a timer using WinStartTimer() to count the number of seconds of inactivity. Whenever the input hook is invoked, it tells the application to reset this counter. Should the threshold be reached, the screen saver goes into effect. There are a couple of interesting points to be made: The hook is a system-wide hook. Since this means it can be invoked from within the context of any process, it must reside in a DLL. Since the hook and the application need to share data but the DLL needs to access it from within any process' context, the data must be declared in the DLL and a pointer to it is kept by the application. Additionally, the DLL has the attributes DATA SHARED SINGLE specified in the .DEF file to indicate that all processes share the same copy of the DLL's data segment. Summary Hooks provide a way to code certain types of logic into your application, which could not be done (easily) in other ways. While they are very useful, care must be taken because, in the case of system-wide hooks, what you do affects the entire system. For example, in a send message hook, you wouldn't use WinSendMsg() to notify your application, or else you would have an endless loop. For all development involving hooks, one must be sure that the design is completely worked out, or you could spend fruitless hours debugging your hook...and these are not easy beasts to debug, either. Probably the worst detriment during development is the lack of good documentation. Many of the hooks are scantily documented in pmwin.h at best, while others have incorrect parameters listed, making things even more difficult. If you have access to CompuServe, the best help you can get is from the IBMers that reside there, since they have been using many of these hooks since their first appearance.

출처: http://www.presenter5.com/OpenSourceBuild.htm

Open Source Build Instructions

HIGHLIGHTS

Firefox 1.5.0.2 (Required for Web Browser Widget)

URL

http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.2/source/

SIZE

34 MB

BUILD STEPS

Windows

VC6/ VC7

The Firefox-1.5.0.2 build on Windows platform requires the build of Mozilla source code. The build process involves the following steps:

1. Download Firefox-1.5.0.2 source code

Software	Download URL	File Name
Firefox-1.5.0.2	https://sourceforge.net/project/showfiles.php?group_id=152554&package_id=187307	firefox-1.5.0.2-source.tar.bz2

2. Unzip the Firefox-1.5.0.2-source.tar.bz2  to any drive on your machine.

           NOTE: In Firefox build we are considering the E:\ drive for building the source. You can build this source in any of the drives.

E:\cygwin\bin

Software Requirements

The following software needs to be installed for a standard Windows build.

• GNU Tools for Microsoft Windows (Cygwin)

Cygwin is a UNIX-like environment for Windows. Firefox uses a developer set of cygwin packages, which must be installed.

You can download the cygwin from the following link http://www.cygwin.com/

These include gawk, make and zip utilities.

Install these utilities into E:\cygwin\. Remember to choose Unix as "Default Text File Type". Besides the default modules, install the following modules.

• cvs

• cygutils

• make

• patch

• patchutils

• perl

• unzip

• zip

• libiconv

By default following modules should be installed.

• ash

• diffutils

• fileutils

• findutils

• gawk

• grep

• sed

• sh-utils

• textutils

Download the make.exe 3.80 version from the following link   http://developer.mozilla.org/en/docs/Windows_build_prerequisites_using_cygwin

Copy the downloaded make.exe in the E:\cygwin\bin

• Netscape wintools

Netscape's wintools.zip contains pre-built libraries and tools which are required to build Mozilla.

Download the Netscape's wintools.zip from the following link http://www.mozilla.org/build/win32-nmake.html

　

Extract the zip file into a temporary directory. Open a command prompt, and set the system variable MOZ_TOOLS to the directory where you have installed the MOZ tools. For example,

set MOZ_TOOLS=E:\mozilla\mozilla\moztools

The MOZ_TOOLS directory should neither be inside the cygwin installation directory nor in any of the sub-directories of  cygwin. If it is existed in any of the above mentioned locations, the build will be failed.

Run the wintools script. This batch script will install the files into %MOZ_TOOLS%/bin.

Finally, run the following commands.

cd moztools\buildtools\windows

install.bat

• Compiler and linker

Microsoft Visual Studio 6.0

Use MSVC command line tools, such as CL for C/C++ compiler.

To build the Firefox you need to install Visual Studio Service Pack 5 and Visual C++ Processor Pack(http://msdn2.microsoft.com/en-us/vstudio/aa718349.aspx)

Run the vcvars32.bat on the command prompt.

Configuring Environment

Creating mozconfig.txt

• Create a file, mozconfig.txt in E:\mozilla\.

• To build Firefox, put the following code in mozconfig.txt.

mk_add_options BUILD_OFFICIAL=1

mk_add_options MOZ_OFFICIAL=1

mk_add_options MOZ_CO_PROJECT=browser

mk_add_options MOZ_OBJDIR="@TOPSRCDIR@/../obj-win32"

ac_add_options --disable-debug

ac_add_options --enable-application=browser

ac_add_options --disable-tests

ac_add_options --disable-static

ac_add_options --disable-strip

ac_add_options --disable-accessibility

ac_add_options --disable-updater

• Create a file called mozset.bat in E:\mozilla\mozilla with the following code.

@echo off

set MOZ_TOOLS=E:\mozilla\mozilla\moztools
(Set to the place where you want Netscape's wintools.zip to install its binaries.)

set HOME=E:\mozilla

set PATH=%PATH%;E:\cygwin\bin;%MOZ_TOOLS%\bin
(Include both the Netscape wintools and the cygwin UNIX-like tools in your command search path.)

set LIB=%LIB%;%MOZ_TOOLS%\bin

set MOZCONFIG=E:\mozilla\mozilla\mozconfig.txt (Set path to mozconfig.txt)

• Run mozset.bat on the command prompt.

Now build the Firefox using the following command.

cd E:\Mozilla\mozilla
make -f client.mk build_all

GCC

 The Firefox-1.5.0.2 build on Windows GCC platform requires the build of Mozilla source code. The build involves the following steps:

1.  Download Firefox-1.5.0.2 source code

Software	Download URL	File Name
Firefox-1.5.0.2	https://sourceforge.net/project/showfiles.php?group_id=152554&package_id=187307	firefox-1.5.0.2-source.tar.bz2

Software Requirements

    The following software needs to be installed for a standard GCC build.

• Download the following packages from http://www.mingw.org/download.shtml

1. binutils-2.16.91-20060119-1.tar.gz

2. gcc-core-3.4.5-20060117-1.tar.gz

3. gcc-g++-3.4.5-20060117-1.tar.gz

4. mingw32-make-3.80.0-3.exe

5. mingw-runtime-3.9.tar.gz

6. w32api-3.6.tar.gz

Extract/Install all the above packages in the same folder, e.g. c:\mingw

NOTE: In Firefox build we are considering the c:\ drive for building the source. You can build this source in any of the drives.

• GNU Tools for Microsoft Windows (Cygwin)

Cygwin is a UNIX-like environment for Windows. A developer set of cygwin package is required to be installed to build Firefox.

Download the cygwin from the following link http://www.cygwin.com/

Install Cygwin into a folder, such as c:\cygwin. Remember to choose Unix as "Default Text File Type". Besides the default modules, install the following modules:

• cvs

• cygutils

• make

• patch

• patchutils

• perl

• unzip

• zip

• libiconv

To perform this, press the View button in the Select Packages part of the installer.

By default the following modules should be installed.

• ash

• diffutils

• fileutils

• findutils

• gawk

• grep

• sed

• sh-utils

• textutils

Download the make.exe 3.80 version from the following link  

http://developer.mozilla.org/en/docs/Windows_build_prerequisites_using_cygwin

Copy the downloaded make.exe in the c:\cygwin\bin

• Netscape wintools

Netscape's wintools.zip contains pre-built libraries and tools which are required to build Mozilla.

You can easily download the Netscape's wintools.zip from the following link

 http://ftp.mozilla.org/pub/mozilla.org/mozilla/source/wintools.zip

Create a folder moztools and put the wintools in it.

Untar mozilla source to any drive on your machine (say c: drive), name the source folder as Mozilla.

Configuring Environment

Creating mozconfig.txt

• Create a file called mozconfig.txt in $(HOME)\mozilla\. 

To build Firefox, put the following code in mozconfig.txt. 

CC=gcc CXX=g++ CPP=cpp AS=as LD=ld

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-opt

mk_add_options BUILD_OFFICIAL=1

mk_add_options MOZILLA_INTERNAL_API=1

mk_add_options MOZ_CO_PROJECT=browser

ac_add_options --enable-extensions

ac_add_options --disable-debug

ac_add_options --enable-application=browser

ac_add_options --enable-official-branding

ac_add_options --enable-canvas

ac_add_options --disable-tests

ac_add_options --disable-installer

ac_add_options --enable-svg

ac_add_options --enable-crypto

ac_add_options --enable-shared

ac_add_options --disable-static

ac_add_options --disable-strip

ac_add_options --disable-accessibility

ac_add_options --disable-activex

ac_add_options --disable-updater

ac_add_options --disable-activex-scripting

• Create a batch file called mozset.bat in $(HOME)\mozilla directory containing the following code.

set HOME=c:\mozilla

set MOZ_TOOLS=$(HOME)\mozilla\moztools

set path=c:\mingwbin;c:\cygwin\bin;%MOZ_TOOLS%\bin;%path%

set HOME=$(HOME)\mozilla

set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot

set MOZCONFIG=$(HOME)\mozilla\mozconfig.txt

Now perform the following steps.

1. Open command prompt and go the $(HOME)\mozilla directory

2. Run mozset.bat

3. Now compile the source using make –f client.mk build_all

4. After compilation gets completed, go to the $(HOME)\mozilla\obj-opt\dist\bin and type firefox to run the binary.

UNIX

To integrate Firefox browser with Presenter on Unix platform few lines in the file available at mozilla/widget/src/xlib/nsAppShell.cpp is required to be changed. This patch automatically changes the original code with the changed code.

To do the same, perform the following steps.

1. Click the link Mozilla changes for  Presenter integration to download the tar file.

2. Untar this file using the following command at the command prompt.

          tar -xvf mozilla_changes_script.tar

          When the respective file gets untarred a directory by the name of script is created in the current working directory.

3. Go to the respective directory and run the patch.csh script.

LINUX (Red Hat Linux 9.0)

1. Download Firefox-1.5.0.2 source code.

Software	Download URL	File Name
Firefox-1.5.0.2	https://sourceforge.net/project/showfiles.php?group_id=152554&package_id=187307	firefox-1.5.0.2-source.tar.bz2

2. Open a Linux Bash-shell and enter the following commands in a Bash-shell to extract the Firefox source code:

bunzip2 firefox-1.5.0.2-source.tar.bz2

tar  –xvf firefox-1.5.0.2-source.tar

This will create a directory named “mozilla”.

Software Requirements

The following softwares should be installed before starting the Firefox build.

• Compiler used gcc-3.3.2

• glibc 2.2 (only)

• Perl  version 5.8. (You can check the Perl version using the command Perl -v.)

• GTK2 not to be used.

• XFT not to be used.

• FreeType2 not to be used.

Links to download required software.

• Perl:           http://www.perl.com/download.csp

• Zip:            http://www.info-zip.org

Configuring Environment

1. Create the .mozconfig file in the mozilla directory with the following configuration options.

mk_add_options MOZ_PHOENIX=1

ac_add_options --disable-accessibility

ac_add_options --disable-calendar

ac_add_options --disable-composer

ac_add_options --disable-debug

ac_add_options --disable-installer

ac_add_options --disable-jsd

ac_add_options --disable-ldap

ac_add_options --disable-mailnews

ac_add_options --disable-tests

ac_add_options --enable-strip

ac_add_options --enable-strip-libs

ac_add_options --disable-shared

ac_add_options --enable-static

ac_add_options --enable-optimize="-O2 -march=i686 -finline-functions -fforce-addr -fno-strict-aliasing"

ac_add_options --enable-extensions="help,cookie,xml-rpc,xmlextras,p3p,pref,transformiix,universalchardet,typeaheadfind,webservices"

ac_add_options --enable-old-abi-compat-wrappers

ac_add_options --disable-toolkit-gtk2

ac_add_options --enable-default-toolkit=xlib

ac_add_options --disable-toolkit-gtk

ac_add_options --disable-toolkit-qt

ac_add_options --enable-toolkit-xlib

ac_add_options --disable-xft

ac_add_options --enable-mathml

ac_add_options --enable-xsl

ac_add_options --enable-crypto

ac_add_options --enable-ipv6

ac_add_options --without-system-nspr

ac_add_options --enable-nspr-autoconf

ac_add_options --enable-xterm-updates

ac_add_options --enable-elf-dynstr-gc

ac_add_options --disable-pedantic

ac_add_options --disable-freetype2

2. Set the following environment variables.

export MOZ_PHOENIX=1

export MOZILLA_OFFICIAL=1

export BUILD_OFFICIAL=1

3. Set the required path using the following command.

export PATH=/USR/X11R6/lib:$PATH

4. Ensure that gmake and zip commands are in the current path and start the Firefox build.

 Starting Firefox build

• Enter the following command in the “mozilla” directory to start the Firefox build.

gmake –f client.mk build

Checking Firefox build for successful completion

• Go to the directory mozilla/obj-opt/dist/bin and execute the following command.

./run-mozilla.sh ./firefox

SOLARIS

1. Download Firefox-1.5.0.2 source code

Software	Download URL	File Name
Firefox-1.5.0.2	https://sourceforge.net/project/showfiles.php?group_id=152554&package_id=187307	firefox-1.5.0.2-source.tar.bz2

2. Open a Solaris shell and enter the following commands in a C-shell to extract the Firefox source code.

bunzip2 firefox-1.5.0.2-source.tar.bz2

tar –xvf firefox-1.5.0.2-source.tar

This will create a directory named “mozilla”.

Software Requirements

The following software’s should be installed before starting the Firefox build:

• libIDL 0.6.8. If libIDL is installed at /usr/local/ directory, then one can check the libIDL version by using “libIDL-config –version” command. Otherwise, find the directory at which libIDL is installed, append it in the PATH environment variable.

• perl 5.0 or higher. (To determine the Perl version, use perl –v command.)

• GNU make 3.74 or higher, except 3.77. (To determine the GNU make version use, gmake –v command.)

• Zip 2.32. (It is a compression and file packaging utility.)

Links to download required softwares:

• libIDL:              ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/SRPMS/

• perl:                  http://www.perl.com/download.csp

• GNU make:      http://www.gnu.org/software/software.html

• Zip:                   http://www.info-zip.org

 To build libIDl 0.6.8

1. tar –xvf <libIDL-source>.tar

2. ./configure

3. vi Makefile and on line 126 comment as here

4. libIDL_la_LDFLAGS = #-version-info $(LT_CURRENT):$(LT_REVISION):$(LT_AGE)

5. -release $(LT_RELEASE)

6. make

7. Enter super user mode using “su” command and do “make install” to install the libIDL in appropriate directories.

 Set the required environment variables using the following commands.

1. setenv CFLAGS="-xlibmil"

2. setenv CXXFLAGS="-xlibmil -xlibmopt -features=tmplife -norunpath"

3. setenv ORIGIN

4. setenv LDFLAGS='-R$ORIGIN -R/usr/sfw/lib -R/opt/sfw/lib -R/usr/local/lib'

5. setenv MOZ_PHOENIX 1

6. setenv MOZ_XUL_APP 1

7. setenv MOZ_APP_NAME firefox

8. setenv CC cc

9. setenv CXX CC

10. setenv CCC CC

Configuring Environment

Create the .mozconfig file in the mozilla directory with the following configuration options:

mk_add_options MOZ_CO_PROJECT=browser

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-opt

mk_add_options MOZ_PHOENIX=1

ac_add_options --enable-optimize="-xO3"

ac_add_options --disable-ldap

ac_add_options --disable-mailnews

ac_add_options --enable-extensions="cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,p3p,gnomevfs"

ac_add_options --enable-crypto

ac_add_options --disable-composer

ac_add_options --disable-debug

ac_add_options --disable-tests

ac_add_options --disable-static

ac_add_options --enable-shared

ac_add_options --enable-single-profile

ac_add_options --disable-profilesharing

ac_add_options --with-xprint

ac_add_options --enable-xinerama

ac_add_options --enable-x11-shm

ac_add_options --enable-ctl

ac_add_options --enable-default-toolkit=xlib

ac_add_options --disable-freetype2

ac_add_options --disable-xft

#ac_add_options --without-system-nspr

ac_add_options --without-system-zlib

ac_add_options --without-system-jpeg

ac_add_options --without-system-png

ac_add_options --without-system-mng

ac_add_options --x-includes=/usr/openwin/include

ac_add_options --x-libraries=/usr/openwin/lib

mk_add_options BUILD_OFFICIAL=1

mk_add_options MOZILLA_OFFICIAL=1

Set the required paths using the following commands.

1. setenv PATH $PATH:/usr/local/bin:/opt/sfw/bin:/opt/SUNWspro/bin:/usr/bin::/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ccs/bin:/usr/ucb:/usr/sfw/bin

2. setenv LD_LIBRARY_PATH /usr/openwin/lib:/usr/local/lib:/usr/sfw/lib:/opt/sfw/lib

Ensure that gmake and zip commands are in the current path and start the Firefox build.

Starting Firefox build

1. Enter the following command in the “mozilla” directory to start the Firefox build.

gmake –f client.mk build_all

Checking Firefox build for successful completion

1. Go to the directory mozilla/obj-opt/dist/bin and execute the following command:

./run-mozilla.sh ./firefox

HPUX

1. Download Firefox-1.5.0.2 source code.

Software	Download URL	File Name
Firefox-1.0	http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.0/source/ Direct download link: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.0/source/firefox-1.0-source.tar.bz2	firefox-1.0-source.tar.bz2

2.  Untar the Firefox source code. It will create a “mozilla” directory.

Software Requirements

The following softwares should be installed before starting the Firefox build:

• libIDL 0.6.8. If libIDL is installed at /usr/local/ directory, then one can check the libIDL version by using “libIDL-config –version” command. Otherwise, find the directory at which libIDL is installed, append it in the PATH environment variable.

• perl 5.0 or higher.(To determine the Perl version, use perl –v command.)

• GNU make 3.74 or higher, except 3.77. (To determine the GNU make version use, gmake –v command.)

• Zip 2.32. (It is a compression and file packaging utility.)

Links to download required softwares.

• libIDL:             ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/SRPMS/

• perl:                 http://www.perl.com/download.csp

• GNU make:     http://www.gnu.org/software/software.html

• Zip:                  http://www.info-zip.org

Setting up the environment variable and compiler flag

Setting up the path for libIDL and HPUX native compiler aCC.

setenv PATH /opt/libIDL/bin:/usr/bin:/opt/aCC/bin:$PATH

Setting up the library path for libIDL:

setenv SHLIB_PATH /opt/libIDL/lib

setenv LIBIDL_CONFIG /opt/libIDL/bin/libIDL-config

Setting up the aCC compiler Flags:

setenv CC 'cc -Ae +DA1.1 +DS2.0'

setenv CXX 'aCC -ext +p +DA1.1 +DS2.0'

setenv CFLAGS '-DHPUX11 -Dhpux'

setenv CXXFLAGS '-DHPUX11 -Dhpux'

Code addition in Firefox

NSPR provides platform independence for non-GUI operating system facilities. These facilities include threads, thread synchronization, normal file and network I/O, interval timing and calendar time, basic memory management (malloc and free) and shared library linking.

In HPUX 11i, the system header file netdb.h does not define the addressinfo structure that provides hints about the type of socket the caller supports, which is used by the getaddrinfo function that provides protocol-independent translation from host name to address. To resolve this, we have created a header file called hpsock.h that defines addressinfo structure and the necessary macros needed by getaddrinfo function.

To update the Mozilla changes for HPUX in firefox source code please refer to the Unix section

Configuring Environment

Create the .mozconfig file in the mozilla directory with the following configuration options.

. $topsrcdir/browser/config/mozconfig

mk_add_options MOZ_PHOENIX=1

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-opt

ac_add_options --disable-auto-deps

mk_add_options MOZ_CO_PROJECT=browser

ac_add_options --enable-application=browser

 

ac_add_options --disable-accessibility

ac_add_options --disable-calendar

ac_add_options --disable-composer

ac_add_options --disable-debug

ac_add_options --disable-installer

ac_add_options --disable-jsd

ac_add_options --disable-ldap

ac_add_options --disable-mailnews

ac_add_options --disable-tests

ac_add_options --enable-strip

ac_add_options --enable-strip-libs

ac_add_options --enable-shared

ac_add_options --enable-extensions="help,cookie,xml-rpc,xmlextras,p3p,pref,transformiix,universalchardet,typeaheadfind,webservices"

ac_add_options --disable-toolkit-gtk2

ac_add_options --enable-default-toolkit=xlib

ac_add_options --disable-toolkit-gtk

ac_add_options --disable-toolkit-qt

ac_add_options --enable-toolkit-xlib

ac_add_options --disable-xft

ac_add_options --enable-mathml

ac_add_options --enable-xsl

ac_add_options --enable-crypto

ac_add_options --enable-xterm-updates

ac_add_options --disable-pedantic

ac_add_options --disable-freetype2

Starting Firefox Build

• Give the following command in the “mozilla” directory to start the Firefox build:

gmake –f client.mk build_all

Resolving Build Errors

You may come across thread related linking error “Unsatisfied symbols: pthread_join” in the module <xxx>/mozilla/toolkit/mozapps/update/src/updater. 
To resolve this error use the option “-lcma” during linking.

Checking Firefox build for successful completion

1. Go to the following directory. 

mozilla/obj-opt/dist/bin 

2. Execute the following command.

./run-mozilla.sh ./firefox

Integration with Presenter

For all Windows Platforms

    Copy all the files from obj-win32\dist\bin folder to 3rdparty\dll folder.

For all UNIX Platforms

    Copy all the files from dist/bin folder to 3rdparty/dll folder.

cd gsoap-2.7

./configure

7. Compile the gSoap sources

8. Change the directory to the soapcpp2 directory

9. Run the following commands

touch env.h

./src/soapcpp2 -penv env.h

CC -c envC.cpp

10. Copy libcrypto.so and libssl.so from the Presenter base kit to the soapcpp2 folder.

11. Compile and link the gSoap libraries using the following commands

cc -DWITH_NONAMESPACES -DWITH_OPENSSL -I/*path-to-openssl-include-folder– c stdsoap2.c 

cc -b -G -o libstdsoap2.so envC.o stdsoap2.o -L. -lcrypto -lssl

 *path-to-openssl-include-folder: Provide the path to Openssl/include folder here.

 Modification details for gSOAP Solaris Build

 soapcpp/src/soapcpp2_yacc.y

Modified Line no: 115

Original Code

%expect 1

Modified Code

/*%expect 1*/

HPUX

1. Download gSOAP 2.7.6e and OpenSSL sources from the following websites.

Software	Download URL	File Name
gSOAP	http://sourceforge.net/project/showfiles.php?group_id=52781&package_id=68161&release_id=394790	gsoap_2.7.6e.tar.gz
OpenSSL	http://www.openssl.org/source/	openssl-0.9.8e.tar.gz

2. Untar gSoap and openssl sources using the following commands.

gunzip gsoap_2.7.6e.tar.gz

tar –xvf gsoap_2.7.6e.tar

NOTE: This would create a directory named gsoap-2.7

gunzip openssl-0.9.8e.tar.gz

tar –xvf openssl-0.9.8e.tar

NOTE: This would create a directory named openssl-0.9.8e

3. Change the directory to the gSoap directory

cd gsoap-2.7

4. The following files need to be modified for the gSOAP build:

soapcpp/src/soapcpp2_yacc.y

soapcpp2/stdsoap2.cpp

soapcpp2/stdsoap2.h

     NOTE: For details, please refer to the Modifications details given below.

 ./configure

6. Compile the gSoap sources

7. Change the directory to the soapcpp2 directory.

8. Run the following commands

9. Copy libcrypto.so and libssl.so from the Presenter base kit to the soapcpp2 folder.

10. Compile and link the gSoap libraries using the following commands.

cc -z +Z -DWITH_NONAMESPACES -DWITH_OPENSSL -I/*path-to-openssl-include-folder -c stdsoap2.c

aCC -b -o libstdsoap2.sl envC.o stdsoap2.o -L. -lcrypto -lssl

 *path-to-openssl-include-folder: Provide the path to Openssl/include folder here.

 Modification Details for gSOAP HPUX Build

1.  soapcpp/src/soapcpp2_yacc.y

Modified Line no: 115

Original Code

%expect 1

Modified Code

/*%expect 1*/

2. soapcpp2/stdsoap2.cpp

Replace all instances of the following code in stdsoap2.cpp.

Original Code

__cplusplus

Modified Code

__cplusplus1

For example: Consider the following code.

Original Code

#ifdef __cplusplus

Modified Code

#ifdef __cplusplus1

3. soapcpp2/stdsoap2.h

1. Replace all instances of the following code in stdsoap2.h:

For example: Consider the following code.

Original Code

#ifdef __cplusplus

Modified Code

#ifdef __cplusplus1 

2. Modified Line no: 1714

Original Code:

SOAP_FMAC1 void SOAP_FMAC2 soap_fault(struct soap*);

Modified Code:

#ifdef __cplusplus

extern "C" {

#endif

SOAP_FMAC1 void SOAP_FMAC2 soap_fault(struct soap*);

3. Modified Line no: 1944

Original Code

SOAP_FMAC1 int SOAP_FMAC2 soap_recv_fault(struct soap*);

Modified Code

　

SOAP_FMAC1 int SOAP_FMAC2 soap_recv_fault(struct soap*);

#ifdef __cplusplus

}

#endif

gunzip xerces-c-src_2_7_0.tar.gz

tar –xvf  xerces-c-src_2_7_0.tar

NOTE: This would create a directory named xerces-c-src_2_7_0

                C compiler: CC