Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2001-12

Components missing

6 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Antonio Augusto Todo Bom Neto

Please, I'm older programmer, to COBOL, CLIPPER, dBaseII II II+ and other things but very new in Object Oriented Languages.

I instaled Lazarus binary code then FreePascal, after.

But no components are appearing in Lazarus.

Do I need to indicate any dir to Lazarus? Are the /usr/lib/lazarus/units/linux/* the LCL?

Thank you

Reply by email

Marco van de Voort
to Mattias Gaertner: On Mon, 10 Dec 2001 12:02:50 -0200 Sorry. I never tested the binary. You're right, the…
Show quoted text 13 lines
Antonio Augusto Todo Bom Neto wrote: > > Maybe the binary release is corrupt. Does anyone else has the same problem? > > > > These sources are compiled and the resulting ppu files are stored in > > <lazarusdir>/lcl/units/ > > This is the problem: I don't have this dir Sorry. I never tested the binary. You're right, the binary puts all ppu and o files of the lcl, interfaces, IDE and extra components in the lib/lazarus/units/linux directory. This makes only sense if there is a VERY good documentation, but there isn't any. You need the source to find out the declarations. I think, you should use the cvs version, which is pretty simple: cvs -d co lazarus make

And if usually update an already checked out CVS, don't forget to add -Pd as parameter to update

so
cvs [-d update -Pd lazarus

(the part in brackets can be omitted if you set the CVSROOT environment variabele to the :pserver part)

Reply by email

Antonio Augusto Todo Bom Neto
to Antonio Augusto Todo Bom Neto: Please, I'm older programmer, to COBOL, CLIPPER, dBaseII II II+ and other things but very…
Show quoted text 21 lines
On Thu, 6 Dec 2001 14:02:12 -0200 Antonio Augusto Todo Bom Neto wrote: > But no components are appearing in Lazarus. Maybe the binary release is corrupt. Does anyone else has the same problem? > Do I need to indicate any dir to Lazarus? Normally, you only have to set the freepascal compiler path in the environment->general options. > Are the /usr/lib/lazarus/units/linux/* the LCL? No. The lcl sources can be found in <lazarusdir>/lcl/ and <lazarusdir>/lcl/include/ These sources are compiled and the resulting ppu files are stored in <lazarusdir>/lcl/units/

This is the problem: I don't have this dir

But this is only the widget independent part. For gtk there are additional sources in <lazarusdir>/lcl/interfaces/gtk/

Neither this

which will be compiled to <lazarusdir>/lcl/units/gtk/

Nor this

Show quoted text 15 lines
So you have to add -Fu<lazarusdir>/lcl/units/ -Fu<lazarusdir>/lcl/units/gtk/ to the compiler to compile lcl programs. Also have a look on the FAQ on the website. Mattias _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Mattias Gaertner
to Antonio Augusto Todo Bom Neto: Please, I'm older programmer, to COBOL, CLIPPER, dBaseII II II+ and other things but very…
But no components are appearing in Lazarus.

Maybe the binary release is corrupt. Does anyone else has the same problem?

Do I need to indicate any dir to Lazarus?

Normally, you only have to set the freepascal compiler path in the environment->general options.

Are the /usr/lib/lazarus/units/linux/* the LCL?

No.
The lcl sources can be found in
<lazarusdir>/lcl/ and <lazarusdir>/lcl/include/

These sources are compiled and the resulting ppu files are stored in <lazarusdir>/lcl/units/

But this is only the widget independent part.
For gtk there are additional sources in
<lazarusdir>/lcl/interfaces/gtk/

which will be compiled to
<lazarusdir>/lcl/units/gtk/

So you have to add
-Fu<lazarusdir>/lcl/units/ -Fu<lazarusdir>/lcl/units/gtk/

to the compiler to compile lcl programs.
Also have a look on the FAQ on the website.

Mattias

Reply by email

Mattias Gaertner
to Mattias Gaertner: On Mon, 10 Dec 2001 12:02:50 -0200 Sorry. I never tested the binary. You're right, the…
Show quoted text 23 lines
> Antonio Augusto Todo Bom Neto wrote: > > > > Maybe the binary release is corrupt. Does anyone else has the same problem? > > > > > > These sources are compiled and the resulting ppu files are stored in > > > <lazarusdir>/lcl/units/ > > > > This is the problem: I don't have this dir > > Sorry. I never tested the binary. You're right, the binary puts all ppu and o files of the lcl, interfaces, IDE and extra components in the lib/lazarus/units/linux directory. This makes only sense if there is a VERY good documentation, but there isn't any. You need the source to find out the declarations. I think, you should use the cvs version, which is pretty simple: > > cvs -d co lazarus > make And if usually update an already checked out CVS, don't forget to add -Pd as parameter to update so cvs [-d update -Pd lazarus (the part in brackets can be omitted if you set the CVSROOT environment variabele to the :pserver part)

IMO the -d is more important:

cvs update -d

Mattias

Reply by email

Mattias Gaertner
to Antonio Augusto Todo Bom Neto: Please, I'm older programmer, to COBOL, CLIPPER, dBaseII II II+ and other things but very…
Show quoted text 6 lines
> Maybe the binary release is corrupt. Does anyone else has the same problem? > > These sources are compiled and the resulting ppu files are stored in > <lazarusdir>/lcl/units/ This is the problem: I don't have this dir

Sorry. I never tested the binary. You're right, the binary puts all ppu and o files of the lcl, interfaces, IDE and extra components in the lib/lazarus/units/linux directory. This makes only sense if there is a VERY good documentation, but there isn't any. You need the source to find out the declarations. I think, you should use the cvs version, which is pretty simple:

cvs -d co lazarus
make

Mattias

Reply by email