Re: Conditional recipe execution

2015-01-31 Thread SF Markus Elfring
> But a quick check of your link above shows no comments or anything > in the makefile describing what it does, Thanks for your look at my example. > and I don't really understand the purpose behind all these recipes > which consist of if-statements where the body of the recipe is made empty > i

Re: Conditional recipe execution

2015-01-24 Thread SF Markus Elfring
>> I hoped somehow that another level of data indirection could be avoided. > > To be honest, based on what I've seen, you could do with a few more > levels of indirection. My knowledge around GNU make usage is evolving. > The rules you've presented here are (to me) almost impossible to read.

Re: Conditional recipe execution

2015-01-23 Thread Paul Smith
On Fri, 2015-01-23 at 23:17 +0100, SF Markus Elfring wrote: > >> I find that a backslash would not be needed at this place if would like to > >> keep the "RM command" on a separate logical line. > > > > It is definitely needed. As I've said, it is not possible for a single > > variable or functio

Re: Conditional recipe execution

2015-01-23 Thread SF Markus Elfring
> It appears that KDevelop's "makefile" editing mode doesn't properly > handle backslash continuations. This tool might still have got few open issues around improved handling of the make file syntax. But I find that its visual feedback was appropriate for parentheses pairs at least. >> Do you r

Re: Conditional recipe execution

2015-01-23 Thread Paul Smith
On Fri, 2015-01-23 at 22:24 +0100, SF Markus Elfring wrote: > > it means that the open parenthesis that it didn't match was the > > "info" function on line 95. > > I find this detail hard to believe. > > I hope that the current KDevelop editor does not misguide me. The parentheses > pairs are fou

Re: Conditional recipe execution

2015-01-23 Thread SF Markus Elfring
> The error doesn't mean that the closing parentheses is missing from line 95, I understand this information part. > it means that the open parenthesis that it didn't match was the > "info" function on line 95. I find this detail hard to believe. I hope that the current KDevelop editor does no

Re: Conditional recipe execution

2015-01-23 Thread Paul Smith
On Fri, 2015-01-23 at 21:56 +0100, SF Markus Elfring wrote: > >> parallel-inc.make:95: *** unterminated call to function 'info': > missing ')'. Stop. > > > > I think the message is pretty clear: you're missing the end parenthesis > > ")" to the info function which starts at line 95: > > I read m

Re: Conditional recipe execution

2015-01-23 Thread SF Markus Elfring
>> parallel-inc.make:95: *** unterminated call to function 'info': missing ')'. >> Stop. > > I think the message is pretty clear: you're missing the end parenthesis > ")" to the info function which starts at line 95: I read my make rule in the way that the closing parentheses is really not on t

Re: Conditional recipe execution

2015-01-23 Thread Paul Smith
On Fri, 2015-01-23 at 20:38 +0100, SF Markus Elfring wrote: > > You need to describe your situation. Use words, but with detail. > > I have adjusted my build scripts. Now I wonder about another > error message for a recipe. > > parallel-inc.make:95: *** unterminated call to function 'info': miss

Re: Conditional recipe execution

2015-01-23 Thread SF Markus Elfring
> You need to describe your situation. Use words, but with detail. I have adjusted my build scripts. Now I wonder about another error message for a recipe. parallel-inc.make:95: *** unterminated call to function 'info': missing ')'. Stop. Corresponding excerpt Lines 91 - 101: … $(RESULT_FUNC

Re: Conditional recipe execution

2015-01-18 Thread SF Markus Elfring
>> Would use cases around the standard command "split" be concrete enough >> for further clarification? >> https://en.wikipedia.org/wiki/Split_%28Unix%29 > > No. I am bit surprised that you find such a tool as an unclear example at the moment. I am using my Python script which I developed as a c

Re: Conditional recipe execution

2015-01-18 Thread Paul Smith
On Mon, 2015-01-19 at 00:08 +0100, SF Markus Elfring wrote: > >> * I need to split an input file into several smaller files. > > > > I don't see any way that $(eval ...) is needed or helpful for any of > > those things. > > Can a make variable be set by this function within a recipe? Yes, I've a

Re: Conditional recipe execution

2015-01-18 Thread SF Markus Elfring
>> * I need to split an input file into several smaller files. > > I don't see any way that $(eval ...) is needed or helpful for any of > those things. Can a make variable be set by this function within a recipe? >> I imagine that conditional evaluation of recipes will be possible somehow, >> w