On 2010-04-06 06:26:01 -0400, Jacob Carlborg <d...@me.com> said:
Second try: building with dmd and then linking with gcc. This will cause the problem that I have to link to the D standard library when linking with gcc and for that I have to know the path to the standard library. I don't know if it is possible to get the path to the standard library.
This prompted me to check how creating a dynamic library is handled by D for Xcode. D for Xcode does this exact thing you describe: use GCC for linking (because Xcode expects gcc when converting build settings to command line arguments). So I added a dynamic library target to a project to check if it worked all right, and it does! It's great to see a feature like this (creating a dynamic library) work without having tested it before. :-)
Perhaps I need to add a project template for dynamic libraries so you can save the few clicks it takes to create the target.
-- Michel Fortin michel.for...@michelf.com http://michelf.com/
