Hi,

I just read the thread about 'libc' and that made me think. What are the supported platforms Lazarus runs on?

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

Graeme Geldenhuys wrote

I just read the thread about 'libc' and that made me think.

Which thread?

What are the supported platforms Lazarus runs on?

The IDE?

I think it's Windows (98 or superior), Unix (all supported by FPC)

Architectures: x86, x86_64, powerpc. May run on other hardware, but probably isn't much tested on them. Someone got it to run on sparc, but with some issues I think.

Felipe Monteiro de Carvalho wrote

Which thread?

Titled "the libc unit again" in the fpc-pascal mailing list. Talking about to many units requiring the libc unit, which isn't portable, so limits supported platforms.

The IDE?

Yes the IDE. So Lazarus runs on FreeBSD too.. Anybody using it on 64bit systems?

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

He is talking about my post in fpc-pascal ml.
I asked to mark the libc unit as obsolete because it set only for i386, but many users here use it anyway, although the Unix libraries have the same functions as well..

Ido

Graeme Geldenhuys wrote

Titled "the libc unit again" in the fpc-pascal mailing list. Talking about to many units requiring the libc unit, which isn't portable, so limits supported platforms.

I think he is talking about people that write 3rt party components for Lazarus, not Lazarus itself.

Lazarus should not contain any reference to libc.

I use it on a Linux 64 bit system (I also create things for 64 bit servers of Linux, so it's something really important for me).

Ido

Graeme Geldenhuys wrote / nap?sal(a):

Yes the IDE. So Lazarus runs on FreeBSD too.. Anybody using it on 64bit systems?

I use it on 64bit linux (with gtk2 no less). There's no FPC for 64bit FreeBSD.

AFAIK fpc doesn't run on x86_64-freebsd yet, due to problems with the startup code.

Vincent

ik wrote

I asked to mark the libc unit as obsolete because it set only for i386, but many users here use it anyway, although the Unix libraries have the same functions as well..

Well, not all of them! In the fpGUI project I use two libc functions for Linux which aren't available in the unixbase etc units. I did IFDEF that code, created an alternative for other platforms like FreeBSD and limited it to only one location in the code so as not to use it elsewhere.

But yes, libc can be misleading to a unknown developer. I fell in that trap in the beginning when I didn't know it was Linux and x86 specific.

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

Of course, every day :)

Michael.

Like? Note that the password stuff is now in both 2.2.1 and 2.3.x in the "users" package.

But yes, libc can be misleading to a unknown developer. I fell in that trap in the beginning when I didn't know it was Linux and x86 specific.

Maybe we should get it over with and add deprecated to all functions.

Marco van de Voort wrote

Like? Note that the password stuff is now in both 2.2.1 and 2.3.x in the "users" package.

getgrgid() - Used for getting the Group ID Name from the Group ID. getpwuid() - Used for getting the User Name from the User ID.

Both of these are used in a FileGrid component (eg: File Open Dialog) to display a files User and Group names like graemeg:users instead of 5000:3000

My work-around for FreeBSD is to display the numeric values only. I'm thinking of looking up the values manually in /etc/groups and /etc/passwd but was told it can be inaccurate.

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

Seems you did not read the answer I gave you on that issue:

But that would need ifdefs and libc, too. ;)

Have fun,
Marc

Yes these are in users. So if you have snapshots (both 2.2.1 and 2.3.1) of february or later, simply use units "grp" and "pwd". Also have a look at "users" where Michael stuffed some wrappers (though I don't particularly like them). The source is in fpc/packages/users/src

If you don't use recent snapshots, just get these units from the snapshot and use them with your current versions.

Don't forget to prefix the function names with "fp", as done in the entire RTL for libc primitives to escape naming conflicts.

My work-around for FreeBSD is to display the numeric values only. I'm thinking of looking up the values manually in /etc/groups and /etc/passwd but was told it can be inaccurate.

Depends who you make software for. If you make it for some embedded device that you fully control you can. If it is somehow for general customers compensation, don't. Sooner or later you'll run into places that have central authentication systems for lots of machines (and Stack is one of them which is why I revamped these units). There are even places that link them to Active Directory via LDAP.

Thanks for the info Marco. I only use FPC 2.2.0 but I'll have a look at those units.

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

Somehow you seem to circumvent hotmail's junk filtering ?

All mail goes to my junk folder by default except from people on my mailing list.

How is it possible that "marco van de voort" enters my inbox ?

(I once clicked on the key or something)

Bye,
Skybuck.

Skybuck Flying wrote

Somehow you seem to circumvent hotmail's junk filtering ?

Yes. I don't use Outlook mostly.

All mail goes to my junk folder by default except from people on my mailing list. How is it possible that "marco van de voort" enters my inbox ?

Logically, there is a flaw in your filtering.

(I once clicked on the key or something)

I don't have a key

Ok I think I solved the problem.

Somehow general mailing list ended up in my address book.

Hopefully now it's gone.

Bye,
Skybuck.