Re: [MSEide-MSEgui-talk] MSE and XLib.

>> Why, for example for libc.so.6 (needed to compile fpc himself), fpc does not >> use libc-dev and the libc.so created ? > Good question, and I guess only the FPC compiler team can answer that. Huh, I did ask it (now 14 hours ago) but still nothing in fpc-mailing list. (as usual, when I ask

Re: [MSEide-MSEgui-talk] MSE and XLib.

Ooops, in previous mail, please read: libc-dev and his link libc.so. Fre;D -- View this message in context: http://mseide-msegui-talk.13964.n8.nabble.com/MSEide-MSEgui-talk-MSE-and-XLib-tp5p13.html Sent from the mseide-msegui-talk mailing list archive at Nabble.com.

Re: [MSEide-MSEgui-talk] MSE and XLib.

> I'll fork it and use initializedynlib() from msedynload which loads > dynamically. It will take a while... Excellent idea and or freedom, I can be patient. > BTW, the code is not buggy. As explained to Graeme, if, like they said, the right way is to use lib***-dev then there is a bug.

Re: [MSEide-MSEgui-talk] MSE and XLib.

On Monday 14 August 2017 15:26:17 Fred van Stappen wrote: > Hello Martin. > > > May I ask you why MSE and fpGUI use the buggy code of fpc/packages/x11 ? > > > At the end it is only Pascal headers for the libX11.so library, mse could > have his own x11 code. > I'll fork it and use

Re: [MSEide-MSEgui-talk] MSE and XLib.

On 2017-08-14 15:28, Fred van Stappen wrote: Why, for example for libc.so.6 (needed to compile fpc himself), fpc does not use libc-dev and the libc.so created ? Good question, and I guess only the FPC compiler team can answer that. But if true, it does sound a bit inconsistent (from their

Re: [MSEide-MSEgui-talk] MSE and XLib.

> Why, for example for libc.so.6 (needed to compile fpc himself), fpc does not > use libc-dev and the libc.so created ? Sory, I am hot, I cannot resist. For me, fpc act as very selfish. For himself and the libraries needed to compile himself ---> ok, the good soname is used. But for all

Re: [MSEide-MSEgui-talk] MSE and XLib.

Hello Graeme. Thank you to your answer but could you explain me why, if using lib**-dev **is** the way to do, why fpc does it only for third library. Why, for example for libc.so.6 (needed to compile fpc himself), fpc does not use libc-dev and the libc.so created ? I am very sorry but if

Re: [MSEide-MSEgui-talk] MSE and XLib.

On 2017-08-14 14:34, Fred van Stappen wrote: A Linux/FreeBSD fpc release was compiled using the pascal headers for libX11.so.6 and using symlink libX11.so >> libX11.so.6.0.8. Fred, as they tried to explain in the FPC mailing list, it is the way Unix-type systems have worked for decades. The

Re: [MSEide-MSEgui-talk] MSE and XLib.

Hello Martin You know that I never give up. A concrete example. A Linux/FreeBSD fpc release was compiled using the pascal headers for libX11.so.6 and using symlink libX11.so >> libX11.so.6.0.8. This release was installed on a system (with libX11-dev too to make it work). If, some time later,

[MSEide-MSEgui-talk] MSE and XLib.

Hello Martin. May I ask you why MSE and fpGUI use the buggy code of fpc/packages/x11 ? At the end it is only Pascal headers for the libX11.so library, mse could have his own x11 code. Fre;D

Re: [MSEide-MSEgui-talk] MSE on nabble.com ?

> http://mseide-msegui-talk.13964.n8.nabble.com mseide-msegui-talk | Mailing List Archive mseide-msegui-talk.13964.n8.nabble.com mseide-msegui-talk forum and mailing list archive. General list for the cross platform toolkit MSEide+MSEgui

Re: [MSEide-MSEgui-talk] MSE on nabble.com ?

On Sunday 13 August 2017 15:38:18 Fred van Stappen wrote: > Hello Martin. > > > What do you think to create a mse account on http://www.nabble.com ? > We already have https://www.mail-archive.com/mseide-msegui-talk@lists.sourceforge.net/ which also contains the messages from Berlios. > > You may

[MSEide-MSEgui-talk] Test

Test. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ mseide-msegui-talk mailing list