Re: [openMSX-devel] Config files

[Manuel B. <ma...@ms...>]

Wouter Vermaelen wrote:
>>At least the doubles should be removed, so the TurboR GT and ST and 8250
>>configs in src/cfg could be removed since they are in /share/machines too.
>>2) Second, I propose just to move all of them to the machines directory.
>>Later we could spread them as a 'machine pack', upload them to an FTP
>>site or even let them be retrieved from an online database.
>>For now, we should just put them all in /share/machines, IMO. They're
>>not really useful in src/cfg, since they can not really be used directly.
>>This means also the CBIOS stuff should get a machine name.
> 
> Completly agreed. Volunteers?

I'll do it. Atarulum just send me (and you ;-) a whole bunch of new 
configs. I'll check those and add them today, I hope.

>>3) And what do we do with the exampleconfigs.xml?

> I don't care much for it. In the next release its functionality (showing
> all devices and their possible parameters) will be replaced by DTD's.

It's quite instructive for users to create some config files, but I 
think with the -ext system it isn't really necessary anymore indeed. We 
should check if everything is there though: let's make an extension for 
every device that is useful. E.g., also for JoyNet.. (Can't think of 
other ones that are missing at the moment... ah! Panasonic MSX Audio? Or 
other special carts?)

>>4) About the names of the ROM files mentioned in those config files. I
>>propose to use the names that are used on FUNet in the openMSX dir:
>>http://www.funet.fi/pub/msx/system_roms/openMSX Those names are not
>>perfect yet, but they are the most informative that you can find on the
>>net (atarulum and I came to these preliminary names...). Probably all
>>configs use these names, but I'm not entirely sure about that.
> 
> Agreed, but we should also put "roms/" in front of each name. This is the
> directory structure we agreed upon.

So, we agreed on a roms/ dir in the extension or machine dir?
Is it very interesting to do that?
As far as I'm concerned, I'd be very happy having the roms just in the 
same dir as hardwareconfig.xml. There are no other files there anyway.

>>Last question: Wouter, did you get a chance to think about those paths
>>that are hardcoded? I still feel they should be more easily
>>configurable, for porters and packagers.
> 
> I've looked over the code, but I don't think it needs changes. The only
> thing porters/packagers need to change it the openMSX base directory
> 	/opt/openMSX
> 	~/.openMSX
> All other paths are relative to these 2 base directories.
> These paths are coded in one single place in the source tree
> 	src/file/FileContext.cc:105

But then you assume that everything is installed in only one directory. 
For most applications in e.g. Debian, this is not the case. E.g. zsnes:
binary is /usr/bin/zsnes
docs are in /usr/share/doc/zsnes
manual is in /usr/share/man/man1/zsnes.1.gz

Did anyone try to install openMSX globally on his system and tried to 
use a local .openMSX dir with it, to see if this is a workable installation?

What about saving settings.xml to the local .openMSX dir?

-- 
Grtjs, Manuel

PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/