On 31 March 2016 at 22:35, Mattias Gaertner
wrote:
> On Thu, 31 Mar 2016 22:17:20 +0100
> "vfclists ." wrote:
>
> >[...]
> > I suppose that this depends on using building a project with the right
> > widgetset? My thoughts where more along the line of using the Compile
> > button on the package
On Thu, 31 Mar 2016 22:17:20 +0100
"vfclists ." wrote:
>[...]
> I suppose that this depends on using building a project with the right
> widgetset? My thoughts where more along the line of using the Compile
> button on the package to compile for all the chosen widgetsets in one go.
With "chosen"
On 31 March 2016 at 21:49, Mattias Gaertner
wrote:
> On Thu, 31 Mar 2016 21:38:46 +0100
> "vfclists ." wrote:
>
> > Is there some way to build a package for all widgsets in one go like the
> > IDE's Build Many option?
> >
> > Changing widgetsets results in a recompile of a lot of GUI packages an
On Thu, 31 Mar 2016 21:38:46 +0100
"vfclists ." wrote:
> Is there some way to build a package for all widgsets in one go like the
> IDE's Build Many option?
>
> Changing widgetsets results in a recompile of a lot of GUI packages and
> wonder whether that can be avoided. Adding the LCLWidget to t
Is there some way to build a package for all widgsets in one go like the
IDE's Build Many option?
Changing widgetsets results in a recompile of a lot of GUI packages and
wonder whether that can be avoided. Adding the LCLWidget to the output path
of packages doesn't seem to work.
The only way I ca
On 31.03.2016 22:38, vfclists . wrote:
Is there some way to build a package for all widgsets in one go like
the IDE's Build Many option?
Changing widgetsets results in a recompile of a lot of GUI packages
and wonder whether that can be avoided. Adding the LCLWidget to the
output path of pac
