Get the IDE working under windows: weeks/months because of lack of developers.
You can already write some win32 applications using the LCL.

Mattias

Hello,

Can anybody tell some approximation about the effort for fixing things so lazarus and sw developed in lazarus can work on win32? Currently even lazarus is not working.

Is that a matter of hours / days / weeks?

Pista

Ok, maybe I can take a look at this event propagation stuff...

Could you please give me a short overview where should I look for? (If you have no idea just say that; I just want to avoid understanding unnecessary parts of the code.

Pista

What _is_ the easiest app for this? The examples dir examples are all 700- 1 MB each. I ask this because I'll have to debug NetBSD Lazarus.

I tried to smartlink lazarus, but LD can't handle it: Linking ./lazarus
./lcl/units/libpgrids.a: could not read symbols: Memory exhausted lazarus.pp(326) Error: Error while linking
Closing script ./ppas.sh
gmake[1]: *** [lazarus] Error 1

Probably there are simply too many symbols. It is not even "close", since it is exhausted at the 80th .a, while there are about 250 .a's in the link.res of Lazarus, and at that point it already eats up my 512 MB ram.

bash-2.05b# ld --version
GNU ld version 2.12.1 [FreeBSD] 2002-07-20
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty.

The examples can be smartlinked though, and then are typically 760-1060 kb (testall is larger) (normal size is 1-1.3 MB, so smartlinking shaves off about 33%) Linker eats between 100-120 MB and 150 MB (edittest and testall)

My guess would be days.
Lazarus essentially runs but non-interactive, i.e. it doesn't react on user events, I have the impression. This needs to be fixed, and then it should essentially be ready for use.

Michael.

They are simple in terms of code/functionality , not in terms of program size...

And that the smartlinking eats memory can only be solved by having an internal FPC linker, IMO.

Michael.

For instance:
- Check what happens if a menu is selected. (for menu)
- Check what happens when a key is pressed. (for example for synedit)

Michael.

This is what I meant in my other mail: User events are not communicated. I think that if this can be fixed, there should not be a problem in getting Lazarus to work. That's why I don't think it will be 'weeks' or 'months'.

(of course, after that there will probably be a lot of debugging necessary, but essentially, lazarus should work)

The best way I think is to see why the simple apps don't work (you can use the insight debugger that comes with cygwin for this) and fix that. After that Lazarus will probably function as well.

Michael.

You can already write some win32 applications using the LCL.

No I can't. Even very simple applications do not work.

On linux I did a little application: one button, one edit field, and by pressing the button the edit field is filled with something. On linux this works, but if I compile it under win32 from command line, it does not work. Seems like the button press event is not propagated to the appropriate method.

Other problem on win32: The size of the form when I start the application is totally random. The preset defaults do not seem to be used.

Pista