Re: [MSEide-MSEgui-talk] Out-of-the-box package with fpgui, msegui and mse-fpc included.
> Anyway it is extremely difficult to explain In short, according: http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html 3.1.1. Shared Library Names Every shared library has a special name called the ``soname''. The soname has the prefix ``lib'', the name of the library, the phrase ``.so'', followed by a period and a version number that is incremented whenever the interface changes (as a special exception, the lowest-level C libraries don't start with ``lib''). Every shared library also has a ``real name'', which is the filename containing the actual library code. The real name adds to the soname a period, a minor number, another period, and the release number. In addition, there's the name that the compiler uses when requesting a library, (I'll call it the ``linker name''), which is simply the soname without any version number. The linker ld can deal with "soname" (the most recommended), "real name'' (to link a particular number) and the "linker name" (for fast coding to point to the soname without number.) Sadly, for a obscure reason, fpc accept only the "linker name" and strip everything from the soname before to sent it to the linker ld. and makes impossible to link a "soname". -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] Out-of-the-box package with fpgui, msegui and mse-fpc included.
> _What_ "bug"? The bug is that fpc does not allow to link a library with soname with number. For example it is not possible to link libX11.so.6 when using "external". Fpc will strip the code into libX11.so, without the so number. You are obliged to create a symlink libX11.so that point to ink to libX11.so.6. The bug is not about using dev package (even if it should not be needed for fpc users). Anyway it is extremely difficult to explain it is why I did a fork from fpc and have fixed the bug. I think that in the world only Martin and I did understand the bug. Now I can install fpc and msegui on a RPi with Raspbian distro without the need to be connected to install some no needed dev-package. https://github.com/fredvs/freepascal Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] Out-of-the-box package with fpgui, msegui and mse-fpc included.
Hello fredvs, you wrote on Thu, 9 Apr 2020 03:57:16 -0700 (MST): > I am thinking to create a package for the Raspbian Pi that includes > msegui, fpgui and fpc binary. You mean, "for Raspbian (distribution) for the Raspberry Pi" (hardware)? Yes, that's certainly interesting, although it shouldn't be a specifically targeted package, but also available for all the other architectures supported. > The idea is to provide a package out of the box, that people can use > directly, without any need to install any dependencies. There are a couple questions to be regarded: - Is it _legal_ to combine these packages? - Is it at all possible to combine them without "any dependencies"? (And a corollary: Is it possible to do without causing interferences?) > Sadly for that the original fpc binary is not suited for that because it > needs to install some dev package. This would give the answer "no" to the second question above - if fpc _needs_ another package, it will probabely not work without it. Then there's the problem whether it's _legal_ to put the dependent package into your "super package", and what might happen when this is installed on a system that _needs_ a different version of this additional package. I think that's a bad idea, as it foregoes the reason for a package system in the first place, leaving the user with the same mess that was called "depandency hell" under the older Windows versions. > Sadly too fpc team is not in plan to fix this big bug, see: > https://bugs.freepascal.org/view.php?id=32367 _What_ "bug"? The additional dev package? If it's really needed, this is _not_ a bug but a requirement. If it's _not_ needed, of course, it should be removed, and won't be neccessary to include into a "super package". > So the proposition it that: > > - fork fpc and create /mse-org/msefpc and fix the bug. > - give binaries of that fixed fpc for Unix OS (Rpi, Linux, FreeBSD). > > What do you think? I'd rather suggest to create a _clean_ "mseide / msegui" package with inherent dependencies to whatever is needed to use it (probabely only fpc) and perhaps provide a link or a repository for an appropriate (current) fpc package, too. Raspbian is a Debian derivative, so it uses their "super capable" package manager that should be able to handle all neccessities to make the installed software useable. If you attempt to provide something beyond what this system is meant for, they much likely will ban you forever from use of any Debian system or component... No, keep it simple and adhere to the standards of the system you use. -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) --- Mit freundlichen Grüßen, S. Schicktanz --- ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] Out-of-the-box package with fpgui, msegui and mse-fpc included.
Hello Everybody. GTK, Qt and KDE have recently change their licenses, it is much more restrictive now. Maybe the opportunity for people to try other widgetset more open, like fpGUI or MSEgui... Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
[MSEide-MSEgui-talk] Out-of-the-box package with fpgui, msegui and mse-fpc included.
Hello everybody. I am thinking to create a package for the Raspbian Pi that includes msegui, fpgui and fpc binary. The idea is to provide a package out of the box, that people can use directly, without any need to install any dependencies. Sadly for that the original fpc binary is not suited for that because it needs to install some dev package. Sadly too fpc team is not in plan to fix this big bug, see: https://bugs.freepascal.org/view.php?id=32367 So the proposition it that: - fork fpc and create /mse-org/msefpc and fix the bug. - give binaries of that fixed fpc for Unix OS (Rpi, Linux, FreeBSD). What do you think? Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
