10 Dec
2004
10 Dec
'04
2:50 p.m.
Please, look at the options in config.h... It's really meant only for
developers who are sick of the fucked up debug output. If some user
decides to play around with these options (the other ones in the
config.h are things like "strict checking of the nonpaged pool on every
allocation" or "tracking of statistics about the tagged blocks in the
pool" and "whole-page allocations") it's really up to the user to fix
any problems which turn up because of changing these settings.
After all this is a source file, and we don't have something like
"menuconfig" or just "config" which allows normal users to edit it.
What do you not like about the compile-time configuration? the ifdefs in
the code or just that it's compile time?
No matter how many options there are, the ReactOS team can always choose
to ship only a single set of binaries (and support only this set of
binaries) - everybody who builds ReactOS himself takes the risk of doing
something wrong.
Ge van Geldorp wrote:
From: Casper
Hornstrup
Why would we want both variants?
I think we should stay away from this kind of compile-time configuration
options as much as possible. In my opinion, the CONFIG_XXX stuff as found in
the Linux kernel is a big mess and we shouldn't follow their example. When
we basically ship one single set of binaries we have at least a chance to
find bugs which people report, when you have to set a huge number of
CONFIG_XXX constants all bets are off.
Ge van Geldorp.