/trunk/install/launcher/izpack-launcher-1.3_windows/doc/en/howto.html - Annotate - | gvSIG desktop 1 - gvSIG

8474

jmvivo

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">

2

<html xmlns="http://www.w3.org/1999/xhtml">

3

<head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

  <meta name="Generator" content="KWord HTML Export Filter Version 1.40.2.1 " />

  <meta name="Author" content="Marc Eppelmann" />

  <title>howto.html</title>

67

  <style type="text/css">

68

/* KWORD_CSS_EXPORT = 1.15.2.6 */

69

BODY

70

71

  background-color: #FFFFFF

72

73

.Standard

74

75

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-transform: none; font-variant:normal;

76

77

.Document_Title

78

79

  text-align:center; text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: bold; font-size: 24pt; text-decoration: none; text-transform: none; font-variant:normal;

80

81

.Head_1

82

83

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: bold; font-size: 20pt; text-decoration: none; text-transform: none; font-variant:normal;

84

85

.Head_2

86

87

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: bold; font-size: 16pt; text-decoration: none; text-transform: none; font-variant:normal;

88

89

.Head_3

90

91

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: bold; font-size: 12pt; text-decoration: none; text-transform: none; font-variant:normal;

92

93

.Enumerated_List

94

95

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-transform: none; font-variant:normal;

96

97

.Alphabetical_List

98

99

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-transform: none; font-variant:normal;

100

101

.Bullet_List

102

103

  text-indent:0pt; line-height:normal; text-shadow:none; font-family: helvetica; font-style: normal; font-weight: normal; font-size: 12pt; text-decoration: none; text-transform: none; font-variant:normal;

104

105

@page

106

107

  size: 21.0cm 29.7cm;

108

  margin-top: 42pt;

109

  margin-left: 28pt;

110

  margin-bottom: 42pt;

111

  margin-right: 28pt;

112

113

  </style>

114

</head>

115

116

117

<body>

<h1>Izpack-Launcher&nbsp;</h1>

<p class="Standard" style="text-align: left;"></p>

<h2><span class="Head_2">HowTo

145

Compile an Executable for the Win32 Platform.</span></h2>

<p class="Standard" style="text-align: left;">This document endeavors

153

to describe how to compile a&nbsp;Windows executable version of the

154

Izpack launcher using&nbsp;open source tools and Windows as a build

155

environment.</p>

156

157

158

<p class="Standard" style="text-align: left;"><br />

</p>

<h3><span class="Head_3">Table of Content </span></h3>

<p class="Standard" style="text-align: left;">

183

184

185

<br />

1. Introduction <br />

196

197

198

2. Startup <br />

3. Prerequisites <br />

4. Getting Sources <br />

5. Installation<br />

6.&nbsp;Preparation<br />

7. Perform complete compilation of the Izpack-Launcher - Distribution<br />

8. Test<span class="Head_3"><br />

<span class="Standard">9. Customization</span></span><br />

10. Shutdown <br />

<br />

<br />

</p>

<h3><span class="Head_3">1. Introduction</span></h3>

<p class="Standard" style="text-align: left;">Izpack-launcher is a

321

native Executable, that searches for, installs if not found and starts

322

a Java Runtime Environment (JRE) together with a customers "IzPack Java

323

- setup.jar".

324

If Java is already&nbsp;installed then it&nbsp;just starts the setup.jar.&nbsp;</p>

325

326

327

<p class="Standard" style="text-align: left;">IzPack-launcher can be

328

compiled and run on a number of OSs. But it will be of most

329

benefit&nbsp;to Windows users, who lack the ability of being able to

330

effectively accomplish the above task using good old unix scripting

331

tools.</p>

332

333

334

<p class="Standard" style="text-align: left;">Building of a self-extracting version is also possible. This uses a technique which is nicely illustrated by

335

Julien in a separate <a href="http://www.izforge.com/izpack/7zip-sfx-tutorial/demo.html">flash</a> "screen-cam" demonstration or alternatively a <a href="http://www.izforge.com/izpack/7zip-sfx-tutorial/izpack-win32-sfx-tutorial.pdf">pdf</a>.</p>

336

337

338

<p class="Standard" style="text-align: left;">For more information on

339

how

340

to use, embed and build a IzPack Setup with the IzPack-Launcher,

341

read&nbsp;the manuals which come with IzPack and&nbsp;IzPack Launcher.

342

