Lazarus Faq/ko: what changed

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

Old	New		Line
1	1		이 문서는 원래 www.lazarus.freepascal.org 에 있던 것 입니다. 관리 및 확장 면에서 위키가 훨씬 더 유용하기 때문에 이 곳으로 복사되었습니다.
2	2
3	3		## 일반적인 이야기
4	4
5	5		### 더 많은 FAQ 를 볼 수 있는 곳은 어디인가요?
6	6
7	7		[공식 웹사이트](http://www.lazarus.freepascal.org)를 보세요. 그밖의 괜찮은 FAQ 가 있습니다.
8	8
9	9		### 도대체 실행파일의 크기가 왜 이렇게 큰 겁니까?
10	10
11	11		실행파일의 크기가 큰 이유는 GDB (GNU Debugger) 를 사용하기 위한 많은 정보들을 포함하고 있기 때문입니다.
12	12
13	13		컴파일러에 이 디버깅 정보를 제거하기 위한 옵션 (-Xs) 이 있습니다만, 버전 2.0.2 이전의 컴파일러는 이 기능에 버그가 있기 때문에 제대로 동작하지 않습니다. 이 버그는 현재 개발버전에서는 수정되었습니다.
14	14
15	15		"strip" 이라는 이름의 프로그램을 사용하면 실행파일로 부터 디버그 심볼을 삭제할 수 있습니다. 이 프로그램은 lazarus\pp\bin\i386-win32\\ 에 있습니다.
16	16
17	17		커맨드 라인에서 간단하게 "strip --strip-all \<대상 실행파일의 경로와 이름\>" 을 입력 하세요.
18	18
19	19		실행파일을 좀 더 작게 만들려면, [UPX](http://upx.sourceforge.net/) 가 좋은 해법이 될 것입니다. UPX는 정말 멋진 실행파일 압축기 로서, 압축 해제에 추가적인 메모리가 필요없는 알고리즘을 사용합니다. (역자 주: 이 압축 알고리즘은 [LZO](http://www.oberhumer.com/opensource/lzo/) 라고 불리며, 오래 전 셀빅의 카마수트라 라는 어플에서 사용되었...^^) 또한 상당히 빠른 압축 해제 속도를 가지고 있습니다. (펜티엄 133에서 초당 10 MB 정도)
20	20
21	21		커맨드 라인에서 간단하게 "upx \<압축할 실행파일의 경로와 이름\>" 을 입력 하세요.
22	22
23	23		라자루스로 만든 간단한 GUI 어플리케이션의 경우 strip과 upx를 사용한 후 크기는 다음과 같습니다.
24	24
25	25		- 리눅스 상에서는 ~ 700kb
26	26		- 윈도우 상에서는 ~ 420kb
27	27
28	28		그렇다고 UPX가 꼭 좋은 것은 아닙니다. UPX에 대한 좀 더 자세한 이야기는 [[Size Matters\|크기문제에]] 대한 페이지를 참고하세요.
29	29
30	30		또 한가지 주목해야 할 사실은, 라자루스의 "hello world" 프로그램은 그 자체로 이미 다음에 나열된 많은 기능들을 포함하고 있다는 것 입니다.
31	31
32	32		- XML 제어 라이브러리
33	33		- png, xpm, bmp 그리고 ico 파일을 다루는 이미지 라이브러리
34	34		- 라자루스 컴포넌트 라이브러리의 위젯 대부분
35	35		- 프리 파스칼 런타일 라이브러리 전체
36	36
37	37		큰 크기의 실행파일 이면에는, 사실 이렇게 실제 어플리케이션이 필요로 하는 대부분의 기능들이 이미 들어 있습니다.
38	38
39	39		라자루스 실행파일의 크기는 처음에는 매우 크지만 아주 조금씩 늘어나게 되는데, 이는 프리파스칼 컴파일러와 라자루스가 폼을 다루는 방식 때문 입니다. C++ 프로젝트의 경우 (뭐 다른 언어들도 마찬가지 입니다만) "hello world" 프로그램은 처음에는 매우 작지만 조금만 복잡한 기능을 추가하면, 그 크기가 급격하게 늘어나게 됩니다.
40	40
41		-	~~<figure>~~
42		-	~~<img src="Lazarus_vs_cpp.png" title="Lazarus_vs_cpp.png" />~~
43		-	~~<figcaption>Lazarus_vs_cpp.png</figcaption>~~
44		-	~~</figure>~~
	41	+	![](/wiki-images/d/de/Lazarus_vs_cpp.png)
45	42
46	43		### 윈도 환경에서 링킹이 오래 걸리는 이유는?
47	44
48	45		이 문제는 FPC 2.2 와 라자루스 0.9.24 부터 해결되었습니다. 업데이트 하세요. 이후 설명은 이전 버전에 대한 것 입니다.
49	46
50	47		Generally speaking, compilation on Windows takes more time then other platforms because the GNU Linker utilized by Free Pascal is slow on this platform. This problem only affects Windows, and is only bad on relatively old computers (less then 1Ghz) and computers with little RAM (128MB or less).
51	48
52	49		Also, if you smartlink LCL the linking will be much slower. A study about this is located here: [[File size and smartlinking]]
53	50
54	51		A internal linker was developed, and is ready, but will only be available when Free Pascal 2.2 is released (of course it's also available via subversion). It decreases the linking time dramatically.
55	52
56	53		Note: In 2.1.1 Windows uses an internal linker for win32/64/ce which speeds the process up a bit. A Lazarus recompile then eats about 280MB.
57	54
58	55		### ppc386.cfg이나 fpc.cfg이 필요한가요?
59	56
60	57		fpc.cfg만 있으면 됩니다. 이를 통해서 컴파일러는 라이브러리를 어디서 찾아야 하는지 알게 됩니다.
61	58
62	59		### lazarus 는 어떻게 컴파일하나요?
63	60
64	61		다음과 같이 하세요:
65	62
66	63		`$ cd lazarus`\
67	64		`$ make clean all`
68	65
69	66		### LCL 을 이용한 다른 프로젝트는 어떻게 빌드할 수 있나요?
70	67
71	68		프로그램을 만드는데 IDE 를 사용할 수 없다면, lazbuild 를 사용하세요. 이것은 lazarus 프로젝트 및 패키지를 만들기 위한 명령행 버전입니다. LCL 프로그램을 IDE 나 lazbuild 없이 만들려면 다음 행을 fpc.cfg 끝에 추가하세요.
72	69
73	70		` # searchpath for other toolkits (Linux)`\
74	71		` -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/{YourToolKit}`
75	72
76	73		` # searchpath for other toolkits (Windows)`\
77	74		` -Fu/{YourLazarusDirectory}/components/units/{YourToolKit}`
78	75
79	76
80	77		Where {YourToolKit} may be gtk2, gnome, qt or win32 and run:
81	78
82	79
83	80		ppc386 your.project.pp
84	81
85	82		Hint: Don't forget to install the development packages for your toolkit otherwise you might a receive something like: [[Linker message: cannot find -l]].
86	83
87	84		### FPC의 어떤 버전이 필요한가요?
88	85
89	86		MacOSX는 2.0.4, 그 외의 모든 시스템은 2.2.2 버전이 필요합니다. 또한 2.2.3 버전이나 2.3.x 버전의 경우 svn을 통해서 사용하실 수 있습니다. 주의: 2.2.0 버전은 MacOSX에서 파일명의 대소문자 구분 관련 버그가 있습니다.
90	87
91	88		### Lazarus가 컴파일이 되지 않습니다.
92	89
93	90		1. 컴파일러가 올바른 버전인지 체크 하십시오.
94	91		2. fpc 라이브러리가 같은 버전인지 체크 하십시오.
95	92		3. fpc.cfg 파일 있는지, 그리고 ppc386.cfg 파일이 오래된 것은 아닌지 체크 하십시오.
96	93		4. 해당 OS관련 FAQ도 체크 하십시오.
97	94
98	95		### When I try to compile a project, I have an error
99	96
100	97		#### "Cannot find Unit interfaces". How can I solve this?
101	98
102	99		It means the compiler can not find the file 'interfaces.ppu' or it means it found one, but it is wrong or outdated.
103	100
104	101		This unit can be found in {LazarusDir}\lcl\units\\{TargetCPU}-{TargetOS}\\{LCLWidgetSet}\interfaces.ppu. For example: /home/username/lazarus/lcl/units/i386-linux/gtk/interfaces.ppu.
105	102
106	103		Make sure, it is only there. If you have multiple versions of interfaces.ppu, then you probably have a wrong configuration (for instance you added a lcl directory to a search path). Remove all interfaces.ppu, but the one in the directory above.
107	104
108	105		If you selected a different widgetset than you used to build lazarus, you need to build the LCL for this widgetset.
109	106
110	107		If it is there, but you get this error, you are using a different compiler / rtl for compiling your project than you used for compiling your Lazarus IDE. You can do one of the following
111	108
112	109		- Rebuild the LCL (or Lazarus completely) with the compiler selected in the Environmnent Options. You can do this with Tools -\> Build Lazarus. Before doing this, check the current settings in Tools -\> Configure Build Lazarus.
113	110		- Change the compiler in the Environment Options to the one you used to compile Lazarus. Look carefully also in the Environment Options to see if you are using the correct paths for the Lazarus Directory and the FPC sources directory. Check that there is only one version of the compiler configuration file fpc.cfg - it should reside in /etc/ for Linux/Unix systems or in the same directory as the fpc compiler for Windows systems. Try to run "fpc -vt bogus" to check which fpc.cfg is being used in your system. Rogue copies often creep in if you have updated your compiler to a new version; they may be found in your home directory or in the same directory as the one in which you built your new compiler. DELETE THESE!!
114	111		- You may also try to change the widgetset currently selected for the project. For example, the sample project "objectinspector" that comes with Lazarus is set to gtk by default. Compiling this project will surely give you "Can't find unit interfaces" in Windows platform. Changing widgetset to default(Win32) in Project \\| Compiler Options... \\| LCL Widget Type (various) should fix this issue.
115	112
116	113		### When I try to compile delphi projects under lazarus, I have an error
117	114
118	115		#### at the line :{\$R *.DFM} How can I solve this problem ?
119	116
120	117		Lazarus (or better Linux) doesn't know about resources, so you can't use them in the way Delphi/Win32 does. However Lazarus uses a method pretty compatible with this. You can still use your Delphi layouts (.dfm files) if you use the following steps:
121	118
122	119		- You need a textual version of the .dfm files. D5 and higher are doing this as default. If you have older files: ALT-F12 to see the layout as text and paste/copy. When you have a text .dfm file, just copy it to a .lfm file.
123	120		- Create a file with lazres (in lazarus/tools) lazres yourform.lrs yourform.lfm
124	121		- Add the following initialization section to
125	122
126	123		` initialization`\
127	124		` {$I yourform.lrs}`
128	125
129	126		Please keep in mind that not all properties in the dfm are supported yet by lazarus, so you might get a crash.
130	127
131	128		#### 'Identifier not found LazarusResources'.
132	129
133	130		When creating a form Lazarus automaticaly add some extra units to the uses section of your form unit. During the conversion of a delphi unit to a Lazarus unit this does not happen. So you need to add LResources to the Uses section of your form unit.
134	131
135	132		### When accessing events of objects e.g. the onclick event of a button I get the following error. ERROR unit not found: stdCtrls
136	133
137	134		Make sure, in the Project -\> Project Inspector, that your project depends on the package 'LCL' and that you have installed the FPC sources.
138	135
139	136		Lazarus is the IDE and the visual components library LCL. All other stuff, like IO, Database, FCL and RTL are provided by FPC. The IDE needs the paths to all sources.
140	137
141	138		The FPC source path can be set via: Environment -\> Environment Options -\> Files -\> FPC source directory
142	139
143	140		### How to embed a small file in the executable, without the need of a separate file? How to embed a resource?
144	141
145	142		For example:
146	143
147	144		`/your/lazarus/path/tools/lazres sound.lrs sound1.wav sound2.wav ...`
148	145
149	146		will create sound.lrs from sound1.wav and sound2.wav.
150	147
151	148		Then include it behind the form lrs file:
152	149
153	150		`...`\
154	151		`initialization`\
155	152		`{$i unit1.lrs} // this is main resource file (first)`\
156	153		`{$i sound.lrs} // user defined resource file`\
157		-	\
	154	+
158	155		`end.`
159	156
160	157		In your program you can then use:
161	158
162	159		`Sound1AsString:=LazarusResources.Find('sound1').Value;`
163	160
164	161		### 디버그 결과를 어떻게 볼 수 있나요?
165	162
166	163		LCL은 LCLProc 유닛의 2개 프로시져에서 디버그 출력을 작성 할수 있습니다.
167	164
168	165		2개 프로시져 명:
169	166
170	167		- DebugLn: which works about the same as WriteLn, but accepts only strings.
171	168		- DbgOut: which works about the same as Write, but accepts only strings.
172	169
173	170		In normal circumstances the output is written to stdout. If stdout is closed, (for example when the application is {\$AppType Gui} or compiled with -WG on Windows), no output is written.
174	171
175	172		Debug output can also be written to file. The initialization code of the LCLProc unit checks Lazarus.exe's command line parameters for '--debug-log=\<file\>'. On finding this parameter any subsequent debug output is sent to \<file\>.
176	173
177	174		만약 '--debug-log' 명령어 파라메터를 사용하지 않으면, 시스템 환경설정의 변수 xxx_debuglog를 검사합니다, xxx는 파일 확장자를 제외한 파일 명입니다. For Lazarus this would be lazarus_debuglog. 만약 환경설정에서 변수가 없다면 lazarus_debuglog 환경설정의 변수 파일을 받아서 디버그 출력합니다.
178	175
179	176		예: 설정하려면:
180	177
181	178		`set lazarus_debuglog=c:\lazarus\debug.txt`
182	179
183	180		디버그 출력은 다음파일에 저장됩니다. c:\lazarus\debug.txt
184	181
185	182		Since this is implemented in lclproc, every application using lclproc, can use this output facility.
186	183
187	184		Debuging Lazarus
188	185		Most useful for Windows: If you want output on a console, add {\$APPTYPE console} to lazarus.pp ; Then rebuild Lazarus.
189	186
190	187		### What is the meaning of the various file extensions used by Lazarus?
191	188
192	189		The [[Lazarus Tutorial\|Lazarus Tutorial#The Lazarus files]] explains some extensions by an example. Here is a brief list:
193	190
194	191		`*.lpi`
195	192		Lazarus Project Information file (stored in XML; contains project-specific settings)
196	193
197	194		`*.lpr`
198	195		Lazarus Program file; contains Pascal source of main program
199	196
200	197		`*.lfm`
201	198		Lazarus Form file; contains configuration information for all objects on a form (stored in a Lazarus-specific textual format; the actions are described by Pascal source code in a corresponding `*.pas` file)
202	199
203	200		`.pas` or `.pp`
204	201		Unit with Pascal code (typically for a form stored in a corresponding `*.lfm` file)
205	202
206	203		`*.lrs`
207	204		Lazarus Resource file (this is a generated file; not to be confused with a Windows resource file).
208	205
209	206		This file can be created with lazres tool (in directory Lazarus/Tools) using commandline: lazres myfile.lrs myfile.lfm
210	207
211	208		`*.ppu`
212	209		Compiled unit
213	210
214	211		`*.lpk`
215	212		Lazarus package information file. (stored in XML; contains package-specific settings)
216	213
217	214		### I have fixed/improved lazarus. How can I add my changes to the official lazarus source?
218	215
219	216		Create a patch and send it to the developers. For details see [[Creating A Patch]].
220	217
221	218		### When I do var mytext: text; to declare a text file, I get "Unit1.pas(32,15) Error: Error in type definition". How can I fix this?
222	219
223	220		The TControl class has a [[doc:lcl/controls/tcontrol.text.html\|Text]] property. In a method of a form, that has higher visibility, the [[doc:rtl/system/text.html\|Text]] type from the system unit. You can use the [[doc:rtl/system/textfile.html\|TextFile]] type, which is just an alias for the Text type or you can add the unit to the type definition.
224	221
225	222		`var`\
226	223		` MyTextFile: TextFile;`\
227	224		` MyText: System.Text;`
228	225
229	226		A similar name clash exists with assigning and closing a text file. TForm has a assign and a [[doc:lcl/forms/tcustomform.close.html\|Close]] method. You can use [[doc:rtl/objpas/assignfile.html\|AssignFile]] and [[doc:rtl/objpas/closefile.html\|CloseFile]] or add the unit name System.
230	227
231	228		### I get an error when using Printer.BeginDoc
232	229
233	230		The unit Printers must be added to the uses section.
234	231
235	232		The Printer4Lazarus package must be added to your project requirement in the IDE under: Project\\|Project Inspector\\|Add\\|New Requirement\\|Package Name:
236	233
237	234		If the package Printer4Lazarus package is not in the list when opening the dropdown box it must be installed. The package is part of the Lazarus installation and can be found in: \[lazarus installed directory\]\components\printers
238	235
239	236		If you used the default installation directories \[lazarus installed directory\] is:
240	237
241	238		- Windows: c:\lazarus
242	239		- Linux: /usr/lib/lazarus
243	240
244	241		The same solution also applies to the exception you can get when referencing Printer.Printers
245	242
246	243		### Why are TForm.ClientWidth/ClientHeight the same as TForm.Width/Height
247	244
248	245		The TForm.Width/Height do no include the frame, because there was no way to retrieve the frame size on all platforms. Without a reliable way, the LCL would move the forms around on the screen or resize them endlessly.
249	246
250	247		Eventually when there is a reliable way to get the size and position of a window with its frame on all platforms, then it will be changed. To keep compatibility with older LCL forms, a version number and some extra methods will be added.
251	248
252	249		### I created a Patch to dock the IDE Messages form on the "Source Code Editor" form (at bottom)
253	250
254	251		Such patches will not be applied, because they only implement a small part of the needed docking. The goal is to create a complete dock manager and use that. A complete dock manager can dock all IDE windows and it allows to let the user define how to dock. For example dock the messages window above or below the source editor or ... or not at all. For instance:
255	252
256	253		+-------------------++--+
257	254		\|menu \|\| \|
258	255		+-------------------+\| \|
259	256		+--++---------------+\| \|
260	257		\|PI\|\| Source Editor \|\|CE\|
261	258		+--+\| \|\| \|
262	259		+--+\| \|\| \|
263	260		\| \|+---------------++--+
264	261		\|OI\|+-------------------+
265	262		\| \|\|messages \|
266	263		+--++-------------------+
267	264
268	265		The dock manager can store the layout and restore it on next load. Preferably the dock manager can dock in pages too. The dock manager does not need to use drag and drop. All patches implementing docking without a dock manager makes it harder to implement a real dock manager and will be rejected.
269	266
270	267		### How can I become a developer lazarus and access management in the SVN and bug-tracker?
271	268
272	269		First of all: you must learn about Lazarus, to prove your knowledge and skill. Start by reading the [[Lazarus Documentation\|wiki articles]], read the Lazarus source code, giving a look at the [Lazarus Bug-Tracker](http://www.lazarus.freepascal.org/mantis), fix some bugs, and if you think you are ready, contact the developers on the [mailing list](http://www.mail-archive.com/lazarus@miraclec.com).
273	270
274	271		## Where is ... defined
275	272
276	273		### Virtual key constants
277	274
278		-	~~Virtual key constants are defined in LCLType. Add LCLtype to your <b>uses</b>.~~
	275	+	Virtual key constants are defined in LCLType. Add LCLtype to your uses.
279	276
280	277		## Using the IDE
281	278
282	279		### How can I use "identifier completion"?
283	280
284	281		You can invoke identifier completion by pressing \[ctrl\]\[space\]. Under the menu item Environment -\> Editor Options -\> Code Tools -\> Automatic Features you can set how quick this should happen automatically.
285	282
286	283		## Linux
287	284
288	285		### How can I debug on Linux without the IDE?
289	286
290	287		First of all you need a debugger. gdb is the standard debugger under linux and there are several GUI-frontends available. One common frontend is ddd, which is part of most common distributions. To compile lazarus/lcl with debug-information you should then use the following commands to start a debug session:
291	288
292	289		` $ make clean; make OPT=-dDEBUG`\
293	290		` $ ddd lazarus`
294	291
295	292		Be warned however, that ddd is not as comfortable as e.g. the Lazarus debugger. Specially if it comes to view the contents of a variable you have to take into account that ddd/gdb are case sensitive whereas Pascal is case-insensitive. Therefore you have to type all variable names in uppercase to see their contents. For more information take a look into the fpc-manuals.
296	293
297	294		### I can debug now but ddd does not find my sources or complains that they contain no code. Whats that?
298	295
299	296		This is a path-related problem with either gdb or ddd. You can aviod this by
300	297
301	298		- Use the "Change directory" command from the ddd menu and choose the directory where the sources are located. The drawback of this method is that you now can't use the source of the program you started with (e.g. lazarus). Thus it may be neccessary to change the directory multiple times.
302	299		- In ddd goto \[Edit\] \[gdb-settings\] and set the search-path
303	300		- Create a \$(HOME)/.gdbinit file like:
304	301
305	302		` directory /your/path/to/lazarus`\
306	303		` directory /your/path/to/lazarus/lcl`\
307	304		` directory /your/path/to/lazarus/lcl/include`
308	305
309	306		### I receive an error during the linking that states /usr/bin/ld can't find -l\<some lib\>
310	307
311	308		Package Based Distributions
312	309		You need to install the package that provides the lib\<somelib\>.so or lib\<somelib\>.a files. Dynamic libs under linux have the extension .so, while static libs have the extension .a. On some Linux distro's you have installed the package (rpm, deb) \<packagename\> which provides \<some lib\>, but you also need the development package (rpm, deb), normally called \<packagename\>-dev, which contains the .a (static lib) and/or the .so (dynamic lib).
313	310
314	311		Some distributions have commands to find which package contains a file:
315	312
316	313		Mandriva
317	314
318	315		`[]$ urpmf lib<somelib>.so`
319	316
320	317
321	318		will list all packages containing the file named lib\<somelib\>.so, you'll have to install those ending in -devel
322	319
323	320
324	321		Debian
325	322
326	323
327	324		install the apt-file utility (apt-get install apt-file) then
328	325
329	326		`[]$ apt-file search lib<somelib>.so`
330	327
331	328
332	329		will list all packages containing the file named lib\<somelib\>.so, you'll have to install those ending in -dev
333	330
334	331		Source Based Distributions and Manual Compilation (LFS)
335	332		Make sure that there is a lib\<somelib\>.a in the path, and that it contains the right version. To let the linker find the dynamic library, create a symlink called lib\<some lib\>.so to lib\<some lib\>\<version\>-x,y.so if necessary (and/or for static lib; lib\<some lib\>.a to lib\<some lib\>\<version\>-x,y.a).
336	333
337	334		FreeBSD
338	335		As source based distro's, and also make sure you have -Fl/usr/local/lib in your fpc.cfg and/or Lazarus library path. Keep in mind that GTK1.2 has "gtk12" as package name under FreeBSD. (same for glib) NOTE: This has changed as of late. Newest ports have gtk-12 and glib-12 as well. You might stumble on this problem, since FPC requires the "-less" ones, you will need to symlink them like this:
339	336
340	337		`[]# cd /usr/local/lib && ln -s libglib-12.so libglib12.so`\
341	338		`[]# cd /usr/X11R6/lib && ln -s libgtk-12.so libgtk12.so`\
342	339		`[]# cd /usr/X11R6/lib && ln -s libgdk-12.so libgdk12.so`
343	340
344	341		NetBSD
345	342		As source based distro's, and also make sure you have -Fl/usr/pkg/lib in your fpc.cfg and/or Lazarus library path
346	343
347	344		### How can I convert a kylix 2 project into a lazarus project?
348	345
349	346		Nearly the same way as converting a Kylix project into a Delphi/VCL project.
350	347
351	348		The LCL (Lazarus Component Library) tries to be compatible to Delphis VCL. Kylix CLX tries to be QT compatible. Here are some general hints:
352	349
353	350		- Rename all used CLX Q-units like QForms, QControls, QGraphics, ... into their VCL counterparts: Forms, Controls, Graphics, ...
354	351		- Add LResources to the uses section of every form source
355	352		- Rename or copy all .xfm files to .lfm files.
356	353		- Rename or copy .dpr file to .lpr file.
357	354		- Add "Interfaces" to the uses section in the .lpr file.
358	355		- Remove {\$R *.res} directive
359	356		- Remove {\$R *.xfm} directive
360	357		- Add {\$mode objfpc}{\$H+} or {\$mode delphi}{\$H+} directive to .pas and .lpr files
361	358		- Add an initialization section to the end of each form source and add an include directive for the .lrs file (lazarus resource file):
362	359
363	360		` initialization`\
364	361		` {$I unit1.lrs}`
365	362
366	363
367	364		The .lrs files can be created via the lazres tool in: (lazarusdir)/tools/lazres.
368	365
369	366		For example: ./lazres unit1.lrs unit1.lfm
370	367
371	368		- Fix the differences. The LCL does not yet support every property of the VCL and the CLX is not fully VCL compatible.
372	369
373	370		- To make it more platform independant, reduce unit libc (which is deprecated) references and substitute with native FPC units like baseunix/unix as much as possible. This will be necessary to support other targets than linux/x86 (including OS X, FreeBSD and Linux/x86_64)
374	371
375	372		### When compiling lazarus the compiler can not find a unit. e.g.: gtkint.pp(17,16) Fatal: Can't find unit GLIB
376	373
377	374		1\. Check a clean rebuild: do a 'make clean all'
378	375
379	376		2\. Check if the compiler has the correct version (2.0.4 or higher)
380	377
381	378		3\. Check if the compiler is using the right config file. The normal installation creates /etc/fpc.cfg. But fpc also searches for ~/.ppc386.cfg, ~/.fpc.cfg, /etc/ppc386.cfg and it uses only the first it finds.
382	379
383	380
384	381		Hint: You can see which config file is used with 'ppc386 -vt bogus'
385	382
386	383		Remove any ppc386.cfg as it is really obsolete.
387	384
388	385		4\. Check if the config file (/etc/fpc.cfg) contains the right paths to your fpc libs. There must be three lines like this:
389	386
390	387		` -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget`\
391	388		` -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/rtl`\
392	389		` -Fu/usr/lib/fpc/$fpcversion/units/$fpctarget/*`
393	390
394	391
395	392		The first part of these paths (/usr/lib/fpc) depends on your system. On some systems this can be for example /usr/local/lib/fpc/... .
396	393
397	394		Hint: You can see your searchpaths with 'ppc386 -vt bogus'
398	395
399	396		5\. Check that the config file (/etc/fpc.cfg) does not contain search paths to the lcl source files (.pp, .pas):
400	397
401	398		` forbidden: -Fu(lazarus_source_directory)/lcl`\
402	399		` forbidden: -Fu(lazarus_source_directory)/lcl/interfaces/gtk`
403	400
404	401
405	402		If you want to add the lcl for all your fpc projects, make sure that the two paths look like the following and are placed after the above fpc lib paths:
406	403
407	404		` -Fu(lazarus_source_directory)/lcl/units/$fpctarget`\
408	405		` -Fu(lazarus_source_directory)/lcl/units/$fpctarget/gtk`
409	406
410	407		6\. Check if the missing unit (glib.ppu) exists in your fpc lib directory. For example the gtk.ppu can be found in /usr/lib/fpc/\$fpcversion/units/i386-linux/gtk/. If it does not exists, the fpc lib is corrupt and should be reinstalled.
411	408
412	409		7\. Check if the sources are in a NFS mounted directory. In some cases the NFS updates created files incorrectly. Please, try to move the sources into a non NFS directory and compile there.
413	410
414	411		8\. If you are still not succeeded try to use samplecfg script as follows:
415	412
416	413		\# cd /usr/lib/fpc/version/
417	414
418	415		\# sudo ./samplecfg /usr/lib/fpc/\\\$version /etc
419	416
420	417		Note! Do not put - / - after etc because if you do that the system will create a file - /etc/fpc.cfg/fpc.cfg. In fact we want that samplecfg make a file - /etc/fpc.cfg - not the folder /etc/fpc.cfg.
421	418
422	419		### I have installed the binary version, but when compiling a simple project, lazarus gives: Fatal: Can't find unit CONTROLS
423	420
424	421		Probably you are using a newer fpc package, than that used for building the lazarus binaries. The best solution is to download the sources and compile lazarus manually. You can download the source snapshot or get the source via svn:
425	422
426	423		` $ bash`\
427	424		` $ svn checkout `[`http://svn.freepascal.org/svn/lazarus/trunk`](http://svn.freepascal.org/svn/lazarus/trunk)` lazarus`\
428	425		` $ cd lazarus`\
429	426		` $ make clean all`
430	427
431	428		Make sure that lazarus get the new source directory: Environment-\>General Options-\>Files-\>Lazarus Directory Top
432	429
433	430		### Lazarus compiles, but linking fails with: libgdk-pixbuf not found
434	431
435	432		Install the gdk-pixbuf library for gtk1.x:
436	433
437	434		Where to find the gdk-pixbuf library:
438	435
439	436		RPMs: <http://rpmfind.net/linux/rpm2html/search.php?query=gdk-pixbuf&submit=Search+>...&system=&arch=
440	437
441	438		Debian packages: libgdk-pixbuf-dev
442	439
443	440		Sources: <ftp://ftp.gnome.org/pub/gnome/unstable/sources/gdk-pixbuf/>
444	441
445	442		### I have SuSE and I get /usr/bin/ld: cannot find -lgtk Error: Error while linking
446	443
447	444		SuSE installs the gtk devel libs under /opt/gnome/lib (or /opt/gnome/lib64 for 64 bits), which is not in the standard lib path. Simply add it to your /etc/fpc.cfg. (-Fl/opt/gnome/lib).
448	445
449	446		### Lazarus crashes with runtime error 211 after I installed a component
450	447
451	448		After I installed a component, Lazarus crashes with the following message:
452	449
453	450		`Threading has been used before cthreads was initialized.`\
454	451		`Make cthreads one of the first units in your uses clause.`\
455	452		`Runtime error 211 at $0066E188`
456	453
457	454		How can I fix this?
458	455
459	456		Your freshly installed component is using threads. FPC on *nix doesn't automatically include threading support, but it must be intialized. This initialization is done in the cthreads unit. Every application using the component needs to add this unit to the uses clause of the main program. Lazarus itself is no exception. This can be done in two ways:
460	457
461	458		1\) Open the package. In the package editor click on Options. Under page Usage add to the custom options -dUseCThreads. Then rebuild the IDE. This way the cthreads unit will be automatically used by the IDE under unix and the cthreads are initialized.
462	459
463	460		2\) In order to avoid modifying package, a fpc compiler option could be used directly. Open menu Tools-\>Configure "build Lazarus". Configure "build Lazarus" dialog will be shown, in field "Options:" type -Facthreads and then press "OK" button. The next step is to install the package. Lazarus will be built with option -Facthreads which means that it will treat main program as if unit cthreads where first in uses clause.
464	461
465	462		Hint: Maybe your old (non-crashing) lazarus executable is stored as lazarus.old in the same directory as the crashing lazarus executable.
466	463
467	464		See also [[Multithreaded Application Tutorial\|Multithreaded_Application_Tutorial#Units_needed_for_a_multithreaded_application]]
468	465
469	466		### When I run a program with threads I get runtime error 232
470	467
471	468		The complete error message is:
472	469
473	470		`This binary has no thread support compiled in.`\
474	471		`Recompile the application with a thread-driver in the program uses`\
475	472		`clause before other units using thread.`\
476	473		`Runtime error 232`
477	474
478	475		Solution: Add cthreads as first unit to the uses clause of your main program, usually the .lpr-file.
479	476
480	477		### I have Ubuntu Breezy and my fonts in Lazarus IDE look too big
481	478
482	479		If Lazarus is compiled with Gtk1.2, the settings in Gnome Preferences/Font don't have any effect as they are related to Gtk2. You could try this solution: Create a file named .gtkrc.mine in your home directory (if it's not already there) and add these lines to it:
483	480
484	481		style "default-text" {
485	482		fontset = "--arial-medium-r-normal---100-----iso8859-1,\
486	483		--helvetica-medium-r-normal---100------"
487	484		}
488	485
489	486		class "GtkWidget" style "default-text"
490	487
491	488		If this is not enough try and create also a .gtkrc symlink to .gtkrc.mine . It worked in this way under Xubuntu 7.10.
492	489
493	490		### How can my gtk programs use custom rc files?
494	491
495	492		Option a) Name the rc file yourprogram.gtkrc and put it in the same directory where the executable is.
496	493
497	494		Option b) Use unit GtkInt and call GTKWidgetSet.SetRCFilename('your_preferred_rc_file'); Best done before Application.Initialize in the .lpr file with {\$IFDEF LCLGtk}.
498	495
499	496		### I have Ubuntu and I cannot compile for Gtk2 due to missing libraries
500	497
501	498		Ubuntu has a problem with not creating all the symbolic links that you'll need even when the libraries are installed. Make sure that all missing libraries when trying to link for Gtk2 have their appropriate links. For instance, you might need to do:
502	499
503	500		cd /usr/lib
504	501		sudo ln -s libgdk-x11-2.0.so.0 libgtk-x11-2.0.so
505	502
506	503		Make sure that the \[whatever\].so symbolic links are created and point to the actual libraries.
507	504
508	505		### How can I compile a program for Gtk2?
509	506
510	507		At the moment, the Gtk2 compiled IDE is a little unstable, but you can compile software for Gtk2 using the Gtk1 IDE.
511	508
512	509		To start with recompile LCL for Gtk2. Go to the menu "Tools"-\>"Configure Build Lazarus" and set LCL to clean+build and everything else to none.
513	510
514	511		Now click Ok and go to the menu "Tools"-\>"Build Lazarus"
515	512
516	513		Now you can compile your software with Gtk2 going on the Compiler options and changing the widgetset to Gtk2.
517	514
518	515		### I get this message: "\[WARNING\] ** Multibyte character encodings (like UTF8) are not supported at the moment."
519	516
520	517		Since revision 10535 (0.9.21) this message doesn't exist anymore. Previously it was used to warn that a UTF-8 encoding was used. The internal keyhandling routines for the gtk1 widgetset couldn't handle such encoding for keypresses, with the result that keypresses with for instance accented chars were not or wrong detected.
521	518
522	519		(original text for older versions of lazarus)\
523		-	<strike> This warning message indicates that your locale enconding is set to utf-8. If you are using Gtk 1 this can be a serious problem and prevent the correct working of Lazarus or software created with Lazarus.
	520	+	This warning message indicates that your locale enconding is set to utf-8. If you are using Gtk 1 this can be a serious problem and prevent the correct working of Lazarus or software created with Lazarus.
524	521
525	522		To work around this, just change your locale to a non utf-8 before executing the program on the command line, like this:
526	523
527	524		export LC_CTYPE="pt_BR"
528	525		export LANG="pt_BR"
529	526		export LANGUAGE="pt_BR"
530	527		./lazarus
531	528
532		-	~~Substitute pt_BR with the locale for your country. You can create a script to automate this. </strike>~~
	529	+	Substitute pt_BR with the locale for your country. You can create a script to automate this.
533	530
534	531		## Windows
535	532
536	533		### When I cycle the compiler, I get:The name specified is not recognized as an internal or external command, operable program or batch file.\>& was unexpected at this time.
537	534
538	535		In the compiler directory there is an OS2 scriptfile named make.cmd. Different versions of Windows also see this as a script file, so remove it since what is needed for OS2 becomes a hindrance on Windows.
539	536
540	537		### When I cycle the compiler, I get: make\[3\]: ./ppc1.exe: Command not found
541	538
542	539		I don't know why but somehow make has lost its path. Try to cycle with a basedir set like: make cycle BASEDIR=your_fpc_source_dir_herecompiler
543	540
544	541		### When I try to make Lazarus I get:
545	542
546	543		#### make.exe: * * * interfaces: No such file or directory (ENOENT). Stop.make.exe: * * * \[interfaces_all\] Error 2
547	544
548	545		You need to upgrade your make.
549	546
550	547		#### makefile:27: *** You need the GNU utils package to use this Makefile. Stop.
551	548
552	549		Make sure you didn't install FPC in a path with spaces in the name. The Makefile doesn't support it.
553	550
554	551		### How can I give my program an XP look like lazarus has?
555	552
556	553		Project -\> Project Options -\> Check 'Use manifest to enables themes'.
557	554
558	555		### When I run Windows program created in Lazarus it starts with a DOS window
559	556
560	557		Specify the -WG argument (Windows GUI) on the command line of the compiler or in the Lazarus IDE check the Windows GUI check box on the compiler options dialog box (Project menu -\> Compiler Options -\> Linking -\> target OS Specific options.
561	558
562	559		## Mac OS X
563	560
564	561		### 'unknown section attribute: no_dead_strip'라는 메시지와 함께 프로젝트 컴파일에 실패하는 이유는?
565	562
566	563		죽은 코드(Dead code) 제거 기능이 Xcode 1.5이전의 어셈블러와 링커에서는 지원하지 않습니다(Mac OS X 10.3.9버전에서 사용하는). 다음 컴파일 옵션을 꺼 주세요.
567	564
568	565		- Code \> Unit style \> Smart linkable (-CX)
569	566		- and Linking \> Link Style \> Link smart (-XX)
570	567
571	568		## Licensing
572	569
573	570		### Can I make commercial applications with Lazarus ?
574	571
575	572		Yes, the LCL is licensed under the LGPL with an exception, which allows you to link to it statically without releasing the source of your application. Modifications and enhancements to the LCL must be distributed with source. Lazarus, the IDE, is licensed under the GPL.
576	573
577	574		### Why are some components restricted from usage in commercial application ?
578	575
579	576		Lazarus comes with additional components, that were developed by third parties. Those are under various other Licenses. If you wish to use them you need to see the License within the source files of those packages. Most of those 3rd party components are in the directory "components".
580	577
581	578		### How do I know if a Component is part of the LCL ?
582	579
583	580		All LCL units are in the directory "lcl". A List of units belonging to the LCL can be found here <http://lazarus-ccr.sourceforge.net/docs/lcl/> . If you code uses units not listed on this page, you may have used a component that is not part of the LCL.
584	581
585	582		### Can I make commercial plug-ins for Lazarus ?
586	583
587	584		Yes, the IDEIntf part of the IDE is licensed under the LGPL with the same exception, so that shared data structures in this part will not force you to license your plug-in or design-time package under the GPL. You are free to choose a plug-in of any license; we don't want to limit your choice. Therefore non-GPL compatible plug-ins are allowed. Note that it's not allowed to distribute a precompiled Lazarus with these non-GPL-compatible plugins included statically; however, we do not see this as a severe limitation, since recompiling Lazarus is easy.
588	585
589	586		## Contributors and Comments
590	587
591	588		This page has been converted from the epikwiki [version](http://lazarus-ccr.sourceforge.net/index.php?wiki=LazarusFaq).
592	589
593	590		---
594	591		From the Free Pascal wiki, page "Lazarus Faq/ko", as it stood on 2015-06-06 after a change by FTurtle, out of the wiki's dump of 2024-05-26. 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).
595	592		Category: FAQs/ko
596	593		Category: Korean
597	594		Category: Lazarus/ko

Back to history