Re: [Lazarus] It is a beautiful day...
Am 20.07.2019 um 20:05 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 19:37:23 +0200 Werner Pamler via lazarus wrote: Am 20.07.2019 um 15:43 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 15:32:05 +0200 Werner Pamler via lazarus wrote: Am 20.07.2019 um 12:15 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 11:59:56 +0200 Werner Pamler via lazarus wrote: You could create a meta package and install that. Excuse my ignorance. , But what is a "meta package"? A package which only contains requirements of other packages? Yes When installing the new meta package "jvcl_all" which contains all designtime packages I get a message "The package jvcl_all does not have any "Register" procedure which typically means it does not provide any IDE addon. Installing it will probably only increase the size of the IDE and may even make it unstable." and I am prompted to either "Install it, I like the fat" or to "Cancel". How can I avoid this? Do I have to provide a dummy registration unit? It should not warn in this case. I fixed the bug. Thanks. It works correctly now. -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
On Sat, 20 Jul 2019 19:37:23 +0200 Werner Pamler via lazarus wrote: > Am 20.07.2019 um 15:43 schrieb Mattias Gaertner via lazarus: > > On Sat, 20 Jul 2019 15:32:05 +0200 > > Werner Pamler via lazarus wrote: > > > >> Am 20.07.2019 um 12:15 schrieb Mattias Gaertner via lazarus: > >>> On Sat, 20 Jul 2019 11:59:56 +0200 > >>> Werner Pamler via lazarus wrote: > >>> > >>> You could create a meta package and install that. > >> Excuse my ignorance. , But what is a "meta package"? A package > >> which only contains requirements of other packages? > > Yes > > When installing the new meta package "jvcl_all" which contains all > designtime packages I get a message > > "The package jvcl_all does not have any "Register" procedure which > typically means it does not provide any IDE addon. Installing it will > probably only increase the size of the IDE and may even make it > unstable." > > and I am prompted to either "Install it, I like the fat" or to > "Cancel". How can I avoid this? Do I have to provide a dummy > registration unit? It should not warn in this case. I fixed the bug. > What does it have to look like? Mattias -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
Am 20.07.2019 um 15:43 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 15:32:05 +0200 Werner Pamler via lazarus wrote: Am 20.07.2019 um 12:15 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 11:59:56 +0200 Werner Pamler via lazarus wrote: You could create a meta package and install that. Excuse my ignorance. , But what is a "meta package"? A package which only contains requirements of other packages? Yes When installing the new meta package "jvcl_all" which contains all designtime packages I get a message "The package jvcl_all does not have any "Register" procedure which typically means it does not provide any IDE addon. Installing it will probably only increase the size of the IDE and may even make it unstable." and I am prompted to either "Install it, I like the fat" or to "Cancel". How can I avoid this? Do I have to provide a dummy registration unit? What does it have to look like? -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
On Sat, 20 Jul 2019 15:32:05 +0200 Werner Pamler via lazarus wrote: > Am 20.07.2019 um 12:15 schrieb Mattias Gaertner via lazarus: > > On Sat, 20 Jul 2019 11:59:56 +0200 > > Werner Pamler via lazarus wrote: > > > > You could create a meta package and install that. > Excuse my ignorance. , But what is a "meta package"? A package which > only contains requirements of other packages? Yes Mattias -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
Am 20.07.2019 um 12:15 schrieb Mattias Gaertner via lazarus: On Sat, 20 Jul 2019 11:59:56 +0200 Werner Pamler via lazarus wrote: You could create a meta package and install that. Excuse my ignorance. , But what is a "meta package"? A package which only contains requirements of other packages? -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
On Sat, 20 Jul 2019, Mattias Gaertner via lazarus wrote: On Sat, 20 Jul 2019 11:59:56 +0200 Werner Pamler via lazarus wrote: Great news! There is one more thing which would be helpful, at least for me. I am maintaining the Lazarus port of JVCL, and this library currently consists of 16 runtime and designtime packages (i.e. 32 lpk files), and when porting proceeds there will be more to follow. As you an imagine, it is a pain to install them manually... I already set up a project group which can compile all the packages, but what is missing is a way to install them. I mean: Could there be a button "Install"? After clicking on this button a routine should iterate through all the items of the project group, find the design time packages, mark them for installation, and finally rebuild the IDE. Can this be done? You could create a meta package and install that. That is one way, but I think the 'install' option would of course also be nice to have. The program group is already there after all. Making a new file just for install purposes seems superfluous... Michael. -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
On Sat, 20 Jul 2019 11:59:56 +0200 Werner Pamler via lazarus wrote: > Great news! > > There is one more thing which would be helpful, at least for me. I am > maintaining the Lazarus port of JVCL, and this library currently > consists of 16 runtime and designtime packages (i.e. 32 lpk files), > and when porting proceeds there will be more to follow. As you an > imagine, it is a pain to install them manually... > > I already set up a project group which can compile all the packages, > but what is missing is a way to install them. I mean: Could there be > a button "Install"? After clicking on this button a routine should > iterate through all the items of the project group, find the design > time packages, mark them for installation, and finally rebuild the > IDE. Can this be done? You could create a meta package and install that. Mattias -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] It is a beautiful day...
Great news! There is one more thing which would be helpful, at least for me. I am maintaining the Lazarus port of JVCL, and this library currently consists of 16 runtime and designtime packages (i.e. 32 lpk files), and when porting proceeds there will be more to follow. As you an imagine, it is a pain to install them manually... I already set up a project group which can compile all the packages, but what is missing is a way to install them. I mean: Could there be a button "Install"? After clicking on this button a routine should iterate through all the items of the project group, find the design time packages, mark them for installation, and finally rebuild the IDE. Can this be done? Werner -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Adding Required Packages paths... dynamically
On Fri, 19 Jul 2019 00:26:49 -0300 "Marcos Douglas B. Santos via lazarus" wrote: > Hi, > > Imagine a package that has a dependency for another one. However, this > dependency has a conditional to exists. So, I cannot add the Required > Package by default — I'm talking about ZeosLib. > > Then, I used Conditionals (script) for adding ZeosLib paths (-Fu, -Fi) > into the paths of the package — amazing work in IDE, by the way. > > In Custom Options | Conditionals, I have something like this: > ===begin=== > if undefined(NOSYNDBZEOS) then > begin > UnitPath += > ';$PkgOutDir(zcore);$PkgOutDir(zdbc);$PkgOutDir(zparsesql);$PkgOutDir(zplain)'; > IncPath += ';$(ProjOutDir);$PkgDir(zcore)\..\..\src'; end; > ===end=== > > And it works. If user add the package into a project, he/she could > compile with/without support to ZeosLib, just checking/unchecking some > definition into Defines button. Excellent. > > However, my only problem occur if user add zcomponent package, which > belongs to ZeosLib. If so, I get some hints like this: > ``` > Note: Duplicate unit "ZVariant" in "mormot_base 1.18", orphaned ppu > "\zeos\packages\lazarus\lib\zcore\x86_64-win64\ZVariant.ppu" > Note: Duplicate unit "ZVariant" in "zcore 7.2.5", > ppu="\zeos\packages\lazarus\lib\zcore\x86_64-win64\ZVariant.ppu", > source="\zeos\src\core\ZVariant.pas" It means: Two packages reach the same ppu and only one has a source file. Hmm, that should not create a note. I fixed a check in rev61607, please test with trunk. > Note: Duplicate unit "ZVariables" in "mormot_base 1.18", orphaned ppu > "\zeos\packages\lazarus\lib\zcore\x86_64-win64\ZVariables.ppu" > Note: Duplicate unit "ZVariables" in "zcore 7.2.5", > ppu="\zeos\packages\lazarus\lib\zcore\x86_64-win64\ZVariables.ppu", > source="\zeos\src\core\ZVariables.pas" > ``` > > What I don't understand is: > Adding ZeosLib into mormot_base package as a dependency (just for > testing), I have the same paths as using Conditionals. Then, why the > compiler show me these hints when I'm using ZeosLib paths > "dynamically" by Conditionals? These notes come from Lazarus, not fpc. > What should I do to remove them? Mattias -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