A <a href="http://www.izforge.com/izpack/izpack-tutorial.pdf">quickstart tutorial</a>&nbsp;pdf is also provided and is recommended for beginners. There is another "howto compile" in the <a href="http://openfacts.berlios.de/index-en.phtml?title=IzPack/Launcher">WIKI</a>, which describes the compile and build based on&nbsp;MSVC++6.0 and Open Watcom.</p>

<p class="Standard" style="text-align: left;">Finally, Imho: IzPack-Launcher is not the name that describes this Executable exactly.

356

JRE_FindAndStartWithAny(Gui)Jar.exe would be a more precise name. ;-)</p>

357

358

359

<h3><span class="Head_3">2.

360

Startup</span>&nbsp;</h3>

<p class="Standard" style="text-align: left;">IzPack&nbsp;launcher is build

374

and based on WxWindows/wxWidgets, a native and platform independent

375

GUI-Development

376

library similar to Qt and Gtk. But it has more liberal licensing terms then Qt (even for

377

win32 binaries as of the current Qt4 release). That is why you will need (in addition to a

378

C++ Compiler) the WxWindow/wxWidgets distribution. I will describe how to

379

get and

380

prebuild this GUI-library in the Prerequisites and the Preparation Section.</p>

<p class="Standard" style="text-align: left;">To use IzPack-Launcher,

394

you&nbsp;will also need your application as an&nbsp;"IzPack-Setup

395

Jar-File" executable jar. For the impatient you can use the IzPack's

396

Setup-Jar&nbsp;from <a href="http://www.izforge.com/izpack">http://www.izforge.com/izpack</a>, for testing purposes.</p>

397

398

399

<h3 class="Head_3">3.

400

Prerequisites&nbsp;</h3>

<p class="Standard" style="text-align: left;">To start with, you need a

414

C++&nbsp;Compiler. The easiest way is to download and install <a href="http://www.bloodshed.net">DevCPP</a> from

415

http://www.bloodshed.net. This is a complete IDE and comes with all tools needed to compile

416

wxWindows/wxWidgets and IzPack-launcher.&nbsp;</p>

417

418

419

<p class="Standard" style="text-align: left;">The current release of DevCPP

420

is 4.9.9.2 (as of 19th August 2005). Unfortunately the&nbsp;make utility of this suite has a

421

bug, so you have to do 3 very simple edit/copy steps manually. I will describe this in

422

the preparation chapter. Note: if this bug gets fixed in a future

423

release, you might be lucky and not have to fix it yourself!</p>

<p class="Standard" style="text-align: left;">After installation, you have to add the <span style="font-family: monospace;">"bin</span>" - folder of DevCPP to your PATH-Environment variable. i.e. <span style="font-family: monospace;">set PATH=%PATH%;C:\devcpp\bin</span></p>

<h3><span class="Head_3"> 4. Getting

442

Sources</span>&nbsp;</h3>

<p class="Standard" style="text-align: left;">The next thing you have to do is build IzPack-launcher, so checkout the sources from the

456

svn-tree, if you don't have the sources already.&nbsp;<br />

457

458

459

As registered IzPack developer, you can checkout using: <br />

<tt>svn checkout&nbsp;svn+ssh://<i>developername</i>@svn.berlios.de/svnroot/repos/izpack/izpack-launcher/trunk</tt>

473

<br />

while as anonymous user you have to use:<br />

<tt>svn checkout svn://svn.berlios.de/izpack/izpack-launcher/trunk</tt></p>

<p class="Standard" style="text-align: left;"><tt><span class="Standard">Then, you have to download the wxWindows</span><span class="Standard">/</span></tt>wxWidgets<tt><span class="Standard"> sources for your target platform.</span><span class="Standard"> As this is all about Windows - go</span><span class="Standard"> download the old version 2.4.2 (otherwise you will be faced with more build bugs) <a href="http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip">wxMSW-2.4.2-setup.zip</a>

505

from http://www.sourceforge.net . </span></tt>Yes, this is maybe a todo for us - at least we have to adapt the makefiles.<br />

</p>

<h3 class="Head_3">5. Installation</h3>

<p class="Standard" style="text-align: left;">Once you have done your downloading, you are ready to install. I have setup DevCPP

545

with the default options and the default install path: c:\dev-cpp.

546

wxWindows was also installed typically, except I choosed another

547

install path: c:\wxw242.</p>

<h3 class="Head_3">6. Preparation&nbsp;</h3>

