Re: Multiple .o files from single .c file - how?

• Next message: Mike Smith: "Re: Supporting non-commodity mainboard chipsets (2/4-way memory, multiple-PCI) in Linux ..."
• Previous message: George Bonser: "Re: Suggested dual human/binary interface for proc/devfs"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

hpa@transmeta.com (H. Peter Anvin) writes:

> It's not really a .h file then. I usually use .h only for real header
> files that don't cause code to be emitted. Files containing actual
> source that is #include'd for whatever reason (a reasonably common
> operation, especially when there is one file involved which is
> automatically generated) then I usually call it .c as it isn't a
> *header*.

Sure it isn't a header. However calling it .h prevents generation of
unnecessary dependency info.

-- 
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Mike Smith: "Re: Supporting non-commodity mainboard chipsets (2/4-way memory, multiple-PCI) in Linux ..."
• Previous message: George Bonser: "Re: Suggested dual human/binary interface for proc/devfs"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:15 EST