We have done so much above and all we have done is preparation.
As the saying goes, the sharpening of a knife is not mistaken for a firewood engineer. The knife is sharp and the knife is cut.
Let's get started with the real joke !!!!!!!!!!
Start, open the CMD window.
Configure SDK
Cd f: \ part _ OpenOffice \ OpenOffice. org3 \ basis \ SDK
Run setsdkenv_windows.bat for batch processing.
I will explain the working principle of this batch processing. When you run this batch processing, it will let you fill in some paths and then generate another setsdkenv_windows.bat file.
The file is located on XP and Windows 7 and looks different:
XP:C: \ Documents and Settings \ <username> \ Application Data \ % oo_sdk_name % \ setsdkenv_windows.bat-> For Windows2000/XP or later
Win7: C: \ Users \ <username> \ appdata \ roaming \ OpenOffice. org3.4 _ SDK \ setsdkenv_windows.bat
You must pay attention to it here.
The settings are shown below.
You must take a look at what the specific path corresponds to. I will not explain the specific content, it is relatively simple.
Press enter directly. If the operation is successful, the prompt appears.
Then, each time you start a command line, you must first run setsdkenv_windows.bat In the SDK,
In this case, setsdkenv_windows.bat checks whether setsdkenv_windows.bat in the C: \ Users \ <username> \ appdata \ roaming \ OpenOffice. org3.4 _ SDK path has a result.
If yes, run c: \ Users \ <username> \ appdata \ roaming \ OpenOffice. org3.4 _ SDK \ setsdkenv_windows.bat.
If it does not exist, You can reset the path.
Therefore, when you change any path required for configuration, You need to reconfigure it for the following reasons:
After you configure setsdkenv_windows.bat and execute setsdkenv_windows.bat again, setsdkenv_windows.bat sets the system path, which is only valid for the current command line window and is a temporary value, it does not change the system path. When you open a new command line window, the new window does not record the path, so you need to reset it.
Error Handling
Note that an error may occur when your system path contains a path of the "C: \ Program Files \ debugging tools for Windows (x86)" type.
Error cause: (x86) above the brackets,
Available in c: \ Users \ <username> \ appdata \ roaming \ OpenOffice. org3.4 _ SDK \ setsdkenv_windows.bat
Rem set path appropriate to the output directory
If defined oo_sdk_out (
Set Path = % oo_sdk_out % \ winexample. Out \ bin; % PATH %
) Else (
Set Path = % oo_sdk_home % \ winexample. Out \ bin; % PATH %
)
Path contains the parentheses (x86) and conflicts with), and I don't know how to solve them. Fortunately, my win7
32. Then I set C: \ Program Files \ debugging tools for Windows (x86)
C: \ Program Files \ debugging tools for Windows, and change the system path to c: \ Program.
Files \ debugging tools for Windows, OK.
On the 32-bit Windows 7 7 server, I am delayed for a lot of time due to this error.
Well, here is the real configuration of the SDK.
Finished. Rest ....