* config.h
@ 2002-12-10 20:56 Chuck Winters
2002-12-11 7:28 ` config.h Joseph D. Wagner
0 siblings, 1 reply; 2+ messages in thread
From: Chuck Winters @ 2002-12-10 20:56 UTC (permalink / raw)
To: linux-c-programming
Would it be prudent to include the linux/config.h file in a user
level program to check for the existence of certain modules? I know
there are other ways, like using autoconf, etc. I was just wondering.
Chuck
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: config.h
2002-12-10 20:56 config.h Chuck Winters
@ 2002-12-11 7:28 ` Joseph D. Wagner
0 siblings, 0 replies; 2+ messages in thread
From: Joseph D. Wagner @ 2002-12-11 7:28 UTC (permalink / raw)
To: 'Chuck Winters', linux-c-programming
> Would it be prudent to include the linux/config.h
> file in a user level program to check for the
> existence of certain modules? I know there are
> other ways, like using autoconf, etc. I was just wondering.
No, because modules can be dynamically loaded on-the-fly, completely
independent of however the kernel is compiled.
Additionally, config.h (actually just an #include for autoconfig.h) is an
automatically generated file which varies depending upon how an INDIVIDUAL
USER compiles his/her own INDIVIDUAL kernel. There's no way for you to
anticipate the contents of config.h in advance. It's better to use other
methods.
Use of config.h would be necessary if you were compiling something directly
into the kernel.
Joseph Wagner
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-12-11 7:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-10 20:56 config.h Chuck Winters
2002-12-11 7:28 ` config.h Joseph D. Wagner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).