<p class="Standard" style="text-align: left;">You can read the

574

documentation on how to build the wxWindows library, or alternatively follow the required steps below to compile with DevCpp.</p>

<p class="Standard" style="text-align: left;">A) In order to compile

588

the wxWindows/wxWidget Libraries, you have to set some environment

589

variables. You can set these globally with Settings --&gt; Control

590

panel -&gt; System -&gt;Advanced -&gt; Environment Variables or only in

591

the current Console:</p>

<p class="Standard" style="text-align: left;">i) Adjust the environment

605

variable WXWIN to your wxWindows/wxWidgets&nbsp;installation-

606

&nbsp;base path: <br />

</p>

<pre class="Standard" style="font-family: monospace;">&nbsp;&nbsp;&gt;&nbsp;set WXWIN=C:\wxw242</pre>

<p class="Standard" style="text-align: left;">ii) Don't forget to add the "bin"

646

subdirectory of DevCPP to your PATH environment variable:<br />

</p>

<pre style="font-family: monospace;">&nbsp;&nbsp;&nbsp;<span style="font-family: monospace;" class="Standard">&gt; set PATH=%PATH%;C:\dev-cpp\bin</span></pre>

<p class="Standard" style="text-align: left;"></p>

<p class="Standard" style="text-align: left;">iii) Now open a new&nbsp;console (cmd.exe), change to the wxWindows&nbsp;basedir typing:<br />

<br />

<span style="font-family: monospace;">

&gt; cd /d C:\wxw242\src\msw&nbsp;</span></p>

<p class="Standard" style="text-align: left;">iv) and enter:<br />

<br />

<span style="font-family: monospace;">

&gt;&nbsp;&nbsp;</span><span style="font-weight: bold;"><span style="font-family: monospace;">make -f makefile.g95 clean</span><br />

</span><br />

&nbsp;to cleanup&nbsp;previous&nbsp;created binaries. This is not required, for the first time.<br />

</p>

<p class="Standard" style="text-align: left;">v) now enter:<br />

<br />

<span style="font-family: monospace;">

&gt; </span><span style="font-weight: bold; font-family: monospace;">make -f</span><span style="font-family: monospace;"> </span><span style="font-weight: bold; font-family: monospace;">makefile.g95 FINAL=1</span></p>

<p class="Standard" style="text-align: left;">NOTE: Unfortunately,

850

there is a tiny bug in the make tool or copy-tool (as I sayed above). (The

851

destination option is not recognized correctly),&nbsp;<br />

So you will get a Error message like:</p>

<p class="Standard" style="text-align: left; font-family: monospace;">mkdir ..\..\lib\msw<br />

mkdir ..\..\lib\msw\wx<br />

cp ../../include/wx/msw/setup.h ../../lib/msw/wx/setup.h<br />

<span style="font-weight: bold;">process_begin: CreateProcess((null), cp ../../include/wx/msw/setup.h ../../lib/m</span><br style="font-weight: bold;" />

<span style="font-weight: bold;">sw/wx/setup.h, ...) failed.</span><br />

make (e=2): The system cannot find the file specified.<br />

make: *** [../../lib/msw/wx/setup.h] Error 2</p>

<p class="Standard" style="text-align: left;"><span class="Standard">or:</span><br />

</p>

<pre style="font-weight: bold; font-family: monospace;">cp ../common/dosyacc.c ../common/y_tab.c</pre>

<pre style="font-family: monospace;">process_begin: CreateProcess((null), cp ../common/dosyacc.c ../common/y_tab.c, .</pre>

<pre style="font-family: monospace;">..) failed.</pre>

<pre style="font-family: monospace;">make (e=2): The system cannot find the file specified.</pre>

<pre style="font-family: monospace;">make: *** [../../src/common/y_tab.c] Error 2</pre>

<p class="Standard" style="text-align: left;"><br />

However there is a simple Workaround by doing the three following easy things ;-) :&nbsp;</p>

<p class="Standard" style="text-align: left;">Just copy the file manually: Enter in the case above: <span style="font-style: italic;"><br />

Note: Use backslash instead of slash.</span></p>

