On 08/01/2018 13:58, Caspar van Leeuwen wrote:
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to run without it - thus it has no place
in a Bar
On 08/01/2018 14:09, Mikael Öhman wrote:
Alans answer is probably the best, but
`BAR_BIN`: '`which bar`'
might work as an alternativ to the Tcl specific hack (untested).
This won't work: `which bar` has no meaning in a module file (which is
not a shell script).
K.
On Mon, Jan 8, 2018
On 08/01/2018 15:07, Åke Sandgren wrote:
On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to
On Mon, Jan 8, 2018 at 3:07 PM, Åke Sandgren
wrote:
>
>
> On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
> > I disagree, because the requirement that the variable 'BAR_BIN' that is
> set is a requirement from Foo, not a 'feature' from Bar. Bar knows
> absolutely
On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
> I disagree, because the requirement that the variable 'BAR_BIN' that is set
> is a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely
> nothing about this variable, and is very happy to run without it - thus it
> has no
Alans answer is probably the best, but
`BAR_BIN`: '`which bar`'
might work as an alternativ to the Tcl specific hack (untested).
On Mon, Jan 8, 2018 at 2:01 PM, Alan O'Cais wrote:
> Hi Caspar,
>
> You can use
> modextravars = { 'BAR_BIN': '%(installdir)s/bin'}
> in the
Hi Caspar,
You can use
modextravars = { 'BAR_BIN': '%(installdir)s/bin'}
in the Bar easyconfig. If Bar is a dep of Foo, then when Foo is loaded Bar
will be too and the value will be set. If you *only *want this to be set if
Foo is loaded then that is custom behaviour and you will need to write a
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to run without it - thus it has no place
in a Bar module. To illustrate that more: what if someone
I'm sorry, maybe I should have clarified: Foo requires BAR_BIN to be present at
runtime , so yes, I really do want it to be set in the module file of Foo. Foo
provides a (GUI) wrapper for Bar, but it needs to know the location of the Bar
binary. Rather than searching the path - as other
I think you are misunderstanding the scope of modextravars, it is there to set
additional variables in the resultant module file from the installation (it is
not relevant to the install process of the software, only the final module file
that is written). The modextravars should be set in the
10 matches
Mail list logo