[afb]

I'm looking through the DSSS patch against our project,
and wondering which parts of it you want to have upstream ?
http://svn.dsource.org/projects/dsss/sources/wxd.diff

The dsss.conf and wx/libs.d are not a problem, I'm just
a little concerned about the toplevel "mkwxlibs.d" file...
Both the location of it and the dependency on DSSS etc.

wx-config.exe will be integrated next version, so that should
work on Windows too. But both the current mkwxlibs program
and dsss_build seems to be missing the platform and encoding ?


Is there a way to include those from the files, like with Make ?
(I've ported the wx-platform and wx-encoding scripts to C++)

Where can I read more about packaging for Bud and DSSS ?
(not sure if build handles C++ compiling at all, but anyway...)

[Gregor]

Sorry I didn't see this, I always forget to look at this forum

If you'd like to maintain DSSS buildability upstream, that'd be great, but I'm not asking or requiring you to.

As per the top-level mkwxlibs.d:
1) It does not need to be top-level, it can be wherever you want.
2) It's used as part of the DSSS build process, so the fact that it depends on DSSS is fairly irrelevent and benign, as it's not part of the actuall installation, nor should it be part of non-DSSS builds.
3) If you want to make it obvious that it's only useful as part of the build process, you could name it something like dsss_mkwxlibs.d or whatnot.

As per the fact that mkwxlibs.d doesn't check platform and such, that's because I don't know what platform differences exist . That file just generates a list of libraries from wx-config, and uses that list to make a libs.d file, which is in turn used by DSSS to link against the proper libs. If it needs to generate something different on different platforms, I can change it - it's not my field of expertise.

I'm not sure what you mean by "Is there a way to include those from the files, like Make". The .d file is ran by dsss during compilation, so you could just as easily run anything else. Again, let me be clear: mkwxlibs.d is not used in the installed version, it's just used by the build.

Bu[il]d doesn't handle the C++ part at all, it defers to make. I have documentation on using DSSS in DSSS' source (and SVN), docs/README.software_engineers . If you feel any part is short or unexplanatory, please tell me, it probably needs significant expansion

Thanks for your interest.

[afb]

I ported mkwxlibs.d over to "wx-libs.cpp", and included wx-config-win.cpp
Hopefully it should be able to create wx/libs.d for Bud automatically now ?

There is also a typo in the dsss.conf, says "GNU" but should be "GDC":