makefile question - foo.c := DUMMY=foo 
Author Message
 makefile question - foo.c := DUMMY=foo


Quote:

>Makefile question (about simply expanded variables?):

Hey stupid!

The make utility and makefiles aren't part of the C language. Try
comp.unix.programer instead.

--
Sincerely Yours,

The Scratch Monkey



Mon, 15 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo


Quote:


> >Makefile question (about simply expanded variables?):

> Hey stupid!

> The make utility and makefiles aren't part of the C language. Try
> comp.unix.programer instead.

> --
> Sincerely Yours,

> The Scratch Monkey

You're free to post what you like, of course, but don't you think it might
be possible to be a little more friendly in your redirections? Posting a
question about make, in comp.lang.c, may be off-topic but the association
of make and C is strong enough that (IMHO) the word 'stupid' doesn't really
apply here.

To the OP: he's right, I'm afraid - the make utility is off-topic here. But

'm's in 'programmer'.

--
Richard Heathfield

The bug stops here.



Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo
WHAT DOES "IMHO" mean?


Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo

Quote:

> WHAT DOES "IMHO" mean?

It means turn off your caps lock key, in my humble opinion.

--




Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo
: Makefile question (about simply expanded variables?):

: Similar code appears in a makefile that I received:

: --------------------
: foo.c := DUMMY=foo
: baa.c := DUMMY=ba1

: .c.o:
:         echo $(DUMMY)
: ---------------------
: Presumably the original makefile authors were getting
: something other than spaces echoed when running
:    gnumake foo.o
: or
:    make foo.o

: I just get spaces.  I'm thinking that this
: might be an old gnumake or make feature.

I've never seen or heard of a makefile which contains a ':=', and
I've dealt with a fair number of makes.  By no means all, however,
so it could be some specialised gnu feature.  Your best bet would
be to ask in a group related to the system on which the makefile
was written.  Or edit the makefile to do what you want.

Will



Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo
Mvalen72 schrieb:

Quote:

> WHAT DOES "IMHO" mean?

IMHO : In My Humble Opinion
IMO  : In My Opinion
OTOH : On The Other Hand
BTW  : By The Way
IIRC : If I Remember Correctly
FCOL : For Crying Out Loud
IOW  : In Other Words
HTH  : Hope That Helps
FWIW : For What It's Worth
(there are many many more)

DLTTSM : Don't Listen To The Scratch Monkey
a strange acronym posted by Dann Corbit : he makes them up as he
                                          goes along ;-)

Stephan
(initiator of the campaign against grumpiness in c.l.c)
(-: A new excellent FAQ version has been released !!!      :-)
(-: Get it: http://www.eskimo.com/~scs/C-faq/versions.html :-)



Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo
Scratch Monkey schrieb:

Quote:



> >Makefile question (about simply expanded variables?):

> Hey stupid!

Another remarkable posting by the courtesy off ...

Quote:
> Sincerely Yours,

> The Scratch Monkey

Aparently there's a piece of land for sale in Utah. With a well. Maybe you
can entertain the owner. He's been told to sit at the bottom of the well.

(Confirmation: Yes, i strongly dislike your attitude towards and choice of
words in posting to comp.lang.c)

Stephan
(initiator of the campaign against grumpiness in c.l.c)
(-: A new excellent FAQ version has been released !!!      :-)
(-: Get it: http://www.eskimo.com/~scs/C-faq/versions.html :-)



Tue, 16 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo

Quote:


> > And the ever popular:

> > YMMV : Your Mileage May Vary

> Plus

> RTFM: Read The F*cking Manual

> and its close relative

> STFW: Search The F*cking Web

> I particularly like the second one... :)

Sunil, the anti-grumpy faction has taken to changing the two above via
s/F\*cking/Fine/
This is probably better for public discussion, although it does seem to lose the
savour of the original.

--




Wed, 17 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo


Quote:

> > RTFM: Read The F*cking Manual
> > and its close relative
> > STFW: Search The F*cking Web
> > I particularly like the second one... :)

> Sunil, the anti-grumpy faction has taken to changing the two above via
> s/F\*cking/Fine/
> This is probably better for public discussion, although it does seem to
lose the
> savour of the original.

I prefer to render them as follows:

RTFM: Read The Manual
STFW: Search The Web

I thus let each reader decide for themselves what they think the F stands
for. Oddly, they seem to come up with Sunil's interpretation N % of the
time (for extraordinarily high values of N).

--
Richard Heathfield

The bug stops here.



Wed, 17 Oct 2001 03:00:00 GMT  
 makefile question - foo.c := DUMMY=foo
Jack Klein schrieb:

Quote:

> LOL   : Laughing Out Loud
> ROTFL : Rolling On The Floor Laughing
> AFAIK : As Far As I Can Remember

Nope, that would be AFAICR or (sometimes) AFAIR or (some other times)
AFAICS :-)

AFAIK : As Far As I Know

(we don't wont to confuse any enwsbies, don't we ;-)

Stephan
(initiator of the campaign against grumpiness in c.l.c)
(-: A new excellent FAQ version has been released !!!      :-)
(-: Get it: http://www.eskimo.com/~scs/C-faq/versions.html :-)



Fri, 19 Oct 2001 03:00:00 GMT  
 
 [ 11 post ] 

 Relevant Pages 

1. newbie question: foo.exe ->foo.c ??

2. sizeof(foo) -1 or sizeof(foo)

3. difference between void foo(void) and void foo()

4. extern char *foo vs. extern char foo[]

5. How About #define foo foo

6. (foo == (foo_t *)NULL) vs. ((void *)foo == NULL)

7. Question: what is the _FOO_ convention all about?

8. question about malloc and sizeof *foo

9. #include "foo" vs #include <foo>

10. char foo[]=""; vs char* foo="";

11. #include "foo" vs #include <foo>

12. extern int foo(int); vs int foo(int);

 

 
Powered by phpBB® Forum Software