If FP/Lazarus had dynamic binary packages, the packages (like
laz-core, etc.) could be the only ones downloaded, and the user will
benefit from already compiled packages and not worrying about if it's
going to compile or not.. But of course the binary packages always runs
into the usual problems: It would have to be sorted on the server by
OS/Widget-Set, like Linux32+GTK+QT+Etc, Linux64+GTK+QT, Win32+Native+QT,
Win64+Native+QT, etc. Everytime there is a new release server-side it
would have to trigger a build of all of these.. The workaround for that
could be just defaulting to some Widget-Sets, like GTK2 for Linux, and
Native for Windows, etc. And if the user wants a different Widget-Set
they can use the Source and compile their own.
But of course this is assuming dynamic binary packages existed in FP. ;)
- Dennis
On 2015-04-13 10:41 AM, Michael Van Canneyt wrote:
On Mon, 13 Apr 2015, Graeme Geldenhuys wrote:
On 2015-04-13 14:58, Lukasz Sokol wrote:
Probably doable IFF one wants to, or can, run on SVN/GIT releases
and rebuild by themselves;
I would (and already do) go with this option. It would also download the
least about.
I'm pretty sure with 15 minutes to spare, somebody could write a Lazarus
add-on (package) that registers a new "Get Updates" menu item in say the
Help menu, which triggers a 'git stash; git pull; git stash pop' and
then finally triggers the IDE to rebuild.
This is not so difficult.
IMHO the problem is primarily: what happens if it goes wrong.
i.e. the compile fails somewhere halfway the LCL.
The IDE will continue to function, but you won't be able to compile
any apps.
Also, doing this requires a checkout. This will increase diskspace etc.
Lots of pitfalls.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
