Re: [MSEide-MSEgui-talk] MSEgui and CPU ARM AARCH64.
Hello Sieghard, hello Graeme. Thanks for your lights. Yes, I am excited to try FreeBSD on the Rpi aarch64. But ... there is no fpc target for FreeBSD-aarch64. About the problems with openfile() from clib, it is fixed now, and gives a valid handle. But there is problem also now with fstat(handle, _stat) from clib, it always give a -1 result (in place of 0). I have added the _stat table for aarch64 (taken from fpc 3.2.0 aarch64) and use this one but without success, the result is always -1. Sadly I am blocked, same result using stat(filename, _stat), I dont see what is wrong. > Maybe it's time to use more FPC standard methods for > opening/reading/writing/savingdata. I totally agree with Graeme about the mse-open/write/stat access to files and data. Martin wanted to be totally independent from sysutils and threads of fpc, it is ok, but in fact it limits mse. For my mse applications, I use now the standard fpc methods and all works like charms for the mse GUI widgets. But mseide himself only uses the mse build-in methods and it is very difficult to adapt it when a new release of fpc appears or a new OS target. The positive is that it is absolutely possible to compile and run mse applications for linux-aarch64. But at the moment, for access files and data, better use the standard fpc methods. Happy, creative, different, sane, safe new year. 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] MSEgui and CPU ARM AARCH64.
Hello fredvs, you wrote on Mon, 21 Dec 2020 16:48:11 -0700 (MST): > About Raspian 64 bit and aarch64 and fpc and msegui. > After big fight I finally have a stable Raspian 64 bit on my Rpi 3. Oh, fine, that'sa big advance then. > About fpc aarch64 linux. > Ok, it works and is easy to install. And this is another one. > About msegui on aarch64 linux. > After looong days and looong nights of hard exploration and tweak, nearly > all works. > Graphics, muti-threads and widgets are all ok. So after the preconditions above were met, you were able to get it running? Great. Sorry I didn't respond - I don't even have a fully running series 3 Raspberry available, what I have is just a loaner from a company I work for, to be used for a specific, although hardly moving, project. And I don't have a suffcient supply of SD cards - just 2 of them, and I already (mis)used one for testing an alternative Linux distribution. In addition, I had the impression that the Raspberry 3 was still restricted to 32 bit, but I learned that it has a Cortex A53 CPU, which should be 64 bit capable. > But there is something that I still cannot manage. > > It is once again with the msestat files. > It refuses to work, there is something that I dont catch. > > It has something to do with 'openfile' from clib that is not working (but > ok with cpu arm 32). Interesting, if opening files wouldn't work, there should be many more issues elsewhere, shouldn't they? So, how sure is this the origin of the trouble? Or could it be only a minute moment after, when the file's data are about to be processed, what is to be a process dependent heavily on dynamic memory, and thus pointer manipulations? As far as I recall, there were some problems with pointers also with the transition from 32 to 64 bit an the "intel" PC version of mseide-msegui, which then prompted Martin even to introduce a new type for some internal object field. Sadly, right now, I cannot remember what it was, it was discussed on the list then. Maybe you hit a similar issue again now? > All that said, happy new year without masks. Thanks, same to you, et joyeux noël! And take care of your health. (Unfortunatly, without masks only inside, at home, here abouts...) -- -- (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] MSEgui and CPU ARM AARCH64.
On 21/12/2020 11:48 pm, fredvs wrote: > I will surely take a look, thanks to note it. No problems. I've been looking into getting a new RPi 4 myself, for a similar goal. Testing fpGUI with AArch64. As I much prefer FreeBSD over Linux, I've been keeping an eye (or ear) on what others were saying about RPi + FreeBSD. It seems to be in a good state. > It has something to do with 'openfile' from clib that is not working (but ok > with cpu arm 32). Maybe it's time to use more FPC standard methods for opening/reading/writing/saving data. I've never really understood why Martin diverted from standard FPC feature or units. They always seems to be a cause of issues and extra effort. > All that said, happy new year without masks. That would indeed be a dream come true, but I'm afraid I don't see that in our near future. The UK has just gone into total lockdown again. :-( Regards, Graeme -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
