1
Databases / Re: Step-into the field setter
« Last post by ginoo on Today at 07:50:24 am »thanks @Martin_fr
The proper way to initialize a record is to name each field:Thank you,Problem solved.
const efi_loaded_image_protocol_guid:efi_guid=(data1: $5B1B31A1; data2:$9562; data3: $11D2; data4: ($8E,$3F,$00,$A0,$C9,$69,$72,$3B));
A nice shortcut if you use instead the inbuilt TGuid is that you can write:
const efi_loaded_image_protocol_guid: TGuid = '{5B1B31A1-9562-11D2-8E3F-00A0C969723B}';
Even within Linux, different binary install models are more or less compulsory. End users who want a binary install expect the familiar install model for their platform. Deb users want a deb, rpm users want an rpm, packman....^^ Exactly that ^^ ergo +1
One single look and feel installer would be unfamiliar to every possible user. Its like saying we can make a car that runs on water, or a boat that runs on land, possible and has been done. But in both cases, they do a terrible job at everything !
....Sorry, thats plain silly.
Right now it's plain impossible to install official Lazarus releases on most Linux environments, unless you're using FPCUPDLX.
Again, it is exactly the same for Apple Silicon native macOS installations -I don't have Apple Silicon hardware but have no problem building Lazarus on a intel based Mac and cross compiling.
I honestly can't see the harm in having a consistent installation process, with official support for AMD64 and aarch64 targets on both Linux and macOS. It'll only serve to make Lazarus more accessible for greater adoption. With Delphi just at #11 on this year's Tiobe index, the timing is really perfect for an upgrade of the installation (and by implication, the user experience).
...
Help me understand how this is a bad thing?