Deploying Your Application/ja: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1		-	~~## Contents~~
2		-
3		-	* 1 Windows のインストーラ
4		-	* 1.1 Inno Setup
5		-	* 1.2 InstallJammer
6		-	* 1.3 HJ-Install
7		-	* 1.4 LizaJet Installer
8		-	* 1.5 NSIS (Nullsoft Scriptable Install System)
9		-	* 1.6 Windows Installer XML (WiX) toolset
10		-	* 2 Unix のインストーラー
11		-	* 2.1 Linux 上で RPM パッケージを作る
12		-	* 2.1.1 構築環境を設定する
13		-	* 2.1.2 バイナリパッケージを作る
14		-	* 2.1.3 ソースとバイナリのパッケージを作る
15		-	* 2.2 Linux 上で Debian のパッケージを作る
16		-	* 2.3 GUInseng
17		-	* 2.4 The Zero Install system
18		-	* 2.4.1 Anyone can install software
19		-	* 2.4.2 Anyone can distribute software
20		-	* 2.4.3 It doesn't matter whether software is installed or not
21		-	* 2.4.4 Security
22		-	* 3 Creating a Makefile for your Lazarus software
23		-	* 4 macOS のインストーラー
24		-	* 4.1 macOS のパッケージメーカー（PackageMaker）を使う
25		-	* 4.2 macOS に X11 と GTK をインストールする
26		-
27	1		## Windows のインストーラ
28	2
29	3		Window にはフリーでオープンソースなインストーラーが多く作成されているため、これらの利用をお勧めします。
30	4
31	5		### Inno Setup
32	6
33	7		[Inno Setup](<http://www.jrsoftware.org/isinfo.php>) は Windows 用のフリーでオープンソースなインストーラーであり、商用にも自由に利用できます。 (ソースは Borland Delphi 2.0-5.0 用となっています。)
34	8
35	9		現在利用されている全てバージョンの Windows -- Vista, XP, 2008, 2003, 2000, Me, 98, 95, and NT 4.0. (サービスパックは不要) -- をサポートしており、ファイルのバージョン情報の比較、使用中のファイルの置き換え、レジストリと .ini ファイルへのエントリ作成など、多くの機能があります。[[1]](<http://www.jrsoftware.org/isinfo.php#features>)
36	10
37	11		パブリックドメインではありませんので、配布や利用には制約があります。詳細は、[ライセンス](<http://www.jrsoftware.org/files/is/license.txt>) を確認してください。
38	12
39	13		Inno Setup は、 Windows 用の Lazarus インストーラーにも利用されています。
40	14
41	15		### InstallJammer
42	16
43	17		[InstallJammer](<http://www.installjammer.com/>) は、マルチプラットフォームなオープンソースの GUI インストーラーです。完全なクロスプラットフォームとなるようにデザインされており、Windows、UNIX の多くのバリエーションのほぼ全て、Mac OS X で利用できます。
44	18
45	19		### HJ-Install
46	20
47	21		HJ-Install は、Windows 95, 98, ME, NT 4.0, 2000, 2003, XP, Vista 用のフリーウェアのインストーラーです。インターネット上やCD-Rom、1枚または複数枚のフロッピーディスクで配布されることを考慮して作られています。しかし、ネットワークからもスタンドアローンのスクリプトエンジンとして利用できます。インストーラーと他ファイルの合計で138kbと軽いサイズです。レジストリと ini ファイルの変更、アンインストールはサポートしていません。詳細は、[ウェブサイト](<http://www.freebyte.com/hjinstall/>) を確認してください。
48	22
49	23		### LizaJet Installer
50	24
51	25		LizaJet Installer は商用のインストーラーですがフリー版もあります。 Object Pascal をスクリプトに用いています。詳細は、 [ウェブサイト](<http://www.lizajet.com>) を確認してください。（訳注：09時点でウェブサイトは404エラーですが、インストーラ名で検索すると数多くヒットします。）
52	26
53	27		### NSIS (Nullsoft Scriptable Install System)
54	28
55	29		NSIS はプロ向けのオープンソースなシステムであり、 Windows 用のインストーラーを生成できます。 NSIS インストーラーは34kbの大きさです。詳細は、[ウェブサイト](<http://nsis.sourceforge.net/Main_Page>) または、 [エディター](<http://hmne.sourceforge.net/>) を確認してください。
56	30
57	31		### Windows Installer XML (WiX) toolset
58	32
59	33		XML ファイルから Windows用インストールパッケージを作成します。開発者がビルドプロセスをMSIやMSMといったセットアップパッケージに統合できるように、コマンドライン環境もサポートしています。詳細は、[ウェブサイト](<http://wix.sourceforge.net/>) を確認してください。
60	34
61	35		## Unix のインストーラー
62	36
63	37		### Linux 上で RPM パッケージを作る
64	38
65	39		On Linux, the best way to deploy applications is by using the native package system. Of the many package systems available, RPM (RedHat Package Manager) is the most commonly utilized format, and is defined as the standard one in the Linux Standard Base.
66	40
67	41		To create a RPM file, you need to create a spec text file will the information necessary to build the software, and also an environment to build that spec. The best editor to create RPM packages is Emacs, because it recognizes the spec extension, highlights the text appropriately and even has a menu option to build rpm packages.
68	42
69	43		To build the rpm file use either the emacs menu or this command line (man rpmbuild for more information):
70	44		```
71	45		rpmbuild -ba --clean $HOME/RPM/SPECS/myprogram.spec
72	46		```
73	47
74	48		#### 構築環境を設定する
75	49
76	50		RPM Packages are installed as root to the base system (/ directory), but an accident as root can destroy your machine. To avoid this, packages can be build as a normal use. The build process includes a real install, to make sure the package works, but this install is made to a fake root directory represented by the $RPM_BUILD_ROOT variable.
77	51
78	52		First, go to your home directory (or another directory inside it) and create the following directory structure:
79	53
80	54		RPM
81	55
82	56		RPM/BUILD - This directory is utilized by RPM to build the package.
83	57
84	58		RPM/RPMS - Here you can find binary RPMs after you build them.
85	59
86	60		RPM/SOURCES - Place your compressed tar files and patches here.
87	61
88	62		RPM/SPECS - Place all your spec files here.
89	63
90	64		RPM/SRPMS - Here you can find source RPMs after you build them.
91	65
92	66		Next you will need to create a configuration file to tell rpm builder software where he can find your build directories. Go to your home directory and create a file named .rpmmacros and place the text bellow on it. Make sure to change the directories to the correct ones on your system.
93	67		```
94	68		%_topdir /home/felipe/RPM/
95	69		%_tmppath /home/felipe/tmp
96	70
97	71		%_signature gpg
98	72		%_gpg_name Mandrakelinux
99	73		%_gpg_path ~/.gnupg
100	74		```
101	75
102	76		#### バイナリパッケージを作る
103	77
104	78		The easiest way to create a RPM package is to make it install already compiled software. There are some reason why we might want to avoid compiling the software in the spec file:
105	79
106	80		* It requires creating a Makefile and makefiles are complex
107	81
108	82		* Some packages don't have any binary software in them, so they don't need to be built.
109	83
110	84		Each RPM Package contains a single compressed tar archive. Place the archive under the RPM/SOURCES directory. Zip, gz and bz2 compressions should work ok. The file can either contain the full source of the project if you with to create a source and a binary package or a directory with the files already in place, like if they were installed in the user machine, if you with to create a binary only package.
111	85
112	86		To build a binary package open a spec file with Emacs text editor. On Emacs open the menu "RPM spec" --> "RPM Build" --> "Build Binary Package". This will create a .rpm file under the directory RPM/RPMS
113	87
114	88		Bellow is a spec file that doesn't build the software. In this case the software is a Braille Course composed of html and Macromedia Flash files. Flash files cannot be build on Linux, so it's not possible to create a source package in this case.
115	89		```
116	90		%define name braillevirtual
117	91		%define version 1.0
118	92		%define release mdk
119	93		%define dir braillevirtual
120	94		%define root /home/felipe/tmp/ROOT/
121	95
122	96		Summary: Curso On-Line de Braille
123	97		Name: %{name}
124	98		Version: %{version}
125	99		Release: %{release}
126	100		Vendor: Laboratório de Brinquedos da Faculdade de Educação da USP
127	101		URL: www.braillevirtual.fe.usp.br
128	102		License: Distribuível livremente
129	103		Group: Books/Other
130	104		Packager: Felipe Monteiro de Carvalho
131	105		Source0: home/felipe/Programacao/SOURCES/braillevirtual.tar.bz2
132	106		BuildRoot: %{root}
133	107
134	108		%description
135	109		O Braille Virtual é um curso on-line público e gratuito destinado à difusão e ensino do sistema Braille de leitura e escrita para cegos a pessoas que vêem. É orientado especialmente a pais, crianças, professores e funcionários de escolas inclusivas e pretende facilitar a comunicação entre estas pessoas e as pessoas com cegueira.
136	110
137	111		%prep
138	112		cd $RPM_SOURCE_DIR
139	113		cp braillevirtual.tar.bz2 $RPM_BUILD_DIR
140	114		cd $RPM_BUILD_DIR
141	115		rm -rf %{dir}
142	116		rm -f braillevirtual.tar
143	117		bunzip2 -d braillevirtual.tar.bz2
144	118		tar -xvf braillevirtual.tar
145	119
146	120		%install
147	121		rm -rf $RPM_BUILD_ROOT/usr/share/%{dir}
148	122		cp -r $RPM_BUILD_DIR/%{dir} $RPM_BUILD_ROOT/usr/share/
149	123
150	124		%clean
151	125		rm -rf $RPM_BUILD_DIR/.
152	126
153	127		%files
154	128		/usr/share/%{dir}/
155	129
156	130		%changelog
157	131
158	132		* Mon Oct 24 2005 1.0-mdk.noarch.rpm
159	133
160	134		- Nova atualização do pacote de instalação. Inclusão dos exercícios avançados.
161	135
162	136		* Wed May 12 2005 1.0-mdk.noarch.rpm
163	137
164	138		- Atualizei o pacote para refletir as mudanças no site. Várias pequenas mudanças.
165	139
166	140		* Sun May 05 2005 1.0-1mdk.i586.rpm
167	141
168	142		- O pacote de instalação do braille Virtual para linux é criado.
169	143		```
170	144
171	145		#### ソースとバイナリのパッケージを作る
172	146
173	147		Linux distributions only accept RPM packages that can build the software. This will probably require creating build scripts and/or a Makefile. For more information see the section [[Deploying Your Application\|Deploying_Your_Application#Creating_a_Makefile_for_your_Lazarus_software]].
174	148
175	149		You need to use the %build section to compile the software.
176	150
177	151		Bellow is an example of a spec file capable of building the software. Be very careful when studing this as every little detail is important and follows a precise pattern.
178	152		```
179	153		Name: magnifier
180	154		Version: 3.2.1
181	155		Release: 1
182	156		Summary: Virtual Magnifying Glass
183	157		Group: Accessibility
184	158		License: GPL Version 2
185	159		URL: http://magnifier.sourceforge.net
186	160		Source0: http://internap.dl.sourceforge.net/sourceforge/magnifier/magnifier-3.2.1.zip
187	161		BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
188	162		BuildRequires: fpc >= 2.0.2, lazarus >= 0.9.12
189	163		Requires: ImageMagick
190	164
191	165		%description
192	166
193	167		Virtual Magnifying Glass is a free, open source, multiplatform, screen magnification tool. It is simple, customizable, and easy-to-use.
194	168
195	169		%prep
196	170		%setup -q magnifier
197	171
198	172		%build
199	173		make TARGET=%{_target_cpu}
200	174
201	175		%install
202	176		./install.sh DESTDIR=$RPM_BUILD_ROOT
203	177
204	178		%clean
205	179		rm -rf $RPM_BUILD_ROOT/
206	180
207	181		%files
208	182		%defattr(-,root,root,-)
209	183		/usr/share/magnifier/
210	184		/usr/bin/magnifier
211	185
212	186		%changelog
213	187
214	188		* Wed Feb 15 2006 Felipe Monteiro de Carvalho <felipemonteiro.carvalho at gmail.com> - 3.2-mdk.i386.rpm
215	189		- The Linux RPM package is created.
216	190		```
217	191
218	192		### Linux 上で Debian のパッケージを作る
219	193
220	194		Please, write me.
221	195
222	196		In the mean time have a look at this tutorial written by IBM.
223	197		<http://www-128.ibm.com/developerworks/linux/library/l-debpkg.html>
224	198
225	199		### GUInseng
226	200
227	201		[GUInseng](<http://www.guinseng.de/>) is a a GTK+ based installer for Linux released under GPL.
228	202
229	203		### The Zero Install system
230	204
231	205		[The Zero Install system](<http://0install.net/>) aims to provide a better way of installing software than traditional systems
232	206
233	207		(tarballs, apt-get, bundles, setup.exe, etc). Here are some of yours goals:
234	208
235	209		#### Anyone can install software
236	210
237	211		You don't have to be the administrator (root) just to install a word-processor.
238	212
239	213		#### Anyone can distribute software
240	214
241	215		You don't need to be blessed by a distribution (or anyone else) to be part of Zero Install. The system is completely
242	216
243	217		decentralised.
244	218
245	219		#### It doesn't matter whether software is installed or not
246	220
247	221		You just run it. Zero Install handles the rest (downloading and caching as needed).
248	222
249	223		#### Security
250	224
251	225		If one user downloads a malicious program, other users aren't affected. Users can share downloads without having to trust
252	226
253	227		each other. Installation does not execute any of the downloaded code. Digital signatures are always checked before new
254	228
255	229		software is run.
256	230
257	231		## Creating a Makefile for your Lazarus software
258	232
259	233		The following is a command line build system for a Lazarus software. This is particularly usefull if you with to create a RPM package suitable for inclusing on GNU/Linux distributions. The comments on the files should explain what each part does.
260	234
261	235
262	236		make.sh
263	237		```
264	238		#
265	239		# Detects and parses the architecture
266	240		#
267	241
268	242		ARCH=$(uname -m)
269	243
270	244		case "$ARCH" in
271	245
272	246		"i686") ARCH="i386";;
273	247
274	248		"i586") ARCH="i386";;
275	249
276	250		"i486") ARCH="i386";;
277	251
278	252		esac
279	253
280	254		echo "Target architecture: $ARCH"
281	255
282	256		#
283	257		# Detects and parses the OS
284	258		#
285	259
286	260		OS="linux"
287	261
288	262		echo "Target operating system: $OS"
289	263
290	264
291	265		#
292	266		# Command line to build the sofware
293	267		#
294	268
295	269		fpc -S2cgi -OG1 -gl -WG -vewnhi -l -Fu/usr/lib/lazarus/components/opengl/gtk2x11/ -Fi/usr/lib/lazarus/components/opengl/gtk2x11/include/ -Fu/usr/lib/lazarus/components/jpeg/ -Fu/usr/lib/lazarus/lcl/units/$ARCH-$OS/ -Fu/usr/lib/lazarus/lcl/units/$ARCH-$OS/ -Fu/usr/lib/lazarus/lcl/units/$ARCH-$OS/gtk2/ -Fu/usr/lib/lazarus/packager/units/$ARCH-$OS/ -Fu. -o./magnifier -dLCL -dLCLgtk2 magnifier.dpr
296	270		```
297	271
298	272		install.sh
299	273		```
300	274		#
301	275		# Parses command line options. Currently supported options are:
302	276		#
303	277		# DESTDIR Destination root directory
304	278		#
305	279
306	280		DESTDIR=""
307	281
308	282		for arg; do
309	283
310	284		case $arg in
311	285
312	286		DESTDIR=*) DESTDIR=${arg#DESTDIR=};;
313	287
314	288		esac;
315	289
316	290		done
317	291
318	292		#
319	293		# Does the install
320	294		#
321	295		# "mkdir -p" is equivalent to ForceDirectories pascal function
322	296		#
323	297
324	298		mkdir -p $DESTDIR/usr/share/magnifier
325	299
326	300		cp ./topleft.bmp $DESTDIR/usr/share/magnifier/
327	301		cp ./topright.bmp $DESTDIR/usr/share/magnifier/
328	302		cp ./bottomleft.bmp $DESTDIR/usr/share/magnifier/
329	303		cp ./bottomright.bmp $DESTDIR/usr/share/magnifier/
330	304		cp ./top.bmp $DESTDIR/usr/share/magnifier/
331	305		cp ./left.bmp $DESTDIR/usr/share/magnifier/
332	306		cp ./bottom.bmp $DESTDIR/usr/share/magnifier/
333	307		cp ./right.bmp $DESTDIR/usr/share/magnifier/
334	308		cp ./icon3.ico $DESTDIR/usr/share/magnifier/
335	309
336	310		mkdir -p $DESTDIR/usr/bin
337	311
338	312		cp ./magnifier $DESTDIR/usr/bin/
339	313		```
340	314
341	315		clean.sh
342	316		```
343	317		rm -rf *.o
344	318		rm -rf *.ppu
345	319
346	320		rm -rf *.pas~
347	321		rm -rf *.sh~
348	322		rm -rf *.bak
349	323
350	324		rm -rf *~
351	325
352	326		rm -rf magnifier
353	327		```
354	328
355	329		uninstall.sh
356	330		```
357	331		#
358	332		# Don´t use "rm -rf" in here, because you should only remove the files you created
359	333		#
360	334		rm -f /usr/share/magnifier/topleft.bmp
361	335		rm -f /usr/share/magnifier/topright.bmp
362	336		rm -f /usr/share/magnifier/bottomleft.bmp
363	337		rm -f /usr/share/magnifier/bottomright.bmp
364	338		rm -f /usr/share/magnifier/top.bmp
365	339		rm -f /usr/share/magnifier/left.bmp
366	340		rm -f /usr/share/magnifier/bottom.bmp
367	341		rm -f /usr/share/magnifier/right.bmp
368	342		rm -f /usr/share/magnifier/icon3.ico
369	343
370	344		rm -f /usr/share/magnifier/magnifier
371	345
372	346		rm -f /usr/bin/magnifier
373	347
374	348		rmdir /usr/share/magnifier
375	349		```
376	350
377	351		Makefile
378	352		```
379	353		#
380	354		# Targets
381	355		#
382	356
383	357		#
384	358		# The First target is the one build when there is nothing on make command line
385	359		#
386	360		all:
387	361		./make.sh
388	362
389	363		clean:
390	364		./clean.sh
391	365
392	366		install:
393	367		./install.sh
394	368
395	369		uninstall:
396	370		./uninstall.sh
397	371		```
398	372
399	373
400	374
401	375		## macOS のインストーラー
402	376
403	377		### macOS のパッケージメーカー（PackageMaker）を使う
404	378
405	379		Most macOS programs are distributed as a disk image file (.dmg extension). Normally you download or copy a program's .dmg file to your Mac and double-click it. This "mounts" the disk image and opens it in a window on the desktop, where you'll typically see a package file (.pkg extension) that you double-click to perform the actual program installation. After installation is complete, you "unmount" (eject) the mounted disk image by dragging it to the trash. You can also delete the .dmg file by dragging it to the trash as well.
406	380
407	381		The installer .pkg file is actually a directory, as is the resulting application bundle (.app extension) that it copies to the Applications folder. To the user, .pkg and .app files look and act like ordinary files, but they're really directories whose details have been hidden from the user. You can see what's inside a .pkg or .app file by entering normal cd commands in a terminal window (for example, cd progname.app) or by Ctrl-clicking the file and choosing Show Package Contents from the popup menu.
408	382
409	383		You create .pkg files using PackageMaker, which is installed along with the XCode tools in /Developer/Applications/Utilities. With PackageMaker, you select the folder containing the files you want to package and set other installation options, for example whether a password must be entered to install the program. Note that the folder you select can be an .app file. Choose File \| Create Package to create the .pkg file. You can also save your settings for future use in PackageMaker by choosing File \| Save to create a .pmsp file that you name (.pmproj with later versions).
410	384
411	385		To create a .dmg file, run the macOS Disk Utility, which is installed in /Applications/ Utilities. Select Images \| New \| Image from Folder and choose the folder containing your .pkg file and any other files you want to include in the disk image. In the Convert Image dialog, enter the name of the .dmg file to create, select where it should be saved, and select "compressed" as the image format. The .dmg file that Disk Utility creates is then ready for distribution.
412	386
413	387		### macOS に X11 と GTK をインストールする
414	388
415	389		GUI apps created with Lazarus that use the GTK widgetset require X11 and the GTK libraries to run. X11 is included with macOS, but may not be installed by default on a user's Mac, so you'll want to mention this in your app's read-me file.
416	390
417	391		To install the GTK libraries on a user's system, you could include instructions for using fink. Or you could create a separate .dmg file containing just the files from the /sw/lib folder on your Mac. If you don't want to install all of the subfolders under the /sw/lib folder, copy just the .dylib files from /sw/lib to a different folder and package this folder instead of /sw/lib. Also, remember that the GTK libraries installed on your Mac are specific to the processor that you're running. That is, if you want to support both PowerPC and Intel Macs you'll need to create two different .dmg files and instruct your users to install the appropriate one. Note that the GTK libraries only need to be installed once and can be used with any number of Lazarus GUI programs that you develop.
418	392
419	393		---
420	394		From the Free Pascal wiki, page "Deploying Your Application/ja", as the Internet Archive kept it on 2022-08-19, last changed on 2020-02-29. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).

Back to history