Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

specify a way to add .o files to a library #41

Closed
bos opened this Issue May 24, 2012 · 4 comments

Comments

Projects
None yet
3 participants
Contributor

bos commented May 24, 2012

(Imported from Trac #34, reported by @igfoo on 2005-12-11)

.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.

Contributor

bos commented May 24, 2012

(Imported comment by @dcoutts on 2005-12-11)

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

Contributor

bos commented May 24, 2012

(Imported comment by guest on 2007-12-26)

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

Contributor

bos commented May 24, 2012

(Imported comment by @dcoutts on 2007-12-28)

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.

jsl commented Feb 24, 2015

It seems like this issue didn't even make sense 8 years ago, let alone now. :)

I suggest closing and re-opening another ticket if there is something we're missing. /cc @tibbe

@23Skidoo 23Skidoo closed this Feb 24, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment