exclude=path/ path2/file.d

Not 100% if the above works, but look for ‘exclude’ in the dsss docs.

I didn’t mean to imply that

These .di files are vital to how DSSS works.

Even when it isn’t being used to manage libraries? If all I want to do is compile a lib externally to the management system (i.e., without ‘installing’ it), I really don’t need the .di files, do I? I’ve found, though, that I can use install to move the lib to a custom dir (rather than target) and then do a distclean.

The docs make it seem complicated?

Somewhat. The first time I skimmed through it just seemed that there was a lot going on. When I took the time to read more deeply, I had to go through a couple of times to grok it all. It could just be me, though

DSSS uses the -explicit flag while building libraries, which means that only the files it lists will be built into them, not the dependencies.

Cool. So only the modules in the package get compiled. That makes me very happy.

“All I really wanted was access to the Rebuild executable without building it myself. I don’t care how they do it in the Linux world, I want my binaries without having to compile them first, thank you.”

And so, you downloaded the DSSS light binary. This is exactly what I was trying to encourage – I certainly wasn’t trying to encourage people to build it from source if they want it alone, I actually am not distributing the source separately either.

“I also didn’t like that it generated .di files for everything.”

These .di files are vital to how DSSS works. They associate imports with library files. This is why you don’t have to specify what libraries you want to link against when you use DSSS.

“As it turns out, creating a dsss.conf file is not nearly as complicated as the docs make it seem (Gregor did say doc writing isn’t one of his strengths).”

The docs make it seem complicated?

“There are still a few nits to work out, like I’m fairly certain that the DerelictSDL stuff is being compiled into every single DerelictSDL* library.”

They are not. DSSS uses the -explicit flag while building libraries, which means that only the files it lists will be built into them, not the dependencies.

(The entire next paragraph)

I should point out that a LOT of people are using Derelict through DSSS already, since I made it work with my evil magic.

“I still don’t like that it generates .di files (is there a way to turn that off?)”

To turn this off would be to subvert the entire purpose of DSSS. DSSS uses imports for all forms of dependencies – the .di files it makes associates those imports with libraries. Of course, I mentioned that above

Well, you can turn it off by just not building library files

“Color me converted.”

Thanks for the vote of confidence