Using the Trunk branches for FPC/LAZARUS. lazarus / 21-General ---------------------------------------------------------------------- BSaidus · 2023-06-24 08:30 Hello, I wonder about the usability of the trunk branch of fpc/lazarus. I mean, What are the kind of problems I can encounter while using in production environment. Say I need to use FPC/Lazarus for an application running on AARCH64-freebsd, Might I use it safely. What recommendation for it and what problems can we experiment?? Thank you. ---------------------------------------------------------------------- TRon · 2023-06-24 08:50 @BSaidus: Getting trunk for both FPC and Lazarus to play nice together can sometimes be problematic. But if you want to experiment then you can do so by installing both next to your existing FPC and Lazarus installations (that is when on Linux you have not used your distribution's package manager to install FPC/Lazarus) The most issues you come across is that if you update trunk every day (or a couple of times per day) the risk that something breaks is quite high as you are running bleeding edge it can be a commit is done that influences other code or sometimes a mistake in trunk is made (and you would have to wait for a correction unless you know how to use git to ignore certain commits). If you try and install both FPC and Lazarus from trunk and they work for you then remember the revision numbers so that you can revert to a (more or less) stable environment. It might perhaps sound scary but in reality it really isn't. Once in a blue moon I install trunk FPC and Lazarus and try some new features. Usually that is stable enough to get work done. If you use experimental features then you can get yourself into issues. For example the generics implementation still requires some work so it might be you run into errors when using such a newly introduced feature. Or for example the debugger support has had a lot of work done lately (and not everything is tested/checked yet). Just make sure to not mix your (especially lazarus) projects between versions at least not without making a proper backup of your project so that you are able to revert in case something went wrong (especially with project configuration settings as trunk might introduce things that the older version of Lazarus might not quite understand, or vice verse). edit: In case your only (current) objective is to compile for a pltform that is not (yet) supported by the official release versions of FPC and Lazarus and you are talking about real production (livelihood) then I would suggest to keep on using the official releases for FPC and Lazarus for actual development, do a separate install for trunk FPC and Lazarus (that both run completely stand-alone), and only use the trunk versions for building your project for the newly introduced target (and do that with a back-up of your development version of the project). ---------------------------------------------------------------------- BSaidus · 2023-06-24 12:26 Quote from: TRon on June 24, 2023, 10:50:39 amedit: In case your only (current) objective is to compile for a pltform that is not (yet) supported by the official release versions of FPC and Lazarus and you are talking about real production (livelihood) then I would suggest to keep on using the official releases for FPC and Lazarus for actual development, do a separate install for trunk FPC and Lazarus (that both run completely stand-alone), and only use the trunk versions for building your project for the newly introduced target (and do that with a back-up of your development version of the project). Thats what I did indeed thank you @TRon