On Tue, 10 May 2022 01:36:06 GMT, David Holmes wrote:
>> The way LauncherCommon.gmk is currently written, it's only meant to be
>> included from "make/module//Launcher.gmk", or at least only from one
>> single place for each module. This is because the man page generation that
>> happens in
On Mon, 9 May 2022 23:18:47 GMT, Erik Joelsson wrote:
> The way LauncherCommon.gmk is currently written, it's only meant to be
> included from "make/module//Launcher.gmk", or at least only from one
> single place for each module. This is because the man page generation that
> happens in
On Mon, 9 May 2022 23:18:47 GMT, Erik Joelsson wrote:
> The way LauncherCommon.gmk is currently written, it's only meant to be
> included from "make/module//Launcher.gmk", or at least only from one
> single place for each module. This is because the man page generation that
> happens in
On Mon, 9 May 2022 23:18:47 GMT, Erik Joelsson wrote:
> The way LauncherCommon.gmk is currently written, it's only meant to be
> included from "make/module//Launcher.gmk", or at least only from one
> single place for each module. This is because the man page generation that
> happens in
The way LauncherCommon.gmk is currently written, it's only meant to be included
from "make/module//Launcher.gmk", or at least only from one single
place for each module. This is because the man page generation that happens in
LauncherCommon.gmk is module global. For the jdk.jpackage module,
