Sign in Join

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

Mailing lists / lazarus / 2000-12

wow! on win32.....

9 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

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

Florian Klaempfl
to mooseman: well, for the first time since i started playing with lazarus, i have been able to…
you wrote 6 lines
i updated by CVS lastnight the lazarus source. got the GTK exception as reported by others. downloaded the new FPC(1.0.2) today. just as a side note, i didn't download the FPC package complete with source. i had some problems with compiling lazarus as a result. it was complaining about not being able to find xmlcfg.pp and the other units related to xmlcfg.

xmlcfg is missed in 1.0.2, it's a "bug" of 1.0.2

has the FPC dir structure changed a lot recently? it seems that this installation 'looks' different. any comments?

No, it didn't change that much. Which version did you use before?

Reply by email

Marco van de Voort
to Marco van de Voort: Using recent 1.0.3 compiler: - the includefile "freebsd" is not found, but that is…
Show quoted text 9 lines
+ However when I run the binary I get: + + LM_SCREENINIT called --> should go to GTKObject.Init + TODO: check this Thats all you see ? This message was only a reminder for me that the following code maybe should go GTKObject.Init. After that the IDE is created.

I also see the object inspector and a splash screen flash. Does Lazarus use threading/Clone?
That part is as yet untested.

I'll try to ktrace the program/compile with lineinfo and get more info

Marco van de Voort ( or )

Reply by email

Marco van de Voort
to Marc Weustink: + From: Behalf Of + + After these changes (and seeing each build compiling the LCL three
Show quoted text 15 lines
> + However when I run the binary I get: > + > + LM_SCREENINIT called --> should go to GTKObject.Init > + TODO: check this > > Thats all you see ? This message was only a reminder for me that the > following code maybe should go GTKObject.Init. > > After that the IDE is created. I also see the object inspector and a splash screen flash. Does Lazarus use threading/Clone? That part is as yet untested. I'll try to ktrace the program/compile with lineinfo and get more info

The lineinfo part didn't do much. I sometimes get a RTE 216, sometimes a SIGBUS, and sometimes SIGSEGV, and never a traceback until now.

I tried to ktrace, and put the log on www.stack.nl/~marcov/trace.zip

I don't have a clue yet.

Marco van de Voort ( or )

Reply by email

mooseman
to mooseman: well, for the first time since i started playing with lazarus, i have been able to…

ah! thanks for letting me know about the xmlcfg missing from the package.

my first install was a 0.9x release. then i moved to 1.0 and now 1.02 perhaps i have some things left over from 0.9x dir structure.

it just seemed that on this go around, my units/win32 dir was much more populated than previous. maybe that is simply to do with the fact i didn't install the fpc source this time....and i have fewer other dirs. i pruned my tree just before installing 1.0.2 so there was a bunch of stuff that didn't come back afterwards.
no matter. everything builds when i type make, so that is a happy thing for me.

moose.

as a side note, why doesn't the fpc package put the PDF files in the doc dir? not that it matters, i thought it was odd to have them not in the doc dir.

you wrote 21 lines
At 23:39 07.12.2000, you wrote: >i updated by CVS lastnight the lazarus source. got the GTK exception as >reported by others. downloaded the new FPC(1.0.2) today. >just as a side note, i didn't download the FPC package complete with >source. i had some problems with compiling lazarus as a result. it was >complaining about not being able to find xmlcfg.pp and the other units >related to xmlcfg. xmlcfg is missed in 1.0.2, it's a "bug" of 1.0.2 >has the FPC dir structure changed a lot recently? it seems that this >installation 'looks' different. any comments? No, it didn't change that much. Which version did you use before? _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

mooseman

well, for the first time since i started playing with lazarus, i have been able to compile _and_ run it.

it looks good, but i am having severe redraw other painting artifacts.... also, am noting that the gtk performance on win32 leaves something to be desired. granted, i am running a dog slow pc, but it runs all my other software that i would benchmark it by....

i must say, however, that i am truly wow-ed by the looks...

i updated by CVS lastnight the lazarus source. got the GTK exception as reported by others. downloaded the new FPC(1.0.2) today. just as a side note, i didn't download the FPC package complete with source. i had some problems with compiling lazarus as a result. it was complaining about not being able to find xmlcfg.pp and the other units related to xmlcfg.

has the FPC dir structure changed a lot recently? it seems that this installation 'looks' different. any comments?

i downloaded the GTK dlls from the lazarus site last night. didn't go to the other link... should i?

what other things should i look at to a) eliminate the redraw and painting problems and b) improve performance??

one last thing, when i was watching the debug window scroll by with messages, i noticed tons of gtk function failures.

moose.

Reply by email

Marc Weustink
to Marco van de Voort: Using recent 1.0.3 compiler: - the includefile "freebsd" is not found, but that is…

+ From: Behalf Of
+
+ After these changes (and seeing each build compiling the LCL three
+ times ??!) lazarus compiles.

That's to solve a compiler problem. make compiles the LCL in fact 6 times. If I didn't add this, the compiler thinks a unit it just had compiled has to be compiled again. If you turn on some verbose messages, you would see the number of units it compiles each step reduces.

+ However when I run the binary I get:
+
+ LM_SCREENINIT called --> should go to GTKObject.Init
+ TODO: check this

Thats all you see ? This message was only a reminder for me that the following code maybe should go GTKObject.Init.

After that the IDE is created.

Marc

Reply by email

Marco van de Voort
to mooseman: well, for the first time since i started playing with lazarus, i have been able to…

Using recent 1.0.3 compiler:

- the includefile "freebsd" is not found, but that is logical. Fixed by adding the appropiate -Fi manually.
- propclassmap in propedit.pp doesn't account for two newer types (dyn-array and tinterfaceraw) Fixed by adding two NILs

After these changes (and seeing each build compiling the LCL three times ??!) lazarus compiles.

However when I run the binary I get:

LM_SCREENINIT called --> should go to GTKObject.Init TODO: check this

Marco van de Voort ( or )

Reply by email