koshi wrote:It wouldn't be hard at all for SpringLobby to include it technically as it also is build on top of wxWidgets. I'd say less than 10 lines of code.
Exactly. I guess this leaves us with an architectural decision: should springlobby launch the settings tool, or should the settings tool be internal code to SpringLobby (and then duplicated by AFLobby)?
But since AFLobby probably would also like to able to call it I would prefer a seperate package and make it install to springs binary directory.
Better yet include it in the spring source itself and make it a seperate target once the building/dependencies issues are worked out.
The whole thing is a lot easier on windows, where it is no problem to produce a relatively small binary that has wxMSW statically linked. On linux I have to date successfully linked it statically to wxGTK, but I would also have to do that for the "real" GTK libs and that just seems wrong. I would even say that static linking (or shipping the dynamic libs) isn't the way to go on linux.
I'm willing to be convinced otherwise though, since I never distributed an app to a diverse lot of users.
You don't need to ship a static lib at all; I'll be recompiling it anyway within the package. The package, in turn, will automagically depend on whatever shared libraries it uses (Ubuntu is really nice this way.)
Just to be sure: this app isn't ready for general distribution yet. (But I am aiming to a relatively complete feature set for next weekend)
As long as it's ready around 0.76 :D