<pre><pre style="font-family: monospace;">&gt; <span style="font-weight: bold;">copy ..\..\include\wx\msw\setup.h ..\..\lib\msw\wx\setup.h</span></pre><span class="Standard">comment out line 546: ( $(COPY) $(WXDIR)/include/wx/msw/setup.h $(subst $(BACKSLASH),/,$@) ) in the</span><span style="font-weight: bold;">&nbsp;</span><span class="Standard">makefile.g95</span> <span class="Standard">and continue the build, by reenter</span>  <span style="font-weight: bold;"></span></pre>

<pre><span style="font-weight: bold;">&gt; make -f</span> <span style="font-weight: bold;">makefile.g95 FINAL=1</span><br /><br />&gt; <span style="font-weight: bold;">copy&nbsp;..</span>\<span style="font-weight: bold;">common</span>\<span style="font-weight: bold;">dosyacc.c ..</span>\<span style="font-weight: bold;">common</span>\<span style="font-weight: bold;">y_tab.c</span><br /><br /><span class="Standard">and continue the build, by enter </span> <span style="font-weight: bold;"><br /><br />&gt; make -f</span> <span style="font-weight: bold;">makefile.g95 FINAL=1</span><br /><span style="font-style: italic;"></span><br /><span style="font-weight: bold;">&gt; copy ..\common\doslex.c ..\common\lex_yy.c<br /><br /></span><span class="Standard">again and </span><span class="Standard" style="font-weight: bold;">finish</span><span class="Standard"> the wxWin-build, by (last) re-enter </span> <span style="font-weight: bold;"><br /></span><span style="font-weight: bold;"><br />&gt; make -f</span> <span style="font-weight: bold;">makefile.g95 FINAL=1</span><br /><br /></pre>

<p class="Standard">The wxwindows libs and all other wxw stuff should now compiled successfully. </p>

<p class="Standard">OK. You are now able to compile the IzPack-Launcher Exe.</p>

<pre><span style="font-weight: bold;"></span></pre>

<h3 class="Head_3">7. Perform complete compilation of the IzPack-Launcher - Distribution</h3>

