multiple .bygfoot dir
multiple .bygfoot dir
Seeing as I now have a number of bygfoot versions running. I was wondering if the .bygfoot dir could be under the bygfoot folder instead of in the /user. this would allow me to have a number of instances.
,bygfoot under bygfoot-1.7.3
.bygfoot under bygfoot-unstable
.bygfoot under bygfoot-1.9.0
OR
you could save it in /user as
.bygfoot-1.7.3
.bygfoot-unstable
.bygfoot-1.9.0
which is probably easier
OR
pass a cli argv like bygfoot .bygfoot1
etc.
Of course Im not totally sure whats in .bygfoot but I know I have to rm -r it each time I compile and run bygfoot for the first time to avoid clashing errors ?
,bygfoot under bygfoot-1.7.3
.bygfoot under bygfoot-unstable
.bygfoot under bygfoot-1.9.0
OR
you could save it in /user as
.bygfoot-1.7.3
.bygfoot-unstable
.bygfoot-1.9.0
which is probably easier
OR
pass a cli argv like bygfoot .bygfoot1
etc.
Of course Im not totally sure whats in .bygfoot but I know I have to rm -r it each time I compile and run bygfoot for the first time to avoid clashing errors ?
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?
Re: multiple .bygfoot dir
you have to do it because the /user/.bygfoot folder is the one with highest priority when looking for text files, and if there were changes involving incompatibilities, the game crashes.vector wrote:you could save it in /user as
.bygfoot-1.7.3
.bygfoot-unstable
.bygfoot-1.9.0
which is probably easier
OR
pass a cli argv like bygfoot .bygfoot1
etc.
Of course Im not totally sure whats in .bygfoot but I know I have to rm -r it each time I compile and run bygfoot for the first time to avoid clashing errors ?
i don't know yet which solution i'd prefer... the very first one isn't a good one because the user would have to 'cd' to the bygfoot dir each time he wants to play (we aren't running things with DOS anymore, are we?)
the second seems to be nice and clean, but it leads to users having to write their config files anew each time they install a new version (for stable branches this isn't good, you'd like to have your old preferences 'imported' if you upgrade to a new version containing bugfixes).
the third one is maybe the best; a bit more circumstantial than the second, but without the disadvantages. so i think i'm going to put it onto the todo list.
gyözö
Press any key to continue or any other key to quit.
really ?gyboth wrote:i've realised it's already possible to give a support dir as an argument. just use the -d switch: bygfoot -d /home/user/.bygfoot-1.7.3.
gyözö
so why did this not work
bygfoot -d/home/mark/.bygfoot2
it still creates .bygfoot not bygfoot2 then exits with
a usage command
-d Add the 'pixmapdir' directory to
and the warning
*** Doesn't seem to be a Bygfoot savegame: /home/mark/.bygfoot/saves/ ***
erm.. the -d doesn't create a directory. it takes a directory as an argument. so you just switch to the bygfoot-1.7.3 or whatever dir, and call bygfoot (or src/bygfoot) with -d ./support_files. there is the drawback, though that the conf file still gets written to the home dir. but you could copy it to the support_files/text_files dir, and it gets loaded with the -d switch.Anonymous wrote: really ?
so why did this not work
bygfoot -d/home/mark/.bygfoot2
it still creates .bygfoot not bygfoot2 then exits with
a usage command
-d Add the 'pixmapdir' directory to
and the warning
*** Doesn't seem to be a Bygfoot savegame: /home/mark/.bygfoot/saves/ ***
gyözö
Press any key to continue or any other key to quit.
Im still having trouble with this.
I now have the 1.7 and 1.9 cvs sources and its almost as if I have to "make install" each time I want to swap which branch i play? Of course I also have to rename or rm /user/.bygfoot
I guess i can live with this ..
but i also still can not get -d to work for me
-d indicates where the /support_file dir is yes?
not to be confused with the /user/.bygoot
eg bygfoot -d/home/user/bygfoot-1.7.3/bygfoot-unstable/support_files
should run the 1.73 branch of bygfoot
while
bygfoot -d/home/user/bygfoot-1.9.0/bygfoot2-unstable/support_files
should run the 1.9 branch.
but that dose not work. I still get whatever the last branch I just "make installed"
I suspect i have to move the /user/.bygfoot manually.? for each branch
I now have the 1.7 and 1.9 cvs sources and its almost as if I have to "make install" each time I want to swap which branch i play? Of course I also have to rename or rm /user/.bygfoot
I guess i can live with this ..
but i also still can not get -d to work for me
-d indicates where the /support_file dir is yes?
not to be confused with the /user/.bygoot
eg bygfoot -d/home/user/bygfoot-1.7.3/bygfoot-unstable/support_files
should run the 1.73 branch of bygfoot
while
bygfoot -d/home/user/bygfoot-1.9.0/bygfoot2-unstable/support_files
should run the 1.9 branch.
but that dose not work. I still get whatever the last branch I just "make installed"
I suspect i have to move the /user/.bygfoot manually.? for each branch
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?
since i had problems with this stuff myself, i've changed the priority order of the support dirs in 1.9. now the support dir in the pwd (current working directory) precedes the home/.bygfoot directory. so you can leave your home/.bygfoot dir for the 1.7 version; you just have to start 1.9 always from the dir with the 'configure' script, so that the support_dir in the directory itself is the one with highest precedence.
as to the -d switch, you have to have a space between the switch and the argument: -d support_dir_to_add.
gyözö
as to the -d switch, you have to have a space between the switch and the argument: -d support_dir_to_add.
gyözö
Press any key to continue or any other key to quit.
another approach
i have previously "make install" bygfoot so now no matter where i am in the dir structure typing bygfoot will run bygfoot.(the version i make install)
however i now have 3 versions of bygfoot src. the official release, the unstable release and the new version pre release.
Rather than having to make install (in the version dir that i want to try next) and then typing bygfoot how can i simply make it so that if im in the dir of the version i want and type bygfoot it runs that version?
this would then allow me to make some script files in my user dir like this:
and
this currently doesnt work because
typing bygfoot in the src dir is bypassed and the make install version is run.
typing ./bygfoot in the src, forcing it to run in src gets me this error
mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot
** (bygfoot:6460): WARNING **: Didn't find definitions directory.
so i tried -d
mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot -d home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable/support_files
and still it couldnt find it
i tried "ls" instead of ./bygfoot to see if the paths were working and sure enough it listed the support_files dir and definitions was there so im lost as to why it dosent work
i have just make uninstall bygfoot
so i now have to give specific paths for it to work.
same problem as b4 WARNING **: Didn't find definitions directory.
i have previously "make install" bygfoot so now no matter where i am in the dir structure typing bygfoot will run bygfoot.(the version i make install)
however i now have 3 versions of bygfoot src. the official release, the unstable release and the new version pre release.
Rather than having to make install (in the version dir that i want to try next) and then typing bygfoot how can i simply make it so that if im in the dir of the version i want and type bygfoot it runs that version?
this would then allow me to make some script files in my user dir like this:
Code: Select all
#!/bin/bash
cd /home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable/src
bygfoot
Code: Select all
#!/bin/bash
cd /home/mark/games/bygfoot/bygfoot11/bygfoot-unstable/src
bygfoot
typing bygfoot in the src dir is bypassed and the make install version is run.
typing ./bygfoot in the src, forcing it to run in src gets me this error
mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot
** (bygfoot:6460): WARNING **: Didn't find definitions directory.
so i tried -d
mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot -d home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable/support_files
and still it couldnt find it
i tried "ls" instead of ./bygfoot to see if the paths were working and sure enough it listed the support_files dir and definitions was there so im lost as to why it dosent work
i have just make uninstall bygfoot
so i now have to give specific paths for it to work.
same problem as b4 WARNING **: Didn't find definitions directory.
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?
just run bygfoot with ./src/bygfoot from the compile directory, ie. the dir with the autogen.sh and configure scripts. the directory './support_files' gets added automatically to the list of support directories, so you shouldn't have a problem with missing support files or dirs. the corresponding script (though i'd make an alias in your stead) would bevector wrote:Rather than having to make install (in the version dir that i want to try next) and then typing bygfoot how can i simply make it so that if im in the dir of the version i want and type bygfoot it runs that version?
Code: Select all
#!/bin/bash
cd /home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable
./src/bygfoot
of course not. the only dirs that get added automatically to the support dir list are './support_files' and '$HOME/.bygfoot'. if you're in 'src', there isn't a './support_files', so the only place for the program to look for support files is '$HOME/.bygfoot', which doesn't contain the new definitions, because it belongs to 1.7.typing ./bygfoot in the src, forcing it to run in src gets me this error
mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot
** (bygfoot:6460): WARNING **: Didn't find definitions directory.
probably because you forgot the leading '/'. if you type -d home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable/support_files, the program looks for the specified directory relative to the current path!.mark@saturnlx:~/games/bygfoot/bygfoot19/bygfoot2-unstable/src$ ./bygfoot -d home/mark/games/bygfoot/bygfoot19/bygfoot2-unstable/support_files
and still it couldnt find it
it's really a pity we have such a time difference we could jabber away such problems in a minute. on the other hand, every linux rookie has these problems in the beginning.
gyözö
Press any key to continue or any other key to quit.
agh yes if only you were next door. Jaqui and Eva could talk over coffee while we "bash"ed code
so simple its embarrasing.
A number of times you wrote /src/bygfoot and I kept thinking you meant cd into src and run bygfoot. But its very clearly not that at all. Well its celar now anyway.
oohh dear
as soon as i actullay type ./src/bygfoot it worked
btw
it matters not we have it working now
yeah!!
so simple its embarrasing.
A number of times you wrote /src/bygfoot and I kept thinking you meant cd into src and run bygfoot. But its very clearly not that at all. Well its celar now anyway.
oohh dear
as soon as i actullay type ./src/bygfoot it worked
btw
a typo i had tried both with and without / and even with and without space between -d it seemed to make no difference.probably because you forgot the leading '/'. if you type -d
it matters not we have it working now
yeah!!
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?