Launchers are only built when CHPL_LAUNCHER is set to (or inferred to be)
a value. Since we haven't done any portals4 work, we haven't explicitly
put in any effort to support a launcher for that configuration (either in
the sense of inferring what the value should be or in the sense of
creating a launcher if none of the existing ones are applicable).
See doc/[release/]README.launcher for the currently-supported launcher
configurations in the release or [git tree]. In most cases, if a new
GASNet launcher is required, it can be kicked off easily by cloning
another GASNet launcher option.
Note that once you set CHPL_LAUNCHER, you'll have to re-build both the
runtime ('make runtime' from $CHPL_HOME) and re-compile your program.
-Brad
On Tue, 5 Aug 2014, Majeti, Deepak wrote:
> Hi,
>
> When I compile a Chapel program on top of GASNet + portals 4, it does not
> generate the launcher binary.
> How do I build the launcher ?
> Thanks!
>
> --
> Regards,
> Deepak Majeti
>
>
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