<p class="Standard" style="text-align: left;">( First ensure, that the

1123

WXWIN-Environment variable is set. Otherwise you get an error like if

1124

you calls the make&nbsp;tool direct in the console.: &nbsp;</p>

<p class="Standard" style="text-align: left; font-family: monospace;">Makefile.mingw:10: /src/makeprog.g95: No such file or directory<br />

make: *** No rule to make target `/src/makeprog.g95'.&nbsp; Stop.)</p>

<p class="Standard" style="text-align: left;">Otherwise if you use the new provided <span style="font-weight: bold;">compile.bat</span> (recommended) you gets an error&nbsp;message, that WXWIN is not defined yet.</p>

1150

<p class="Standard" style="text-align: left;">If all is set up correctly, you can simply compile by start&nbsp;compile.bat file.</p>

<pre class="Standard">C:\izpacklauncher&gt;<span style="font-weight: bold; font-family: monospace;">compile.bat<br /></span></pre>

1158

<p class="Standard" style="text-align: left;">Alternatively you can compile by hand using the following command:</p>

C:\izpacklauncher&gt;<span style="font-weight: bold; font-family: monospace;">make -f Makefile.mingw install</span>

<p class="Standard" style="text-align: left;">Here is just the output:<br />

<br />

<span style="font-family: monospace;" class="Standard">C:\home\marc\izpack-launcher\trunk\src&gt;compile.bat<br />

1202

g++&nbsp; -Wl,--subsystem,windows -mwindows -LC:\wxw242/lib -LC:\wxw242/contrib/lib<br />

1203

&nbsp;-o launcher.exe launcher.o failuredialog.o launcher_resources.o&nbsp; C:\wxw242/lib/<br />

1204

libwxmsw.a -lregex -lpng -ljpeg -lzlib -ltiff -lstdc++ -lgcc -lodbc32 -lwsock32<br />

1205

-lwinspool -lwinmm -lshell32 -lcomctl32 -lctl3d32 -lodbc32 -ladvapi32 -lodbc32 -<br />

1206

lwsock32 -lopengl32 -lglu32 -lole32 -loleaut32 -luuid<br />

1207

if not exist ..\dist\fr mkdir ..\dist\fr<br />

1208

if not exist ..\dist\de mkdir ..\dist\de<br />

1209

if not exist ..\dist\da mkdir ..\dist\da<br />

1210

if not exist ..\dist\pt-BR mkdir ..\dist\pt-BR<br />

1211

if not exist ..\dist\es mkdir ..\dist\es<br />

1212

if not exist ..\dist\it mkdir ..\dist\it<br />

1213

if not exist ..\dist\nl mkdir ..\dist\nl<br />

1214

copy fr\launcher.mo ..\dist\fr<br />

1215

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1216

copy es\launcher.mo ..\dist\es<br />

1217

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1218

copy de\launcher.mo ..\dist\de<br />

1219

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1220

copy da\launcher.mo ..\dist\da<br />

1221

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1222

copy pt-BR\launcher.mo ..\dist\pt-BR<br />

1223

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1224

copy it\launcher.mo ..\dist\it<br />

1225

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1226

copy nl\launcher.mo ..\dist\nl<br />

1227

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1228

copy launcher.exe ..\dist\launcher-Win32.exe<br />

1229

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.<br />

1230

strip ../dist/launcher-Win32.exe<br />

1231

copy launcher.exe.manifest ..\dist\launcher-Win32.exe.manifest<br />

1232

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 file(s) copied.</span><span style="font-family: monospace;" class="Standard"></span></p>

<p class="Standard" style="text-align: left;">Congratulation! You have now a IzPack launcher.exe in the current folder!</p>

<h3><span class="Head_3">8. Test</span></h3>

<p class="Standard" style="text-align: left;">You can test it by enter:<span style="font-family: monospace;"> "launcher"</span> to test the developer version.</p>

<p class="Standard" style="text-align: left;">You will get one of the following screen shots depend on the content of the <span style="font-family: monospace;">launcher.ini</span> in the current folder.</p>

<p class="Standard" style="text-align: left;">If the file&nbsp;launcher.ini contains a valid <span style="font-family: monospace;">"Jar = YourInstall.jar" </span>- line, you will get:<br />

</p>

<p class="Standard" style="text-align: left;"><img style="width: 511px; height: 219px;" alt="default" src="001.png" /></p>

<p class="Standard" style="text-align: left;">Otherwise:&nbsp;</p>

<p class="Standard" style="text-align: left;"><img style="width: 671px; height: 380px;" alt="wrong ini" src="002.png" /></p>

<p class="Standard" style="text-align: left;">Alternatively you can enter <span style="font-family: monospace;">..\dist\launcher-Win32.exe</span> to test the distribution version.</p>

<p class="Standard" style="text-align: left;">The result should be similar to the developer version:<br />

<img style="width: 672px; height: 430px;" alt="dist" src="003.png" /></p>

<p class="Standard" style="text-align: left;">But the file size of this executable is about 1MB smaller than the developers one. At least on my machine ;-)</p>

<h3><span class="Head_3">9. Customization</span> <br />

</h3>

<p><span class="Standard" style="font-family: helvetica;">If you want to test the other languages you have to change your locale in the </span><span class="Standard">regional options dialog launched from the control panel. For example for&nbsp;german</span>:</p>

<br />

<img style="width: 1078px; height: 572px;" alt="change lang" src="004.png" /><br />

<br />

<h3 class="Head_3">10. Shutdown</h3>

<br />

<p class="Standard">Now, that's all folks.</p>

<span style="font-family: helvetica;">

1415

<p class="Standard" style="text-align: left;">Thanks to Julien Ponge,

1416

all&nbsp;developers, members and even the users of IzPack. Thanks goes

1417

also still to VMware, which made this doc possible, since I work with

1418

Linux and run any Win32-OS only in a VMware-sandbox. ;-)</p>

1419

<p class="Standard" style="text-align: left;">Not least thanks to Nick Cunnah for review this doc.</p>

<p class="Standard" style="text-align: left;">This document was initially written at

1433

2005-05-19 by Marc Eppelmann / Oldenburg(Oldb) / Germany</p>

<p class="Standard" style="text-align: left;">This comes without any

1452

warranty. Suggestions and Feedback are always welcome. Send&nbsp;these to <a href="mailto:marc.eppelmann&amp;#064;gmx.de">marc.eppelmann_at_gmx.de</a></p>

<p class="Standard" style="text-align: left;"><span class="Standard">&nbsp;</span><br class="Standard" />

<span class="Standard">

1478

The License is the same as for the entire software. See LICENSE, which comes with the distribution.</span><br />

</p>

<p class="Standard" style="text-align: left;">$Id$<br />

</p>

</span>

1524

</body>

1525

</html>

| gvSIG desktop 1

root / trunk / install / launcher / izpack-launcher-1.3_windows / doc / en / howto.html @ 11445