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

H. Peter Anvin (hpa@transmeta.com)
9 Apr 2000 04:54:18 -0700

Followup to: <m31z4fpl5u.fsf@intrepid.pm.waw.pl>
By author: Krzysztof Halasa <khc@intrepid.pm.waw.pl>
In newsgroup: linux.dev.kernel
>
> All .o files must be independent - the user may enable compiling only some
> of them.
>
> It looks like making stub .c files and #including the real file.h is
> the best approach here. Not that I like the idea of having full C source
> in .h file.
>

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*.

-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."


-
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/