I have often hit problems with the limit of command line lengths many shells
have (CMD.EXE in Windows in my case).
This is a common case with few solutions, I have searched around:
http://www.makelinux.net/make3/make3-CHP-5-SECT-6
I would like to propose a couple new functions in make that can h
Paul,
What is the process to complete the discussion about the addition of this
functionality to make?
I would like to see it (I like the suggestions proposed in the thread). It
would help me greatly and it should not force anyone to change their current
makefiles, it is just an extension for
nt of the fopen
interface. Your ideas on how to do this will be the best approach, surely.
-- Lawrence
> -Original Message-
> From: Paul Smith [mailto:psm...@gnu.org]
> Sent: Wednesday, October 12, 2011 8:17 AM
> To: Lawrence Ibarria
> Cc: 'David Boyce'; Tim
Does it still happen if you do a clean first?
-- Lawrence
> -Original Message-
> From: bug-make-bounces+libarria=nvidia@gnu.org [mailto:bug-make-
> bounces+libarria=nvidia@gnu.org] On Behalf Of david.hag...@gmail.com
> Sent: Wednesday, November 16, 2011 1:41 PM
> To: psm...@gnu
There is a rule to make the missing .so file, or it is a byproduct of a
different target?
-- Lawrence
> -Original Message-
> From: bug-make-bounces+libarria=nvidia@gnu.org [mailto:bug-make-
> bounces+libarria=nvidia@gnu.org] On Behalf Of David Hagood
> Sent: Wednesday, Novembe
This is a rather simple path that implements a very simplified version of what
Tim suggested in his message of Sept 25th
(https://lists.gnu.org/archive/html/bug-make/2011-09/msg00044.html ).
Paul, what do you think? I'd rather not try to do everything, just focus on one
thing. I am not sure how
That message is to be expected. RM is simply informing you that there is no
file that conforms to '*~'.
Do man rm to figure out a way to prevent this warning from appearing.
-- Lawrence
From: bug-make-bounces+libarria=nvidia@gnu.org
[mailto:bug-make-bounces+libarria=nvidia@gnu.org] On
I do like this suggestion, feels quite clean!
-- Lawrence
> -Original Message-
> From: Paul Smith [mailto:psm...@gnu.org]
> Sent: Monday, January 16, 2012 5:15 AM
> To: Lawrence Ibarria
> Cc: bug-make@gnu.org; Tim Murphy (tnmur...@gmail.com)
> Subject: Re: &
This looks like work for your code generator instead of make. The code
generator could do a diff before replacing the file.
Make would have to keep a backup copy of the last time it built with that file,
increasing complexity and time for normal builds.
I'd recommend against this.
-- Lawrence
I like this idea quite a bit.
I see this as still work in progress to define what type of functions the
plugins can have.
Maybe they can even create or change make variables.
In the case of variable_buffer_output, I'd suggest that each plugin has an
'initialization function'. This is a hands
10 matches
Mail list logo
