specify a way to add .o files to a library

[igloo]

.o files may be generated by means outside of cabal, and there should be a way to list them in the .cabal file as being linked with the library.

[duncan]

This needs a great deal more specification. When will these .o files be created for example?

[guest]

By a build hook, probably. Possibly by another hook, or outside of Cabal completely. All you have to do is to tell the linker to link them, though.

Ian

[duncan]

This would not work at all well with a dependency system since we want to know there how to generate or re-generate the .o files rather than just rely on sequencing. On the other hand in the new dependency system it should be easy to add extra ways of generating .o files in a hook. So I think we should wait and revisit this issue when developing the dependency framework.