Reaction score: 1,591
hi trev,To build a GUI helloworld vs a command line helloworld, you would normally install the Lazarus IDE which allows the use of the various widgets sets like GTK and QT.
I started a FreeBSD Portal on the FPC + Lazarus Wiki, though I have to confess that I've spent most of my time on the macOS Portal as FreeBSD is a road much less travelled.
They are both packages: editors/lazarus and editors/lazarus-qt5, if that's what you mean. You can also build them from ports with your own recipe.hi trev,
(you people are doing awesome work...)
My question is, can we have both lazarus and lazarus-qt5, because I would like to can build for GTK and Qt without the need to rebuild all the staff, but just to start the needed IDE. I saw that the pkgs differ by two archives (lazarus-qt5 adds more 2)? With other words can we have both in independent manner? Another question relating to that is, why the both variants are, is there some reason, for example the IDE for GTK on FreeBSD to can not be rebuild for Qt, and because of that is the need of the two variants?
Yes, mark_j, that's the question, they have to use different configurations: installation dir, config file... after the installation and I do not know is this taken in account to can do clear second installation of lazarus-qt5 (I am tried the IDE on Win, Mac, Lin and there the IDE has just one variant and on Win I am managed to have different versions with different fpc compiler versions to can experiment with the newest, and different cross-compilations). I will ask the maintainer to be sure for my intansion. Thanks.They are both packages: editors/lazarus and editors/lazarus-qt5, if that's what you mean. You can also build them from ports with your own recipe.
If you mean installing both and switching between the two, that is possible but I don't know how Lazarus accomplishes that. It "should" be as easy as selecting your build/interface/GUI library. I say, should.
That is the neat part. You decide. Lazarus is being developed to be totally and completely API independent. Once you write your code you just link it against the API widget set of your choice. If you want to use GTK+, great! If you want it to be Gnome compliant, great! As long as the interface code for the widget set you want to use is available you can link to it. If it isn't available, well you can write it.
Yes, trev, the recompilation time/delay I would like to avoid and also to be sure that lazarus-qt5 is not more than a Qt variant of the same lazarus (like lazarus(-gtk2)), which I could achieve by lazarus(-gtk2) recompilation with Qt widgetset.I think cobata knows it can be done - his issue is that Lazarus/FPC needs to recompile its units when he switches from one widgetset to another. I think he wants to avoid this recompilation time/delay.
This being the case, I think the solution might be to investigate using fpcupdeluxe to install and not using the FreeBSD ports system. Each fpcupdeluxe installation is sequestered in its own directory. I've never used it, but from what I've read it should do the trick. See: https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/tag/1.8.2t