Linux Settings Tool
Moderator: Moderators
-
- Posts: 50
- Joined: 21 Jul 2006, 22:11
Hi I am not sure, but i get the Message,
So is there a possibility to compile it on other glibc Systems?
bye bert
Code: Select all
./settings/Settings++: /lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.4' not found (required by ./settings/Settings++)
bye bert
Would it be possible running Settings++ on windows using the gtk+ runtime? Anybody tried it? It sure would be nice to have a cross-plattform settings tool included in the spring distribution instead of the windows-only one.
If it hasn't been tried yet and someone would give me some pointers as to how compile it for windows I'm willling to try.
edit: oops, seems I'm a little confused if you're using gtk+ directly or wxwidgets. possible substituting wxwidgets for gtk+ my posts remains.
If it hasn't been tried yet and someone would give me some pointers as to how compile it for windows I'm willling to try.
edit: oops, seems I'm a little confused if you're using gtk+ directly or wxwidgets. possible substituting wxwidgets for gtk+ my posts remains.
AFAIK there is a difference in the way the settings are stored:
Windows uses the registry, Linux does use a dotrc file (.springrc)
I Assume (i haven't looked at the code) support for windows registry spring settings must be put into the client as well - then it should work.
(Read: No, not at the moment)
Windows uses the registry, Linux does use a dotrc file (.springrc)
I Assume (i haven't looked at the code) support for windows registry spring settings must be put into the client as well - then it should work.
(Read: No, not at the moment)
Possible yes, but there'd be no real point
(Settings++ doesn't contain code to read
or write registry keys, it was meant as a
counterpart to settings.exe rather than a
replacement).
@rudi: Settings++ doesn't impose a font
size restriction, so things may not always
display correctly depending on your WM
setup.
@bert: yes, the source is included.
(Settings++ doesn't contain code to read
or write registry keys, it was meant as a
counterpart to settings.exe rather than a
replacement).
@rudi: Settings++ doesn't impose a font
size restriction, so things may not always
display correctly depending on your WM
setup.
@bert: yes, the source is included.

But it could be a replacement if one would implement an abstraction layer for parsing and storing the options? I haven't looked at your sourcecode yet, do you think it would be feasible?Kloot wrote: it was meant as a
counterpart to settings.exe rather than a
replacement
I would even be tempted to try that if it does not mean rewriting huge chunks of the app.
Actually I think the time would be better invested in packing up the registry config class and shipping it over to the recycle bin.
There are a lot of things that the linux method has that would make lobby integration far easier, and would allow me to implement profile type systems etc.
It would also be a lot more flexible.
The registry class uses the same interface as the Linux file class, and IIRC is separated using compiler preprocessor statements so that the registry code is compiled on windows and the other way around under Linux, something which should be unified as soon as possible. Converting the MFC settings program under windows would be trivial.
I've thought about doing this for a long while but I've never gotten around to actually doing it.
There are a lot of things that the linux method has that would make lobby integration far easier, and would allow me to implement profile type systems etc.
It would also be a lot more flexible.
The registry class uses the same interface as the Linux file class, and IIRC is separated using compiler preprocessor statements so that the registry code is compiled on windows and the other way around under Linux, something which should be unified as soon as possible. Converting the MFC settings program under windows would be trivial.
I've thought about doing this for a long while but I've never gotten around to actually doing it.
Alright, after looking through the sourcecode of both Settings++ and the settings handling in the engine may I conclude:
- there already is an abstraction layer with rts/System/ConfigHandler.cpp
- it differentiates mac/linux/win using conditional compiles
- were Settings++ to use this interface instead of its own FileParser.cpp it could be used on all three plattforms (disregarding possible wxwidgets issues)
Am I right? Missing something?
- there already is an abstraction layer with rts/System/ConfigHandler.cpp
- it differentiates mac/linux/win using conditional compiles
- were Settings++ to use this interface instead of its own FileParser.cpp it could be used on all three plattforms (disregarding possible wxwidgets issues)
Am I right? Missing something?
I agree. A single file placed in windows user "home" directory appears much more user-friendly to me than some regkeys you have to use regedit for to change.AF wrote:something which should be unified as soon as possible.
This part I don't get. Converting it to what?AF wrote:Converting the MFC settings program under windows would be trivial.
I started to adept Settings++ to use the generic ConfigHandler instead of linux specific FileParser (that's alright with you Kloot?).
Couple of problems I've run into sofar:
- expected path issues (corrected with tips from this thread)
- my compiler (g++ 4.1.2) didn't like some implicit type conversions (right term?) from char arrays to wxString. So I wrapped all of them in appropiate functions as proposed in the wxWidgets wiki (should also avoid unicode issues).
I'm now at a point where I've successfully implemented a test call to ConfigHandler.GetInt(key,defaultValue). To fully use this I'll add the default values as fields to the Control struct.
Comments?
Couple of problems I've run into sofar:
- expected path issues (corrected with tips from this thread)
- my compiler (g++ 4.1.2) didn't like some implicit type conversions (right term?) from char arrays to wxString. So I wrapped all of them in appropiate functions as proposed in the wxWidgets wiki (should also avoid unicode issues).
I'm now at a point where I've successfully implemented a test call to ConfigHandler.GetInt(key,defaultValue). To fully use this I'll add the default values as fields to the Control struct.
Comments?
The adaption is somewhat complete. The code compiles ok, but I'm having problems while linking it to the relevant engine code. I've put the source in spring/trunk under tools/Settings++ and wanted to add it to the scons script. I thought that was the easiest way.
Well that was before I learned how complex that script really is (never used scons before). Anyway, after some reading in various documentations I got the source compiled via scons. That's when my trouble with said linking begins.
Here is an archive containing the source plus a diff of the SConstruct file.
The scons part for wxwidgets libs is adapted from here.
If someone could take a look at it and help that would be great. Of course I'm not set on using scons, just thought it would be easiest.
Also please tell me if I'm completely wasting my time here...
Well that was before I learned how complex that script really is (never used scons before). Anyway, after some reading in various documentations I got the source compiled via scons. That's when my trouble with said linking begins.
Here is an archive containing the source plus a diff of the SConstruct file.
The scons part for wxwidgets libs is adapted from here.
If someone could take a look at it and help that would be great. Of course I'm not set on using scons, just thought it would be easiest.
Also please tell me if I'm completely wasting my time here...
Code: Select all
tarendai@tarendai-desktop:~$ ./Settings++
./Settings++: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
tarendai@tarendai-desktop:~$
Do you have that library?AF wrote:Any ideas?Code: Select all
tarendai@tarendai-desktop:~$ ./Settings++ ./Settings++: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory tarendai@tarendai-desktop:~$