Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path
On 6 Mar 2006, at 15:39, Tom Koelman wrote:
Hi,
I am fixing the Windows Installer with regard to the GNUstep.conf
file. I am building base 1.11.2 and gui 0.10.2.
base 1.11.2 was unfortunately not tested on mingw, and released broken.
I would therefore rather take a recent snapshot from svn and use that.
I believe the current state is good ... certainly I used it a few
days ago.
./configure --disable-xml --with-config-file=$GNUSTEP_INSTALL_DIR/
GNUstep.conf
Disabling xml is no longer necessary if you use the modified libxml
as described in the README.MinGW in the current make package.
2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE
value ('/etc/GNUstep/GNUstep.conf') is not an absolute path.
Please rebuild GNUstep-base specifying a valid path to the config
file.
What do I do wrong? As far as I can tell I already build GNUstep-base
specifying a valid path to the config file.
base now uses native windows paths ... current make/base configure
scripts set up two separate config files, one for the unix-style make
environment, and one for the windows-style runtime environment.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path
Sheldon Gill [EMAIL PROTECTED] writes:
I use the following incantations:
In the directory with source of GNUstep make:
cd /gnustep-source/make
./configure --prefix=$GNUSTEP_INSTALL_DIR
--with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install
[...] Build ffcall [...]
# Build and install the base library itself
cd /gnustep-source/base
./configure --disable-xml
--with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install messages=yes warn=no
Now, if I run the defaults.exe program or some other GNUstep using
program I get the following:
2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE value
('/etc/GNUstep/GNUstep.conf') is not an absolute path. Please
rebuild GNUstep-base specifying a valid path to the config file.
What do I do wrong? As far as I can tell I already build
GNUstep-base
specifying a valid path to the config file.
If you have specified a file and it's been picked up correctly you will find
your definition in:
core/base/Source/config.h
I suggest you check that first.
My config.h does not contain a definition of GNUSTEP_CONFIG_FILE. It
does contain this:
/* Disable GNUSTEP_CONFIG_FILE environment variable */
#define OPTION_NO_ENVIRONMENT 1
Are you using the *release* of base 1.11.2 or a later CVS version?
Yes, I am using the release.
Is there maybe some documentation about the way this configuration
file configuration works?
Regards,
Tom Koelman
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path
On 7 Mar 2006, at 06:47, Tom Koelman wrote: Is there maybe some documentation about the way this configuration file configuration works? Yes ... 'configure --help' for the make and base packages, though this changed quite a bit between the last release and the current code in svn. For information on what can go in the config file, you can refer to the base reference documentation (Documentation/Base/Base.html) ... of course, first you have to configure and build base and generate the documentation :-( The *intent* is that the default config should work without any hassle, so that you only need to read the documentation to tweak things later. So we do need to put an effort into making the initial install smooth and reliable. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path
Tom Koelman wrote:
Hi,
I am fixing the Windows Installer with regard to the GNUstep.conf
file. I am building base 1.11.2 and gui 0.10.2.
I use the following incantations:
In the directory with source of GNUstep make:
cd /gnustep-source/make
./configure --prefix=$GNUSTEP_INSTALL_DIR
--with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install
[...] Build ffcall [...]
# Build and install the base library itself
cd /gnustep-source/base
./configure --disable-xml --with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install messages=yes warn=no
Now, if I run the defaults.exe program or some other GNUstep using
program I get the following:
2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE value
('/etc/GNUstep/GNUstep.conf') is not an absolute path. Please rebuild
GNUstep-base specifying a valid path to the config file.
What do I do wrong? As far as I can tell I already build GNUstep-base
specifying a valid path to the config file.
If you have specified a file and it's been picked up correctly you will find
your definition in:
core/base/Source/config.h
I suggest you check that first.
Are you using the *release* of base 1.11.2 or a later CVS version?
Regards,
Sheldon
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Proposal: Mandatory periodic releases
On 7. Mrz 2006, at 16:41 Uhr, Adam Fedor wrote: Well, I try to do something like this, only I aim for binary compatibility, rather than API stability. That's way too hard for me to track - something that all the developers would have to sign up to do, not just me. The last binary incompatible release was September, last year (7 months). I'm not entirely sure what you mean by that. Ensuring ABI/API stability just implies that every once in a while a new version is branched. This branch then is only allowed to add fixes, no new API/ ABI stuff. Development of course will continue as usual (with breaking things ;-) in the trunk and with alpha releases. Technically patches (aka bugfixes) to the branch could/should only be allowed for a release manager, could be you or someone else. A patch would need to ensure that nothing ABI/API is changed, this should be reasonably easy. Since a stable release should happen max every 12 months this should be no big burden. And interest to provide fixes when necessary should be high because only stable versions (and API/ABI compatible fixes) are usually allowed in distributions. Summary: IMHO this should be easy with Subversion. Just do a copy of trunk every 12/18/24 months and mark that the stable release and disallow changes. This might imply that this only makes sense for core components like gstep-make and gstep-base since maybe gstep-gui has so many bugs that it doesn't make sense to tag a stable. Can't decide that. Greets, Helge -- http://docs.opengroupware.org/Members/helge/ OpenGroupware.org ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
