Hi
Is there a possible port of fpc to beos ?
thx

you wrote

Hi Is there a possible port of fpc to beos ?

There is a start of a BeOS port already available in the daily sources.

Peter

If you go to http://befpc.sourceforge.net you can download a working binary distrabution.

Soon there should also be a GUI binging available.

Matt

So, are there two versions of Be-FPC? Because there is one at the CVS, common to all platforms and having the latest updates, and another at sourceforge, specific to FPC but probably out of sync with all the other versions. I do not know if it is the best solution. Will you unify them?

Best regards

Ramon Bosque

So, are there two versions of Be-FPC? Because there is one at the CVS, common to all platforms and having the latest updates, and another at sourceforge, specific to FPC but probably out of sync with all the other versions. I do not know if it is the best solution. Will you unify them?

The one in CVS is based on the other one, but it is still being tested and merged AFAIK.

Carl never replied.. I have no idea how he's getting on. It would be nice to hear from him.

The CVS version I put up works. The Official FPC CVS version didn't compile when I last tried it. I'll give it a go at some point.

My version is based almost entirely on the one submitted by Pascal K., Pixel32 developer. At the moment it's kind of more importand to me to have a compiling set of source with which to work with. I'm sure the official FPC BeOS port will be more satisfactory.

There's a binary distro available from the sourceforge page. It compiles, and compiles itself also, so with it you can rebuild the CVS source. It also contains a really experimental binding to a BeOS GUI application. I'm going to work in ernest on this for the next two weeks - I should have time in the evenings.

Matt

So, are there two versions of Be-FPC? Because there is one at the CVS, common to all platforms and having the latest updates, and another at sourceforge, specific to FPC but probably out of sync with all the other versions. I do not know if it is the best solution. Will you unify them?

The sourceforge version currently works, The FPC version is not (as far as I know.) The sourceforge version will eventually merge, or be 'overtaken' by the official port. I'm just waiting to actually *see* a working version. No one in the FPC camp, bar Carl is working on it afaik, and no one seems all that interested in it.

Matt

This is not the case; the problem is that no-one of the core developers has BeOS installed; it's hard to work on a BeOS port then.

Currently carl is also working on a m68k port; The compiler and the IDE run on a m68k-linux box; I suspect that when that is finished, the POSIX (and hence BeOS) port will be continued.

Many members of the core team have day-time jobs; FPC is worked on whenever possible, so patience please...

Michael.

Quoting Michael Van Canneyt :

This is not the case; the problem is that no-one of the core developers has BeOS installed; it's hard to work on a BeOS port then.

I've already offered to burn you all a copy of BeOS R5 PE and include all of the additional tools that you'll need on the CDR. I'll do it for the cost of postage.. about £1.

Currently carl is also working on a m68k port; The compiler and the IDE run on a m68k-linux box; I suspect that when that is finished, the POSIX (and hence BeOS) port will be continued.

Fair enough, but it still seems to be on the 'back burner'. I'm trying to get something concrete done. It would be nice for Carl to reply to the email I sent him however, even if it's a 'I'll get back to you'.

I'll take another look at the FPC source this weekend. I don't want to waste too much time on it at the moment, because I'm more interested in getting the BeCL, stage 1 working.

Many members of the core team have day-time jobs; FPC is worked on whenever possible, so patience please...

I work a 40 hour week, have a pregnant wife, and 2 cats to feed. Believe me, I have little time myself.

Matt

The problem is not to obtain BeOS; The problem is (e.g. in my case) that the hard disk is already filled with 5 OSes: DOS/Win95/WinNT/ Linux/Solaris. Putting a sixth means again resizing, reinstalling some others.

Carl has little time; I suspect it has slipped through; In any case, we want to release 1.0.6 ASAP, and we are trying to include a BeOS and Solaris port.

Then you'll perfectly understand that there are sometimes delays ;)

As far as I understand it Carl will shift his priorities from the m68k Linux port (Pierre Muller has done some excellent work there) to the BeOS and Solaris port, so probably you'll notice some advances in the coming days/weeks.

Michael.

Quoting

The problem is not to obtain BeOS; The problem is (e.g. in my case) that the hard disk is already filled with 5 OSes: DOS/Win95/WinNT/ Linux/Solaris. Putting a sixth means again resizing, reinstalling some others.

You don't need to repartition your drive. BeOS PE installs to a 500mb virtual partition on your windows drive. You can then boot either from a boot disk or by using the included launcher (which will only work with Win95/98, not NT/2000.) It performs perfectly well in this situation. You'll not notice a performance only real issue is hardware support.

Carl has little time; I suspect it has slipped through; In any case, we want to release 1.0.6 ASAP, and we are trying to include a BeOS and Solaris port.

Cool ;-) I'm not really a compiler person. I'm interested in the creation of the GUI bindings however.

Then you'll perfectly understand that there are sometimes delays ;)

Fair play ;-)

As far as I understand it Carl will shift his priorities from the m68k Linux port (Pierre Muller has done some excellent work there) to the BeOS and Solaris port, so probably you'll notice some advances in the coming days/weeks.

Please don't think I don't appreciate all the work you guys do. Sometime it does feel like you've taken too much work on, however. It's a real shame more people don't take the time to try to help out with the compiler/rtl more.

Matt

Also the help for the classes lib is really needed. Both compability testing as new implementations.

The core team is increasingly totally occupied by working on the core compiler and RTL. The things beside that (FCL, packages etc) are closing the point that they are suffering from that. Stasis is detoriation in the computer world :-)